Blizzard Hotfixed Ignite To Only Have A 2 Second Refresh Window
BZZZZ WRONG.
Seems like you forgot how your own game works, so i’ll show you some nice video evidence.
As you can see quite clearly from this rather famous mage video in classic Demia demonstrates quite clearly that ignite can and should be refreshed within the entire debuff window of ignite, since she has time to cast another whole fireball in the window hence it must be longer than two seconds.
lastly, if mage’s ignite cannot be refreshed past 2 second a mage can never benefit from it’s own ignite, which is simply moronic. and would make it the only spell caster in the game to not receive 200% or higher critical strike modifier. You’ve broken mages. I can only express my exasperation and disappointment in this eleventh hour “Hotfix” to mages when we were all warming up to be the flavor of the month dps, this is so obviously broken and unfair it’s hilarious.
There are at-least 10 other known class bugs we know for certain are legitimate gamebreaking issues, like say literally damage immune warriors and you choose to incorrectly “balance” mages at this point just shows bias towards the wrong and vocal minorities, once again. And frankly i don’t even believe in your reference client anymore after all the #nochanges we’ve seen thusfar.
They could have made classic the perfect version of the game. Included all the fixes from tbc, which completely fixed the vanilla game, which noone played anymore, as they moved to tbc.
flightpaths, mailboxes, AV map, broken questlines.
They could have included all that.
But i think that blizz wanted the bugged version, just to show us all how wrong we were, asking for classic.
Although i see your point, and agree with you on some degree.
But then again, a huge majority of players chose to play mage after seeing some cool stuff that streamers did during the beta without even thinking about the role balance on their servers.
-hey uhm, we dont have any tanks
-then mage is the obvious choice!
-how about a healer? maybe?
-no, mage is the way to go
-if you want to play dps, how about a warlock? we dont have enough of those?
-a warlock is still not a mage!
You get what you deserve, i wish they nerfed it even more, would ve loved to see all these kids crying.
Not a fanboy btw, just hate people who chose to play the class just because “mage stronk!”
If you look at the videos in this thread you will see that it’s working now just like it did back then.
Edit:
It’s as he says it seems that it was wrong before this change. But seeing all these errors or bugs from their reference makes me think that they used some patchwork 2.0.1 client and reverse engineered that one for classic.
I don’t see how streamers are relevant to anything here, i’m posting my disappointment with how this nerf has been doled out based on user feedback that is clearly and demonstrably incorrect from referencing old videos of mages. this is a stealth nerf, not a balance or hotfix. especially when blizzard claims to have the almighty and correct reference client.
I see super hd videos from modern clients and private servers, which are simply not relevant, and a complete cluster of buffs and debuffs hitting raidbosses with no accounting for debuffslots or 1;1 testing. i’ve shown a video of it working, and i can find more pretty easily, I’m not sure why or how the ignite falls off sometimes, but CLEARLY it does get applied in succession by fireballs so the 2 second rule is fubar by default, since a fireball takes 3 seconds to cast.
And i know it seems to count for nothing but i know from first hand experience ignite worked this way, i spent many hours in epl farming scarlets, and i remember explaining to people how OP combustion was since it tended to trigger chains of ignites.
If you disregard all evidence which don’t support your assertion it’s fine, even claiming that Curse or anyone to use these kind if primitive ui addons play on pservers or modern clients is fine. But the video you’ve linked shows that you are wrong.
Correct, something kicked that ignite off, i assume it was munched by a lesser ignite resetting it or some other mechanic, but in the exact same sequence you see very clearly what i said is correct, sequential fireballs are triggering and renewing ignite, a fireball takes more than 2 seconds to cast and this would be impossible if the 2 second rule were in place, i’m not ignoring any information i’m stating the facts of what happened in the clip, nothing more and nothing less.
From what theorycrafters are reporting you have 3s instead of 4s to refresh it (due to batching and other stuff). And you need multiple mages to use it reliably anyway. And the mage with ignite can even spam quick low rank spells to refresh it more often.
Aslong as it behaves this way in raids it’s fine, but relying on lag to dps is always going to be … fun? and yes in theory if the 2 second rule exists but the server snapshots a spell 400 ms late and 400 ms early then the interval is roughly 2 seconds, but clipping that seems unlikely you’re still 200 ms short and that’s an eternity in computer time.
and yes, absolutely blastwave, fireblast, scorch should hit in around and under the 2 second rule as well as low level spells.
The change they did as they’ve said it was that ignite can’t go up to 4s duration if the next cirtical would land after the 1st tick of the dot. Funnily enough in your video there are 2 instances where it happens and in both of them it behaves differently.
1st instance is at 3:31
Fireball crit for 3025 ignite almost instantly after 1785 so i assume that’s the fault of batching as the crit of the fireball should have set the debuff back to 4 sec. After that fireblast for 2012 at 3:32 ignite is off at 3:33 deals 1785.
So we can say that in this case the crit added the damage but didn’t extend the duration to 4 sec as it was ticking already. Eather that or this thing makes little to no sense eather way.
2nd instance is at 12:49
Fireball crits for 2849 PoMPyro don’t crit ignite ticks for 570 at 12:52 fireblast crits for 1538. Ignite ticks for 878 at 12:54 and at 12:56.
The difference between the 2 instances is that when it fell off after 2 sec the crit came just a bit before the ignite in the 2nd case the crit happend just a bit after but in that case it put it back to 4 sec.
This makes little to no sense. I will look into more vide breakdowns as I have some time to waste.
okay. so now you see my point? there is clearly no 2 second “hardcap”, as whilst the debuff is inconsistent, sure but it does infact stack and renew on occasion.
and yes i fully accept it falls off from time to time, but this is not the behavior we’re seeing in game, or here. and i know full well i’ve seen 2+3 stacks in the wild so to speak with my own mage in classic. I’m honestly wondering if it’s just getting resisted or if it’s getting blown out by lesser ignites, or what is up with it but i’m glad you’re seeing what i’m seeing and not just throwing forums at me and laughing like so many uninformed cretins.
I DO accept the possibility that something is causing the game to register the ignite before the 2 second timer, code is code, games aren’t neuclear simulators miliseconds happen. however this is latency and spellbatching related and is damn near impossible to test, and it’s obviously impossible to time travel back to a point where we can conduct practical tests with a good ping. I’m still highly dubious that this is the case due to the exact behaviors exhibited, as it should be a moonshot to see all the factors line up like that.
My current theory is some hence unforseen mechanic is pushing the ignite off, or it really is just the stars aligning that causes this to happen. the fix imposed by blizzard is simply emulating this inconsistent behavior as best as they can interpret.
one of the hard facts i do know about ignite is lesser ignites will cause degradation of the ignite, possibly blowing it off, i’m honestly unsure. we used to call this ignite munching back in the day.
Another source from old wow here: sugguests ignites can simply be resisted and fall off:
If you check wowiki Ignite_(old)
“The direct fire damage hit is, like all damage spells, subjected to the effects of a partial spell resist roll. However, here’s the rub, once that spell resist is calculated and applied to reduce both the direct damage hit and it’s resulting ignite component, these already reduced ignite ticks are then themselves further subjected to another pass of the same spell resist roll each tick.”
