Talk:Dagon

The instant damage
The notes of energy burst say:"The damage is applied instantly, so it cannot be avoided."

However, under some unknown circumstances(I came across these circumstances in both matchmaking and experiments), it is possible to dogde dagon's damage by activating BKB/manta or casting puck's phase shift. It is impossible to avoid its damage by reaction after seeing the particle effects, the circumstances here are mainly those "next level" ones.

It seems that the damage perhaps has a very short delay(≤0.03s probably). Or maybe it really deals instant damage but due to some game engine mechanism, its damage gets delayed.


 * According to this reddit post by User:Bu3ny the damage is not instant, but waits for the next server tick (max. 0.03 seconds) to deal damage and is thus dodgeable in that time period. I'll ask him if there's a reason this is not included on the wiki.--Litzsch (talk) 06:32, 20 June 2017 (UTC)


 * According to my recent test, dagon now really does instant damage, without being delayed for a tick sometimes. It seems that valve has recently fixed this "bug". Hope for further confirmation. --Symmetrychaos (talk) 07:23, 3 July 2017 (UTC)


 * Not for me. Technically if Dagon is instant, the cast time is the same as the damage time. But I tested minutes ago, and it's not. --Elite stay (talk) 07:35, 3 July 2017 (UTC)


 * I did some testing of my own just now and at least for me cast and damage time seem to be simultaneous. (see here) --Litzsch (talk) 08:42, 3 July 2017 (UTC)


 * Still weird. I thought that's Sandbox's bug, but I tested again on demo mode. The result is if cast dagon without turning, yes they are simultaneous, but if with turning, they are not. And even when I tested on local lobby, test subject was lost modifier earlier than received :/ I don't know what happened. --Elite stay (talk) 09:03, 3 July 2017 (UTC)


 * Can't repro that 0.03 now (what happened!) :/ --Elite stay (talk) 09:12, 3 July 2017 (UTC)


 * Check for a debuff. If it still uses a debuff, then it was not fixed. It's not always 0.03 because of how game ticks work. Regardless, the delay is still there, so it can still be dodged.  Bu3ny  (talk) 10:49, 3 July 2017 (UTC)


 * The debuff does still exists, but I've never seen the damage being delayed for a tick even once in the whole test for over one hundred times. If the delay still exists, why didnt it occur for so long? --Symmetrychaos (talk) 11:00, 3 July 2017 (UTC)


 * Yea, the delay seems to be not happen anymore. But it is still dodgeable with invulnerability like before. I can still reliably do it with e.g. storm spirit.  Bu3ny  (talk) 11:32, 3 July 2017 (UTC)


 * But if the delay is no more, why dodgeable? Does it mean that the delay is now always less than a tick(0.03s)? --Symmetrychaos (talk) 12:11, 3 July 2017 (UTC)


 * The spell cast order was given before the dagon cast order. If timed right so that both get executed on the same tick, the spell cast starts first, and then the dagon cast happens. Since both happen at the same tick, they will happen, regardless of what happens to the target. So the invulnerability cannot prevent the dagon, but can prevent the damage, since the damage is applied as last. So the order is: Spell gets cast -> dagon gets cast -> spell applies its effects -> dagon applies its effects.  Bu3ny  (talk) 12:32, 3 July 2017 (UTC)