Arcane Brilliance: The state of the Mage

This week, Arcane Brilliance would like to address all Mages everywhere, from level 1 to level 80, in a spirit of optimism and brotherhood. We only have a little over six weeks left before the release of Wrath, and we need to come together as one Mage...one freakish, mutant Mage with a million arms and legs and wands sticking out all over the place...one giant, horrific ball of flesh, cloth, and silly hats that could hurl a Pyroblast roughly the size of a planet. Let's do it! I'm pretty sure if we all stand facing each other like so...and then blink at the same time...oh sweet mother of all that is good and pure...that's awful...just...just nevermind. We'll clean that up later.
My fellow Azerothians...
We've been through a lot these past four years and change. There was the great respeccing crisis of Molten Core. A string of Blink mishaps. The table-ninjaing scandal of '07. We've Fireballed our way through the scourge invasion, the rise of the silithid, the opening of the Dark Portal. We've killed Ragnaros, Kel-Thuzad, Nefarian, Onyxia, Illidan, and on like 14 separate occasions, Kael'thas Sunstrider. We've emerged unscathed from the bloody, neverending Southshore/Tarren Mill conflict (though countless questgivers and flight masters were lost), and moved on to more organized, focused wars in the various battlegrounds. These were battles with a clear purpose, an attainable goal, and with the notable exception of Warsong Gulch, a firm timetable for troop removal.
Fortunately, throughout all of these conflicts, the economy has remained strong. Seriously, have you seen the price of Runecloth lately?
So now, my fellow Mages, it is time for us to look closely at the state of our glorious class. We know where we've been, and where we are now. We're fully aware of our past, and we know where we want to be as the future rushes toward us. Let's take a constructive look at our unresolved concerns, and try to foretell our place in the coming expansion. Follow me through the break, won't you?
Ok seriously, we all have some worries, right? The beta has given our class a lot of cause to be optimistic--even excited--about where we're headed. Still, there are some nagging doubts. The gap between where we are and where we want to be is narrowing, to be sure, but is still sizable.
We're suspended in a state of flux at the moment--along with every other class--as Blizzard continues to balance and polish. I fully expect this "polishing" to continue even after the expansion is released, so this analysis is going to have to be adaptive and flexible. We'll look at the issues Mages face, and some of the possible solutions. We'll also note the positive changes, to give us a more complete view of our class as a whole.
Overall Concerns
- DPS balance:
Blizzard has posted a few things that lead me to believe they share our desire to see Mages become an elite DPS class again, on some level at least. Though Blizzard's policy of keeping the classes balanced means that we may never again be considered the top DPS class, we can at least hope to be in the same ballpark as other DPS classes, to at some point see the day when a good Mage can top a good Warlock on the damage meter, if they play their cards right.
It will be nearly impossible to gauge the status of this concern until more of the class-balancing is finished, but I can say that in the beta currently, things are encouraging. Our damage output is high--higher in relation to other DPS classes than I can remember it being since the vanilla WoW era. The best part? It's high across all three trees, which means Mages may finally be able to pick their spec based on personal preferences and play-style, instead of based on the accepted raiding tree of the day.
- Frost/Fire-immune targets:
The catch-all solution Blizzard has offered us to this problem is the introduction of Frostfire Bolt. This is a simple fix, and is largely successful. It benefits from any talent that affects either Fire or Frost spells, and so is a viable nuke when presented with a mob that is immune to whichever tree we've specced into. The problem I see with the spell is that, unless you spec into an elementalist build to take advantage of talents from both trees specifically to buff your Frostfire Bolt spell, the spell just isn't useful for anything else. And to be honest, no matter how you distribute your talents right now in the beta, an elementalist build simply isn't nearly as worthwhile as speccing into one of the other three trees, damage-wise. Not to mention that a spec that requires you to cast one and only one spell over and over is incredibly dull.
Overall, Frostfire Bolt is a simple solution to an old problem for Mages, but not much else.
- Mobility:
With the introduction of several short-cooldown, high damage, instant-cast options, Blizzard has gone a long way toward fixing this problem. Our DPS still dips considerably while moving, but not to the point of irrelevancy. Spells like Arcane Barrage, Deep Freeze, Living Bomb, and multiple procs that allow for occasional short-cast or instant cast nukes have made casting on the go an increasingly attractive proposition for Mages.
- PvP viability:
Step 1: Spec Frost.
Step 2: Don't fight Warlocks.
Blizzard has stated their desire to see more specs become viable in more aspects of the game, and this is one area in which Mages could really use a bit more flexibility. Our increased mobility--as well as some very significant improvements in the organization and implementation of the talent trees--has really increased the viability of the Fire and Arcane trees as possible PvP options. Survivability has gone up, mobile damage output has improved, and escapability options have become more plentiful and effective.
The Arcane tree has gained escapability in the form of instant-cast Invisibility, survivability options in the form of the massive upgrade to our spell resistances provided by Magic Absorption, and rock-solid instant-cast damage in the form of Arcane Barrage.
The Fire tree, though still overly fragile, has gained some game-changing mechanics in the form of knockback abilities like Blast Wave and Living Bomb, and Fire Mages' burst damage output has improved. This still appears to be the least viable PvP option for Mages, but at least it won't be entirely useless anymore.
Also, the Frost tree is still really, really good. Mirror Image looks to be a PvP godsend for every spec. And yes, Warlocks are still giant pains in our collective hindquarters.
- Itemization Problems:
Ideally, if we're going to be forced to waste item stats on spirit, we need something to help us take advantage of it. Honestly, I'm still not sure why spirit hasn't simply been converted into Mp5 and health return become an innate flat percentage across all classes. If it's going to stay a Mage stat, and our gear is going to have it at level 80, we need talents or spells that reflect a need for it. Otherwise, we need more Mage-appropriate gear.
Though I still love this spell and have been known to pop it even out of combat, simply to walk into the barber shop or whatever with my own entourage, it has some issues. The damage has been scaled back significantly, which was probably needed, since the original damage was so high and so buggy. The problem with this is that the spell does not scale at all with your spellpower. It doesn't benefit at all from any of our talents. As our gear improves, the spell will become less and less viable. It needs to scale with spell damage, and the spells cast by the copies should benefit from talents that would affect the kinds of spells they're casting. It's no fun to press your big DPS burst button in a boss-fight and then watch all of your copies' spells get resisted because they're rolling with no spell hit rating. As it stands now, Mirror Image will be loads of fun for a fresh level 80 Mage against lower-level targets, and less so as you prgress through the end-game content. That's not good enough.
- School-specific Concerns
Arcane Tree
- Arcane Blast still sucks:
At least, not more than once in a row. They've stated that their intention is to force us to avoid spamming a single nuke spell, to make us switch things up. They want pressing the Arcane Blast button once to be a good idea, pressing it twice to be a bad one.
Frankly, that's just stupid.
I can understand what they think they're doing here, and I agree that pressing one button over and over again is no fun. The problem is that pressing the button once was never that great, it was ramping up the damage over several casts that was the good part. You ramped up the damage, you took the mana penalty, and you learned to rotate it with other spells so that you could maximize the damage and minimize the mana burn. It was one of the more interesting mechanics we had. It certainly beat spamming Fireball or Frostbolt.
Blizzard even introduced a very fun proc mechanic in this expansion--Missile Barrage--that depends on Arcane Blast spam to function. It provided a built-in break in the rotation, and coupled with Arcane Barrage made for a fantastic, interactive, powerful Arcane spell rotation that just felt right.
Now, not only is Arcane Blast too expensive to cast more than once, it's not even really worthwhile to cast the first time. Missile Barrage has been rendered useless, and a spec that was feeling like a very viable standalone spec now has no primary nuke.
What I hope is happening here, what I pray is happening here, is that they're just over-nerfing a spell for testing purposes, and then gradually reducing the nerf to a more acceptable level. The mana penalty needs to be less than 100%, or the damage increase needs to be increased to match the penalty. Mages will manage the rotation themselves, Blizzard; you don't have to force us to play a specific way by instituting an absurd penalty for casting the same spell more than once in a row. Give your player-base a little credit. If you don't want Arcane Blast to be our primary nuke, what's the spell good for? Also, what spell would you prefer we use? Arcane Missiles is already mana-prohibitive, and Arcane Barrage is an instant-cast spell with a cooldown. That's...well...that's it for single-target Arcane damage spells, really. How would you have us play, Blizzard? If Arcane Blast isn't our nuke, what is?
- Arcane as a standalone tree:
The expansion may just change this. If the Arcane Blast issue can be resolved, this tree can absolutely provide a viable PvE or PvP alternative to Fire and Frost. Almost every talent in the tree has been improved, and the new talents are almost universally good. The tree has the potential to be very fun to play, and provide viable PvP and PvE damage.
Fire Tree
- Survivability:
The expansion won't change this much, but the advent of knock-back mechanics improves the situation a bit, and the increase in DPS due to things like Hot Streak helps to balance the continued glass-cannonism this spec appears relegated to.
- Living Bomb
Frost Tree
- Raid utility:
If you want to discourage spamming a single spell, why provide a mechanic like this spell, which in its current form provides a two-charge freeze effect on any target, even raid bosses? Those two charges are currently best spent on two consecutive Frostbolts. This means more of what Blizzard claims to want to avoid: the one-button Mage. This effect needs to be changed to a short duration debuff, which may only allow for two spell-casts anyway, but doesn't discourage you from coupling a Deep Freeze or Ice Lance with your Frostbolts.
In the current build, though the tooltip doesn't reflect it, this spell has had its damage component removed completely. It is back to being a flat stun talent usable only on frozen targets and limited by a 30 second cooldown. No response has been given to multiple queries on the forums, so it's difficult to say whether this is intended or simply a bug. My guess is that it's intentional, along the lines of the 300% mana penalty they applied to Arcane Blast in the last build. I think Blizzard wants to see how Frost Mages fare without the damage portion of the spell.
I'm going to try to be reasonable about this. Perhaps it is unintended. I'll wait for the next build, see if the spell still does no damage.
When that build comes, and the spell still only stuns, I cannot be held responsible for my actions.
On that dark day--and this is a promise--I will type things. They will not be nice things. I will type firmly, and without remorse. I will press keys loudly, and in rapid succession. My words might even be...inflammatory. They may even be italicized, or punctuated with exclamation points. Perhaps both.
I have lain down the gauntlet, Blizzard. Don't test me.
I will make this keyboard sing the song that ends the world.
In conclusion
You may not have been able to tell, but believe me when I say that I like where Mages are going. With a only few small tweaks, the future could be very bright, mainly because it will be lit with the burning corpses of our enemies. Our class is still due for some polishing, and we can hope that it will emerge from that process all the shinier. Playing a Mage in the expansion has the potential to be very exciting. Our new spells and mechanics are largely excellent. Damage-wise (which, when you come right down to it, is really the most importnant issue for Mages), we could end up being very powerful, assuming a solid position as one of the top DPS classes in the game, if not the top DPS class in the game.
If you happen to be in the beta, be sure to give as much constructive feedback as you can both in-game and on the Mage forums. If you aren't in the beta, download the PTR client and test the new talents, then provide as much PTR feedback as you possibly can.
Together we can Blink forward (or backward, whatever) into the future--a future in which we can hold our heads high as we turn things into cats and snakes and then blow those cats and snakes up.
Filed under: Mage, (Mage) Arcane Brilliance, Talents, Classes, Raiding, Features, Expansions, PvP, Economy, Blizzard, Analysis / Opinion, Wrath of the Lich King






