The Care and Feeding of Warriors: Comes the Cataclysm redux
Every week, WoW Insider brings you The Care and Feeding of Warriors, the column dedicated to arms, fury and protection warriors. Despite repeated blows to the head from dragons, demons, old gods, and whatever that thing over there was, Matthew Rossi will be your host.
Last year, we talked about Cataclysm. Since then, we've learned an awful lot about how it's going to affect warriors, starting as soon as patch 4.0.1 drops and changing a whole host of systems we've grown accustomed to. We've learned that the release date is my birthday. I'm pretty sure it's just a coincidence, but I'm still going to ride that coincidence for all it is worth.
What's interesting to me as we look at the coming expansion with another year's perspective is how much of what we heard about is going to be delivered. Yes, defense is gone, armor penetration is gone, reforging is coming, mastery is in. Rage normalization, a rebalancing of tanking to move away from AoE threat's being the expected norm, the transformation of on-next-swing abilities to become instant attacks. Three new warrior races, with the two expansion races and blood elves finally being able to be warriors. It was a heck of a laundry list and amazingly, Blizzard actually seems to be on track to deliver almost all of it.
We've discussed before that 4.0.1 will be a huge sea change for many warriors. I understand feeling some trepidation. I even share your feelings. There will be adjustments to make, and we'll see some changes in how things work that may hinder us in our chosen roles. If you're a DPS warrior, a PvPing warrior, a tanking warrior, I want to be honest and up front with you. You will lose some ability. Rage is changing, stats we rely on are leaving the game -- even the way our abilities are keyed for use is changing. You have every right to feel uncertain about it, and I'm not trying to minimize that. But let's be honest: From the time 4.0.1 drops until World of Warcraft: Matt's Birthday ships, it's not really going to matter if threat is wonky or DPS is low. Better it be now and fixed by launch, ultimately.
Once my birthday comes around, of course, you can be a female goblin warrior. I'm still hoping for immediate race change, because man, that looks badass.
So you want to AoE tank?
We've been talking a lot about tanking in World of Warcraft Matt's Birthday over the past couple of columns. While I don't want to dwell overmuch on it this time out, I did think the following thread should get a quick look. It's a discussion of Thunder Clap's damage and how AoE tanking is supposed to work in Matt's Birthday (OK, last time).
Ghostcrawler - Re: Thunderclap is too weak
That actually isn't an intended change. We don't want AE healing to be trivial. I'll use some examples:
A) Pile of 20 whelps. Go ahead and AE tank this and ask your dps to AE too. You probably don't even need Shield Slam.
B) One giant. I wouldn't use Thunder Clap at all on this, except as needed to keep the debuff up. We want Thunder Clap to be terrible for holding single targets. (I don't think many tanks would argue this point.)
C) A pack of 4 targets that you plan to burn down one at a time. Here is the biggest point of contention. Thunder Clap should be fine for establishing initial aggro (though Shockwave will be better), and it should be fine for keeping add #3 off of the healer. But you should feel like you have to go to town with single target abilities on add #1 that the dps are all focused on. Then you should switch attention to add #2. In Lich King, it was too easy to just hold this whole group with Thunder Clap spam, and to be fair, the dps would just AE as well.
D) The same pack as in C, but this time you decide to CC add #3 and #4. In this case, you should be able to live fine without Thunder Clap at all (unless you really need the debuff).
If you think about it, this isn't that different from what we had to do in The Burning Crusade. On bosses like, say, Dragonhawk in ZA, there were constant streams of hatchlings that needed to be AoE tanked down -- and frankly, back then, warriors were super-horrible at it. Even in the somewhat attenuated Cataclysm state, it should be a lot easier to do this kind of tanking than it was in BC. However, the next statement from this thread struck me as very interesting.
Ghostcrawler - Re: Thunderclap is too weak
On the one hand, this confuses me greatly. First off, I never expected to see Swipe nerfed. It's been better than TC ever since it was buffed to allow it to hit targets behind the druid; I don't get why now Blizzard suddenly cares how much better it is. I find the fact that Blizzard could effectively double TC's coefficient and that would merely bring it in line to be really, really odd.
I do, however, at least take some comfort that Blizzard's considering increasing tank threat. If you've tanked on the beta, you've noticed how strange and inconsistent threat can seem. It's hard to tell why. Are we at the mercy of rapidly diminishing combat ratings' having a powerful effect on threat stats like hit and expertise? Are we simply not putting out threat? Is threat just not scaling as well as DPS? Has there been a drop in pure threat when high-threat abilities were more or less normalized and threat was baked directly into tanking stances?
To be honest, I couldn't tell you. Some classes seem to pull threat a lot more easily than others. I had tremendous issues with warlocks and boomkin druids my last few heroic runs in both Stonecore and Halls of Origination; I don't know if it's losing the threat transfer from Vigilance or just plain and simple not having sufficient threat baked in to do the job. It could be something as simple as the new ability queue system keeping me from making use of my procs.
But based on the fact that Defensive Stance is seeing a buff in the latest PTR patch, I think it's safe to say there's some awareness of the threat inconsistencies. Going from 125 percent threat in D Stance to 200 percent threat should mean that the initial part of the pull for warrior tanks will feel less, "Oh please don't let them do anything stupid." This is an across-the-board chance for all tanks, mind you, which really makes me interested to see how each tank does. We're clearly not going to AoE down everything, but it shouldn't go back to the days of stepping down from tanking because the other guys are just plain better at it.
Bracing ourselves
Whenever 4.0.1 drops, it won't be the end but the beginning of an entirely new way to play our class. It's going to require us to pay attention, to understand that our new abilities won't be balanced for level 80 raids, and to adapt to some heavy changes. This is the most sweeping set of alterations to how classes work in the history of the game, far more so than either The Burning Crusade or Wrath of the Lich King. You are going to have to relearn your class. Itemization is going to change. Abilities are going to change. How threat is generated, how our resources work, how our rotations work -- you're not wrong if you're feeling a little daunted. But please don't be overly concerned. The goal is not to punish you.
Steps are being taken to keep things consistent. A lot of work is being done to standardize things like threat, resource management and damage. Yeah, you'll need to process a lot of change. World of Warcraft: Matt's Birthday (OK, OK, I really won't do it again ... the column's nearly over) is almost an entirely new game, but it does a good job of retaining what everyone likes about warriors. Even with all this change, your arms warrior feels like a warrior.
Check out more strategies and tips for warriors of all specs in Matthew Rossi's weekly class column, The Care and Feeding of Warriors.
Last year, we talked about Cataclysm. Since then, we've learned an awful lot about how it's going to affect warriors, starting as soon as patch 4.0.1 drops and changing a whole host of systems we've grown accustomed to. We've learned that the release date is my birthday. I'm pretty sure it's just a coincidence, but I'm still going to ride that coincidence for all it is worth.
What's interesting to me as we look at the coming expansion with another year's perspective is how much of what we heard about is going to be delivered. Yes, defense is gone, armor penetration is gone, reforging is coming, mastery is in. Rage normalization, a rebalancing of tanking to move away from AoE threat's being the expected norm, the transformation of on-next-swing abilities to become instant attacks. Three new warrior races, with the two expansion races and blood elves finally being able to be warriors. It was a heck of a laundry list and amazingly, Blizzard actually seems to be on track to deliver almost all of it.
We've discussed before that 4.0.1 will be a huge sea change for many warriors. I understand feeling some trepidation. I even share your feelings. There will be adjustments to make, and we'll see some changes in how things work that may hinder us in our chosen roles. If you're a DPS warrior, a PvPing warrior, a tanking warrior, I want to be honest and up front with you. You will lose some ability. Rage is changing, stats we rely on are leaving the game -- even the way our abilities are keyed for use is changing. You have every right to feel uncertain about it, and I'm not trying to minimize that. But let's be honest: From the time 4.0.1 drops until World of Warcraft: Matt's Birthday ships, it's not really going to matter if threat is wonky or DPS is low. Better it be now and fixed by launch, ultimately.
Once my birthday comes around, of course, you can be a female goblin warrior. I'm still hoping for immediate race change, because man, that looks badass.

