Arcane Brilliance: Perfecting the fire tree

When I started this triumvirate of columns highlighting the shortcomings of the three mage trees, I knew that this would be the point at which I would start having problems. See, things were pretty easy with the arcane and frost trees. You can find those two previous columns behind the following links:
- Things I want to see changed, arcane edition
- The constantly evolving, completely stagnant frost tree
You think you have problems? Well how about I trade you my Arcane Barrage for your moving Scorches? See what kind of problems you have then.
The fire tree is flat-out incredible right now. It's near the top of the damage charts at the highest levels of Cataclysm raiding, the talent tree is spectacularly designed from top to bottom, and most importantly, the spec is just really fun to play.
Still, there are a couple of nagging issues -- annoyances that, if addressed, might just result in the game's first truly perfect spec. I think that's a noble goal, and we're gathered here today in pursuit of it.
Ignite munching
After more than four years of losing perfectly good DPS to ignite munching, it's becoming less a fixable issue than an accepted feature of the spec. The developers are fully aware of it, they balance around it, and they've told us in no uncertain terms that they really don't ever intend to fix it. Indeed, they deem it virtually unfixable, due to design limitations.
So if we know we're losing damage to this phenomenon, and the designers know it, and they take it into account when they balance our numbers, is it really a big enough deal to get upset about?
Yes. And here's why:
Ignite damage depends on crit. In a munch-less world, the higher your crit numbers, the more Ignite procs you'd get. But since Ignite munching causes you to lose a good percentage of those potential Ignite procs, independent of your crit rating, crit as a stat is substantially devalued by this bug. In turn, this devalues mastery, and it hurts our chances of getting a good Combustion off. It's a substantial issue.
Crit should be a hallmark stat of the fire tree. The tree is designed around crits, from top to bottom. No less than six fire tree talents depend upon crit to function properly. If the tree were working as designed, crit rating would be the consensus secondary stat for fire mages, just behind intellect and hit-to-cap, but well above mastery and haste.
As it stands now, though, crit isn't worth anywhere close to what it should be, and so for a large number of mages (depending upon gear), haste is a more attractive stat than crit. The tree becomes less about giant, frequent crits (which is precisely what the tree is quite clearly designed to be about ... see Hot Streak, Master of Elements, etc.) and more about lowering cast speed and getting additional ticks on DoT spells.
Now, you might ask, what's really wrong with that? So you stack haste instead of crit. You're just swapping one kind of effectiveness for another.
And while that may be true, I would counter that for a fire mage, the difference between stacking crit and stacking haste is the difference between being a fire mage and being some other kind of mage.
Then you would of course reply Your mom, and I would say Nu-uh, no you dint, and you would retort with for reals, at which point we would, um, throw down? I believe that's how this kind of thing goes.
Bottom line here: Ignite munching screws up the fundamental, unique essence of fire-magehood. I understand that it's nigh impossible to fix at this point. I don't really have a solution to offer here. I don't want a massive redesign. But I don't want another tiny Band-Aid, either. All I want is to see my Ignites happen when they're supposed to. Oh, and a throne constructed entirely out of warlock skulls, upon which to sit and survey my kingdom. I want that too.
Praying to the RNG gods
So you're in a lengthy boss fight. You're Fireballing away, nailing the timing on all of your cooldowns, refreshing Living Bomb at the optimal moments, moving skillfully when necessary, watching your mana, managing your threat generation, and just generally being awesome.
Combustion comes off cooldown. Now you only need one thing: a good solid Ignite proc. Ideally, you'll get a good Hot Streak/Pyroblast crit. Three Fireballs go by. No crits. Four. Still no crits. Then you get a crit on the sixth Fireball, but not on the next one. Fine, you think, maybe a Hot Streak isn't in the cards, and I've been sitting on this Combustion cooldown for going on 30 seconds. You decide you'll settle for a Fireball crit. Three more Fireballs go by with no crit. Four. Five. You open a GM ticket with the subject line "I HATE YOU ALL SO MUCH." Meanwhile, your DPS has dropped below the guild leader's girlfriend and the DK off-tank, and you're curled up in a fetal ball on your computer chair, weeping softly and praying for god to end your misery.
I'm not aware of any other class/spec that is so completely beholden to the random number generator. As we just discussed, we're a crit-heavy bunch. That's the way the spec has been designed. When the crits are coming, we're gods. When they aren't, we're not, and there is no in-between. It's a bit like that old Norm Macdonald routine about the sport of cliff diving: You're either Grand Champion or stuff on a rock.
Regardless of skill, any fire mage can be a terrible fire mage at any point. All it takes is a streak of bad luck. See, the problem lies in the fact that fire mages are so dependent on what amounts to a constant series of dice rolls. Each time we cast a spell, it's a roll of the dice to see whether or not we get a crit. Even if our crit chance is 50%, it's 50% every time we roll that dice. That's a fresh 50% every roll. It never goes up to 75%, and it will absolutely never be 100%. Which means that it's possible that we could cast spells forever and just never see the dice roll our way. It's numerically possible for a fire mage with a high crit chance but spectacularly bad luck to cast Fireball forever without ever seeing a Hot Streak proc.
Now, it's also incredibly improbable for that to happen. The laws of probability dictate that at some point, even the most unlucky schlub will get two crits in a row. But tell that to the fire mage who finds himself mired so deep within that swamp of bad luck, he's forgotten what a crit looks like.
Our numbers can fluctuate so wildly during the course of even a short fight that it becomes very difficult to depend on anything. The spec begins to feel so dependent on strings of luck that you stop feeling like your success has anything to do with your own skill and everything to do with a series of good or bad dice rolls. Downing a boss shouldn't feel like pulling the arm on a slot machine.
Now, how to fix this? I've already shared my feelings on the nature of the fire tree, and how crit should be the most valuable secondary stat. The tree is designed around an amount of uncertainty alternating with streaks of awesomesauce. I don't want that to change. But I do want to see a bit of a concession made to the fact that at any moment, the RNG gods could frown and any fire mage could suddenly become awful through no fault of his own.
Here's my solution:
Cold Streaks. Whenever you go a certain number of casts without a crit, you go cold, which triggers a buff that grants you a free crit on your next cast. Cold streak is probably a stupid thing to call it, but the idea is that even streaks of bad luck can generate a way to get back into a streak of good luck. I just want our luck to be just a teensy bit more controllable.
What do you think? What are some ways we could fix this issue without compromising the essence of fire mages?
Filed under: Mage, Analysis / Opinion, (Mage) Arcane Brilliance