Reader Comments (Page 1 of 3)
Tweaky Sep 27th 2008 5:25PM
Can I get an AMEN!
Hope Sep 27th 2008 7:06PM
See if blizzard is any better at reading this than they are the beta mage forums, cough ghostcrawler, cough.
Ghostcrawler, what an appropriate name, a ghost, that explains the long periods where nobody sees or hears from her, and crawler, like an insect. Harumph!
Chilblain Sep 27th 2008 5:27PM
Great job of summing up the current Mage issues. I was really hopeful when I got in the beta with my level 80 premade a few builds ago. I spent so much time re-spec'ing and trying different talent builds; I couldn't decide how I wanted to play because ALL the trees were so good! But Blizzard has slowly painted all Mages into a corner again, and we're back to the same place we were before Wrath. I wish I could share your optimism, but I'm really struggling to see what their goal is here. We have been complaining abut the same issues time and time and time again, and we are no closer to solving them.
Corey Sep 27th 2008 5:29PM
I would just like to say..... THANK YOU SOOOO MUCH!!! Gah.. I was so incredibly worried for awhile there! No one was saying anything about mages.. for a sec I thought they were just sweaping all the concerns for mage under the carpet, I was tired of reporting and writing emails and posting forum topics about all the issues and boy did you ever narrow them down! YOU ROCK!!!..
Oh and to add a little from my experience.. arcane and fire spec = all my mana go bye bye and im rocking T6 comparable gear..
I wish blizzard would do something about all the new goodies, aka. procs, costing an arm and a leg in the rotations..
hot streak & missle barrage.. awesome procs but maybe a reduction on the mana cost of the spells aswell with the procs would help us keep some of that precious mana that goes fast in various encounters.
jurandr Sep 27th 2008 5:34PM
EXCELLENT post.
11/10
Jim Sep 27th 2008 5:39PM
"Here's the problem: Mages don't really use spirit. When you're constantly casting, a mana-return mechanic that requires you to stop casting for more than five seconds is a bad idea."
Mages certainly do use spirit, and when you're running T5 Arcane with Mage Armor, having 500 MP5 while casting is better than sex.
Aigarius Sep 27th 2008 6:01PM
Amen! Every raiding mage must know the true value of spirit. Mage Armor is the raiding armor. There are only a couple fights in T6 where you can afford to run Molten Armor - when you are on the decurse or parasite duty and can only do damage in short bursts.
Noelor Sep 28th 2008 5:04AM
And of course, the tree with an "inexplicable" talent for boosting spirit gets even more from it, because of Arcane Meditation immediately below. In fact, with the new glyph for Mage Armour, a mage with both the armour and talent might get more mp5 from spirit than from pure mp5.
Moage Sep 27th 2008 5:54PM
I think blizzard is just messing with mages...much how a 5 year old would let his ant farm become well expaneded then for his own amusement take the ant farm and just shake it to h*ll .
emil Sep 27th 2008 6:05PM
The single greatest opening paragraph in the history of wowi, evar.
Aigarius Sep 27th 2008 5:59PM
Clearly you have no idea what you are talking about. The Arcane Blast was never intended to be the primary nuke, it was a mana dump. Arcane Missiles were intended to be the primary nuke. Now with rebalancing Arcane Barrage is the primary nuke and you fill the gaps in with Arcane Blast and Missile Barrage procs. A very powerful and interactive rotation, if you crunch the numbers.
And Fingers of Frost are best used to cast one Frostbolt (that you are already casting when you notice the debuff) and then follow up with a Deep Freeze and then keep spamming Frostbolts onto the deep frozen target. Also the Water Elemental brings added complexity to the spec.
turtlehead Sep 29th 2008 4:13AM
"The Arcane Blast was never intended to be the primary nuke, it was a mana dump. Arcane Missiles were intended to be the primary nuke."
Agreed, and they finally made missiles worthwhile. The tree is still a godawful mess though, and Blizzard continues to flounder with it. The 300% is definitely overkill.
The problem with the mana dump idea conceptually is that it's either a) overpowered with enough support to go flat out all the time or b) not worth using at all, ie., being arcane when the other trees give better DPS. They blew that BC and while Lich is looking better it's still off.
Covnam Sep 27th 2008 6:04PM
How was missile barrage changed to render it useless?
Kadamon Sep 27th 2008 6:47PM
Heh. I always did love that Penny-Arcade comic...though I'm gonna have to agree with the Deep Freeze thing.
I already know I'm speccing Frost again when I level, and I hope Deep Freeze isn't pointless.
Matazuma Sep 27th 2008 6:48PM
/clap
Amazing post once again Christian.
Deep freeze better be a bug if not........the nerdrage will flow like a river!!
Sarius Sep 27th 2008 7:06PM
I've asked before but I'll ask again: Did they fix the Ghost Hit in beta?
turtlehead Sep 29th 2008 3:44AM
I've not run the numbers to test, but it's almost 100% likely fixed or will be. Plan around it going poof.
Going to be rough for my frost mage raiding when the content patch hits. Got to shed haste and +dam to recap, which is going to make him a joke against fire. Been milking that low cap in a big way.
Meresavant Sep 27th 2008 7:39PM
Guys its all about keeping the status quo,... can't you all see?
For those that can't let me explain what I mean...
What blizzard are doing is nerfing one class, then they read everything everyone writes about what class they are going to re-role to and then in tern, nerf the new popular class.
Reason?
Well logic says that if they keep doing that then everyone will eventually end up back at their old respective classes and they would have suceeded in bringing in a whole new wave of abilities without upsetting the current status Quo.
Ok, so its not exactly a means to helping everyone get what they really want which is lots of exciting new toys that are fun. But it is a way of achieving balance I suppose. lol
rydolomo Sep 27th 2008 7:55PM
Blizzard don't read what everyone writes. These nerfs are decided in a boardroom by suits who've never played wow.
Hangk Sep 27th 2008 7:42PM
If Warlocks were Mages...
...I'd complain that we can't put out decent raid DPS as Demonology, that we can't survive a PvP beatdown as Destruction, and that we have no burst damage as Affliction.
...I'd be highly offended that there are some circumstances in which other classes can sometimes out-DPS us. Cos we should do more DPS than anybody, always. Why? Because we should, that's why. Just shut up and accept it.
...I'd complain about our raid utility for some reason, despite the fact that we have a number of highly useful abilities that make our class a key component of any raid.
...I'd complain about our lack of representation at top Arena rankings, utterly oblivious to the fact that every class other than Warriors, Rogues, and Druids is in the same position.
...I'd bitch endlessly about our counter-class and how, darn it, they have such an easy time beating us! Who do they think they are, our counter-class? (Wait. I already kinda do this. Never mind...)
...I'd carry on as though my class was somehow greatly underpowered, despite our success and popularity in every aspect of the game other than high-level small-team arena.
...I'd carry a permanent grudge that ours is not the only class that can wear robes, cast spells, and look cool while doing it. Who do they think they are?
Man. I'm glad I'm not a Mage. Cos with all that complaining to do, how would I find time to ever play the damned game?
(To be fair, Mr. Belt, this article of yours is much less angst-ridden than some you've written. But you must admit that there are times when you do seem to perpetuate the stereotype of the "QQing Mage" pretty enthusiastically.)
Ooops, I've just outed myself as a Warlock on a Mage thread. /use Greater Flame Protection Potion...