We've been talking a lot about tanking in World of Warcraft Matt's Birthday over the past couple of columns. While I don't want to dwell overmuch on it this time out, I did think the following thread should get a quick look. It's a discussion of Thunder Clap's damage and how AoE tanking is supposed to work in Matt's Birthday (OK, last time).
Quote:
Bottom line, NO TANKING CLASS CAN AOE TANK ANYMORE. This is an intended change. It totally screws us over for existing content, but Blizzard seems unconcerned about that.
Bottom line, NO TANKING CLASS CAN AOE TANK ANYMORE. This is an intended change. It totally screws us over for existing content, but Blizzard seems unconcerned about that.
That actually isn't an intended change. We don't want AE healing to be trivial. I'll use some examples:
A) Pile of 20 whelps. Go ahead and AE tank this and ask your dps to AE too. You probably don't even need Shield Slam.
B) One giant. I wouldn't use Thunder Clap at all on this, except as needed to keep the debuff up. We want Thunder Clap to be terrible for holding single targets. (I don't think many tanks would argue this point.)
C) A pack of 4 targets that you plan to burn down one at a time. Here is the biggest point of contention. Thunder Clap should be fine for establishing initial aggro (though Shockwave will be better), and it should be fine for keeping add #3 off of the healer. But you should feel like you have to go to town with single target abilities on add #1 that the dps are all focused on. Then you should switch attention to add #2. In Lich King, it was too easy to just hold this whole group with Thunder Clap spam, and to be fair, the dps would just AE as well.
D) The same pack as in C, but this time you decide to CC add #3 and #4. In this case, you should be able to live fine without Thunder Clap at all (unless you really need the debuff).
If you think about it, this isn't that different from what we had to do in The Burning Crusade. On bosses like, say, Dragonhawk in ZA, there were constant streams of hatchlings that needed to be AoE tanked down -- and frankly, back then, warriors were super-horrible at it. Even in the somewhat attenuated Cataclysm state, it should be a lot easier to do this kind of tanking than it was in BC. However, the next statement from this thread struck me as very interesting.
We had already nerfed Swipe before I saw this conversation, because it was pretty far out in front of other tank AE dps. Thunder Clap's coefficient is something like 0.10 and that could probably be 0.20, which would bring it more in line.
We are also talking a lot about just buffing tank threat across the board, because we've heard a lot recently that it's still too twitchy.
We are also talking a lot about just buffing tank threat across the board, because we've heard a lot recently that it's still too twitchy.
On the one hand, this confuses me greatly. First off, I never expected to see Swipe nerfed. It's been better than TC ever since it was buffed to allow it to hit targets behind the druid; I don't get why now Blizzard suddenly cares how much better it is. I find the fact that Blizzard could effectively double TC's coefficient and that would merely bring it in line to be really, really odd.
I do, however, at least take some comfort that Blizzard's considering increasing tank threat. If you've tanked on the beta, you've noticed how strange and inconsistent threat can seem. It's hard to tell why. Are we at the mercy of rapidly diminishing combat ratings' having a powerful effect on threat stats like hit and expertise? Are we simply not putting out threat? Is threat just not scaling as well as DPS? Has there been a drop in pure threat when high-threat abilities were more or less normalized and threat was baked directly into tanking stances?
To be honest, I couldn't tell you. Some classes seem to pull threat a lot more easily than others. I had tremendous issues with warlocks and boomkin druids my last few heroic runs in both Stonecore and Halls of Origination; I don't know if it's losing the threat transfer from Vigilance or just plain and simple not having sufficient threat baked in to do the job. It could be something as simple as the new ability queue system keeping me from making use of my procs.
But based on the fact that Defensive Stance is seeing a buff in the latest PTR patch, I think it's safe to say there's some awareness of the threat inconsistencies. Going from 125 percent threat in D Stance to 200 percent threat should mean that the initial part of the pull for warrior tanks will feel less, "Oh please don't let them do anything stupid." This is an across-the-board chance for all tanks, mind you, which really makes me interested to see how each tank does. We're clearly not going to AoE down everything, but it shouldn't go back to the days of stepping down from tanking because the other guys are just plain better at it.

