Almost a year later, and by doing this with out explaining what the fix was, screwing up months of work and data based on the 4 second refresh which was TBC ignite
Instead of fixing it at the start just wait for AQ then slip in a vague fix and watch as the mages get all upset
Thanks for the fix 10/10 communication on this would reccomend /s
12 Likes
What�
Sir, this is a Wendyâs, I just need to know if you want cheese or notâŚ
12 Likes
They changed ignite from a 4s duration to 2s.
Will be hard/near impossible to ârollâ ignite now unless you have some ungodly amount of mages
Blizzard finally makes a change thatâs more vanilla like, and all they get is hate. Now your mages will go from gearing for lots of crit to gearing for lots and lots of crit. What a twist.
21 Likes
that wasnât a good way to fix ignite
what they shouldâve done was kept the 4 second duration, but made it so that ignite calculated the damage dealt by all attacks(not just the first 5) that triggered that stack, and also made it so that, when it refreshes, the damage that ignite already dealt isnât added to the new stack
this way, for example, when 5 fire mages crit at the same time with pyroblast for 2500 damage, and ignite then ticks once for 2500 damage, and then another fire mage crits with scorch for 1000 damage, the next tick of ignite would deal 1450 damage, and then if it ticks again for 1450 damage and another fire mage crits with scorch for 1000 damage, then the next tick of ignite would deal 925 damage, and so on
that is, instead of every tick of ignite then dealing 2500 damage, even after someone refreshes it by critting with a low rank of scorch for 150 damage
Ah, well thatâll be fun. No more single Mage getting all the DPS credit.
2 Likes
Why wouldnât we be frustrated?
Weâre told they will not fix obvious bugs like flask snapshotting for warriors, and they go and nerf mage like this?
Thereâs no consistency.
4 Likes
This bugfix was a bit late but its a good one. TBC ignite shouldnt have been in classic at all but atleast its now gone 
.
5 Likes
I actually agree.
The coordination required to keep one ignite going isnât too difficult but one person can screw it up.
At least with this you can do well on your own
1 Like
Oh look, a warrior thatâs happy his hybrid class wont have any competition for DPS.
6 Likes
Did your game not let you roll a warrior? Was the balance between dps an unknown factor? Did any of the meta specs come as a surprise to you in this âsolved gameâ? Are you standing in a fire and then complaining that it burned your feet?
16 Likes
praise azeroth no more scorch spamming mages
1 Like
scorch has nothing to do with this
3 Likes
Now this is what I call âsCoRcHeD eArtHâ hehe 
3 Likes
Have we been told by blizzard that the flask is indeed a bug? Maybe its a featureâŚ
This was a âbugâ being that it was TBC ignite and not vanilla.
Where are you guys seeing ignite at 2s? Mine still rolls for 4sâŚ
1 Like
Ignite still has a base duration of 4 seconds. Essentially each additional crit now only adds 2 ticks onto Ignite without changing its remaining time, rather than refreshing it to 4 seconds (ie Ignite at 0 sec, crit at 1.6 sec, ignite tick at 2 sec, then 4 sec ; crit gives two ticks but only over the 1.4s left on Ignite). With spell batching already delaying Ignite procs, rolling Ignites are much more prone to falling off.
Most of us donât care too much, especially given that this is how it worked in vanilla. This only upsets tryhard parsers who foolishly thought theyâd own the one big Ignite for 98% of the boss fight.
9 Likes
This.
Several of my guild Mages were kinda miffed at the idea that if they werenât the lucky first crit, theyâd appear to pull terrible DPS since all their Ignite damage was being counted towards someone else. This will alleviate that dramatically.
It will also alleviate the possibility of a single Mage pulling insane TPS due to massive Ignite rolling, which is also nice and healthy for the game.
4 Likes
Honestly I was looking forward to the fun factor of having a small team of fire mages try to maintain Ignite as long as possible. I do however support the âbugfixâ if this is indeed how Ignite worked in vanilla.
Annoyingly however, all the damage meter addons (details, recount) do credit the mage who starts an Ignite with all the damage the Ignite causes before it falls off. With only 4 fire mages (Combustion and good luck) we were able to roll an Ignite for about half of a boss fight in MC, but it did not belong to me. Before the fight I was neck-and-neck with âmage xâ in total damage, but after that fight I was behind him by several thousand. No surprise there, âmage xâ owned that Ignite.
Is this something inherent in the game, or is this something the damage meter addons could measure differently? I really do try to not have an ego about my dps, but it is a measuring stick by which you can find ways to improve. However, the way Ignite damage is currently calculated is disingenuous and thereâs no way to tell if your damage was lower than another mage because you performed poorly, or just had bad luck with being the one to start a rolling Ignite.
Hmm crit builds having unreliable damage outputs, whoda thunk it?
1 Like