Reader Comments (Page 1 of 4)
Wayne Apr 9th 2011 2:16PM
The only thought I had would be similar to what you put, except instead of making it a "On-Use", perhaps there is a way to tie it into fireball, (Via glyph perhaps) that after 5 or so unsuccessful critical attacks, the next fireball's crit chance is doubled until a crit is obtained.
Benjamin Apr 11th 2011 11:33AM
A potentially elegant solution to the critic streak issue is to give combustion back some of its old functionality, but maybe (gasp!), as a passive effect. Make each fireball non crit increase its crit chance by 5-10% or something.
Sounds to me like an opportunity for more interesting gameplay, just tweak the damage numbers a bit to compensate.
Trexxen Apr 9th 2011 3:00PM
My solution for Ignite Munching is to rework the entire ignite talent from the ground up. Instead, work it so that it is like this:
- Procs on every crit, periodic or not
- Stores a "percentage" of that crit as a DoT, say...10%.
- Lasts ten seconds (Plenty of time for even lesser geared fire mages to get a crit)
- Each time it procs again, the new ignite number is added on to the old one.
- To prevent obvious balance issues, the DoT is capped at, say...2.5x your current spell power, or something similar.
Thoughts?
SINisterWyvern Apr 9th 2011 8:50PM
I don't know why it can't be like many other dots and go "a more powerful effect is already active" meaning small ignites won't kill off the large ignites.
Jebediah54 Apr 10th 2011 1:15AM
That's already how it works, but the problem comes when you get two crits right in a row. Say you get a Hot Streak proc, so you finish casting your current fireball, then Pyroblast! and they both crit. The game can't recognize that short of a time frame so it adds one of those spell crits to your ignite (don't remember which, the one that hits slightly before or after), and the other one is just a free bit of direct damage that isn't applied to the DoT.
Or perhaps you get a crit in the first two seconds of Ignite moving up to its 6 second duration as opposed to its 4 second duration (when you get another crit to stack on ignite, it increases the duration to 6), the new crit completely overwrites your previous ignite leaving you with a smaller ignite than you should have had.
The biggest problem comes from the fact that DoTs can crit and munch your big crits in either of the cases, but they're trying to fix that in the next patch by making it so DoT crits don't trigger ignite.
Trexxen Apr 10th 2011 2:33AM
Well, that's kind of what the point of this new method is - it minimizes munching by having a "cap" that you can go towards, so any crits over the cap just extend the DoT, even if they munch.
akiva Apr 9th 2011 2:19PM
Something like this?
http://www.wowhead.com/item=31857
razion Apr 9th 2011 2:23PM
I'd rather have a stacking haste buff the longer we don't crit, that just keeps us casting faster and faster, weaving fire more dangerously and more recklessly, and if we hit a big enough ballpark then we get something equivalent to Cold Snap (but for fire spells). This means that you can still have that big unlucky streak, but when you do get that big unlucky streak it not only happens faster, but it resets a lot of big cool-downs like Flame Orb and Combustion, so it's like winning the lottery. And speaking of Combustion, I'm really more in favor of it just being a flat damage-increasing buff. Because that's what I'm after in a cool-down--increased damage. Why not just give it to us like that directly or turn it into a damaging spell?
My two cents on the issue.
Twilytgardnaery Apr 10th 2011 1:37AM
Love love love love LOVE this!
Shorten Apr 10th 2011 5:44AM
Impatiente Ardor - your consecutive non-critical spells increase your critical chance by 9% and your critical damage by 0.9%. Stacking up to 9 times for lasts 20 seconds, buff cleared by successively landing a critical strike.
Go Blizz, feel free to use that at will.
Docseuzz Apr 10th 2011 4:25PM
What's odd is that it would be even MORE valuable to NOT have crit rating, to elongate that powered up state....
Kadamon Apr 9th 2011 2:28PM
Skulls for the skull throne!
Qauren Apr 9th 2011 2:28PM
Damage increa... whaaa?
The point of a cooldown is it increases your damage by a lot for a short period of time.
A properly charged up ignite can hit quite easily for about 100k-120k over 10 seconds.
That's an extra 10-12k dps for 10 seconds, for ONE gcd...
That's before you combine it with Impact for AoE.
How much more damage do you -want-?
Faerevol Apr 9th 2011 2:48PM
The answer is all of it. :)
Wolftech Apr 9th 2011 2:58PM
If you played a mage (and from your comments, I can only assume you are a dirty 'lock) or even bothered to read the article, you would know that ignite is bugged. You would also know that because ignite is bugged and crit isnt working like it should, that the chance of getting a properly charged up combustion (you said ignite, but I am sure combustion is what you meant because combustion is the cool down, ignite is the dot) is as rare as a Hyacinth Macaw drop.
In the future, please read the article or at least know the basics of the class before you comment.
Skelemorris Apr 9th 2011 3:10PM
I agree! We need aaaaaaaall of the damage. All of it! ::::)
Bigdoggy May 19th 2011 1:29PM
ALL OF IT! IT SHALL ALL BE MIIINE!
Malsi Apr 9th 2011 2:48PM
I'm still mad at you for your lack of an article last Saturday! It was like Christmas morning, only without Santa, and without presents! Saturday is a very sad day when I can't imagine your sexy voice while you preach the doctrine of IHATEWARLOCKS.
Since you're the next best thing since they discovered cheesecake, I'm willing to forgive you, in fact I already have! Just beware the next time you decide to take a vacation on the most holy of days! I will demand justice which will be in the form of the following:
• More Warlock hate ( there wasn't enough this week).
• You are to be forced to listen to Rebecca Black's "Friday", since Justin Beiber wasn't enough.
• You must write three "Queue" columns in order to make up for missed day!
P.S. I still love you no matter what!
venslor Apr 9th 2011 3:25PM
I agree. Every Saturday, I get up, log in, and come to learn more about my favorite class. Last Saturday was nothing but sadness. I even check Sunday, more sadness. We deserve a note. haha
Christian Belt Apr 9th 2011 6:28PM
I apologize, profusely. My work schedule and family schedule has been nothing short of ridiculous of late, and last week's AB became a casualty of that nonsense. I'll figure something out so it doesn't happen anymore. On the bright side, though, it is good to be missed!