|
|
It is complicated
1.9.0 introduces a damage queue to prevent deep recursion and fix some bugs
Previously all damage has been issued immediately, so for example in 1.8.10 when Thunder hit an enemy and killed it, the next instance of Thunder ability no longer sees the enemy cause he's dead.
In 1.9.0 the damage gets enqueued and will only be applied to the enemy later in the same frame, meaning those two Thunders damaged the enemy "exactly at the same time" and then the damage manager has split their damage equally to kill the enemy.
So, architecture-wise, it works properly and while it was convenient to chain Thunders this way, I'll have to leave it as it is, because it does not conflict with the ability's description and returning the old behavior will complicate the code / make it more dirty and (probably) buggy. |