Whenever 4.0.1 drops, it won't be the end but the beginning of an entirely new way to play our class. It's going to require us to pay attention, to understand that our new abilities won't be balanced for level 80 raids, and to adapt to some heavy changes. This is the most sweeping set of alterations to how classes work in the history of the game, far more so than either The Burning Crusade or Wrath of the Lich King. You are going to have to relearn your class. Itemization is going to change. Abilities are going to change. How threat is generated, how our resources work, how our rotations work -- you're not wrong if you're feeling a little daunted. But please don't be overly concerned. The goal is not to punish you.
Steps are being taken to keep things consistent. A lot of work is being done to standardize things like threat, resource management and damage. Yeah, you'll need to process a lot of change. World of Warcraft: Matt's Birthday (OK, OK, I really won't do it again ... the column's nearly over) is almost an entirely new game, but it does a good job of retaining what everyone likes about warriors. Even with all this change, your arms warrior feels like a warrior.
Filed under: Warrior, (Warrior) The Care and Feeding of Warriors, Wrath of the Lich King, Cataclysm







Reader Comments (Page 1 of 3)
Josin Oct 8th 2010 1:05PM
I always look forward to seeing what new Warrior toon you're going to feature in the screenshot, Matt.
Kudos for the little green heathen. She looks dangerous.
Firestyle Oct 8th 2010 1:20PM
I'm excited for these changes - but, fearful every time I hear they are increasing tank threat. I'm just afraid they are falling into the QQ rather than simply making a QoL change.
Josin Oct 8th 2010 1:37PM
People have shown the parses, and between that and the excessive reports of being unable to hold threat off of equally or even lesser-geared DPS, Blizzard saw logic in increasing threat generation from tanks.
Aedilhild Oct 8th 2010 2:04PM
Ghostcrawler used the mot juste for (warrior) threat — "twitchy." Through the summer and early fall, aggro didn't correspond to the specific attacks warriors use to grab and hold, with disorienting and discouraging results. Nostalgia aside, it just wasn't rewarding. I tanked a beta heroic last night, and see where the PTR threat boost and possible Thunder Clap coefficient multiplication can close the gap and make tanking response optimal.
Sciarc Oct 8th 2010 2:11PM
I'm pretty sure that it's been demonstrated that the recent buff to tank threat on the PTR/beta merely brings tank threat in-line with current live values. As in:
Live DPS threat modifier: 70% (from threat reduction talents)
Live tank threat modifier: 200% (so tank threat is roughly 3X dps threat)
Beta DPS threat modifier: 100% (no more threat reduction talents)
New Beta tank threat modifier: 300% (3X dps threat)
Something like that.
Natsumi Oct 8th 2010 4:29PM
http://forums.worldofwarcraft.com/thread.html?topicId=27026329228&sid=2000
This may explain your tanking issues. Revenge currently LOWERS your threat when you push the button, which is funny as hell when you don't like the mage in the #2 spot, but is otherwise annoying.
Bikhai Oct 9th 2010 2:12PM
@Natsumi
Interesting bit of info there. I would say that it's a definite place for improvement. Saying Revenge lowers your threat is a bit misleading though. Keep in mind with the test they showed: even if you generate less overall threat killing a given mob using Revenge/auto-attacks, your threat per second is still increased by using revenge. You're generating less total threat, but you're also generating it over a shorter period of time because you kill the mob more quickly. Doesn't mean it doesn't need to be fixed, but that's how it looks to me.
Munitions Oct 8th 2010 1:30PM
That Worgen looks amazing.
Anyway, what scares me most about this is getting people to attack my target. I wonder how long it'll be before people start doing that themselves.
Jason Oct 8th 2010 1:52PM
Perhaps WoWInsider should do another Macro how-to so DPS can focus the tank and easily attack the tank's target. I know you can do that with key bindings, but that may be too simple for some folks.
Byron Oct 9th 2010 2:08AM
1. Bind an available, accessible key to 'Focus Target' in the Game Menu -> Key Bindings menu.
2. At the start of a run, target your tank and use the macro in step #1 above to set him to focus.
3. Create a macro that attacks the target of your focus:
/assist [@focus]
or
/startattack [@focustarget]
or
/use [@focustarget] BigNukeAbility1
or
/target [@focustarget]
/use BigNukeAbility1
or
/assist [@focus]
/use BigNukeAbility1
or lots of other variations, but you get the idea.
4. Bind that macro to an available, accessible key. Either use the wonderful Spellbinder addon to bind the macro directly to a key, or put the macro in a specific actionbar slot and bind that slot to a key in Game Menu -> Key Bindings.
5. Profit!!!!
Zach Oct 8th 2010 1:32PM
The release date is my B-day too, it definitely means something.
jbodar Oct 8th 2010 6:47PM
I could mean that you and Rossi were switched at birth.... *gasp* dun-dun-DUNNNNNN!
Anye Oct 8th 2010 7:59PM
Yes, it means something.
...
It means you and the author have the same B-day.
AltairAntares Oct 8th 2010 1:34PM
With the new buff to tank threat I'm much more optimistic about tanking- and speaking as a feral druid- not having my swipe finger numb when ever I tank will be super nice.
Overall I am much more optimistic about tanking then I am healing.
feniks9174 Oct 8th 2010 1:36PM
I heard something in vent last night from one of my guilds warriors that confused me.
Do DPS warriors have any CC whatsoever? Apparently there are horror stories coming from the beta about Fury/Arms getting insta-kicked from randoms because they have nothing to CC with. I know this was a problem in BC, but I was also under the impression that it was being fixed and you were getting -something- . . .
Josin Oct 8th 2010 1:43PM
No CC for warriors. Their CC is that things die faster with them around.
Firestyle Oct 8th 2010 1:51PM
Who needs to CC: when you are in plate mail and have a shield. That seems to be the viable solution to that problem. After one target is dead, the tant takes your add off you, you weapon swap and dps it down.
Samuel Oct 8th 2010 1:56PM
Unless you got 3 DPS warriors/dks in a group there shouldn't be problems with CC. Pretty much every other cass has something. Bizzard also stated that they don't want CC or die. If you are in a good gourp then you can do even without CC.
clundgren Oct 8th 2010 4:15PM
This is a viable concern, for sure, as anyone who played a non-cc class through BC can tell you. While Blizzard has stated that CC won't be mandatory, there is a risk that without it warriors could be insta-kicked. The fact is that there are a lot of players who are prone to snap judgements, and they might not wait a few pulls to see how much a good warrior offers to make up for lack of single target CC.
Mayhew Oct 8th 2010 4:22PM
I have some concerns about this, too. There were murmurs in the past about us getting some sort of CC option -- perhaps a revision to Intimidating Shout. However, this has not happened.
In my opinion, if we don't have a viable CC option as DPS, then we should be able to justify our presence through contributing substantial dps. However, this has not been my experience at all. I did the Uldum and Twilight Highlands quests before they gave quest rewards, so my warrior was running 5-mans in Deepholm greens and a few level-appropriate blues. However, I was doing substantially less dps as level 85 fury than I do as level 80 fury on live servers, and I was the far below the top two dps in the group. I'm not even sure if I out-dps'd the tank.
I really hope that I will soon find out that I was Doing It Wrong. If that's not the case, though, I could see some discrimination against dps warriors occurring.