Tuesday, July 7, 2009

Aggro, and what happens when you have it

Whenever you get into combat, monsters automatically create a "hate list". They will attack whoever is on top of that list (exceptions apply). Everything that you do in combat moves you higher on the hate lists (aggro) of each and every monster in combat, for example, drinking a potion, using Bloodrage, healing, dealing damage, etc etc. Monsters will attack you if you are right at the top of their hate list, unless you are
1) In melee range (5 yards I believe) and at less than 110% of the aggro of the guy the mob is currently hitting (tank)
2) More than 5 yards away and at less than 130% of the tank's aggro.
Therefore, if you are not the tank, you don't want to be at the top of a mob's hate list. Here's a nice list of the threat modifiers of each class if you're interested.

What we should be interested in, however, is what happens when the fit hits the shan and you pull aggro from me (or your tank). In patch 3.0.8, all player taunts were changed such that they not only work in melee range, but work up to a range of 30 yards, like for example, Taunt. What's going to happen when you pull aggro from a caster mob is that I will taunt it back, and continue building hate on it since it is casting a spell at you and wont move out of my melee range.
When you pull a melee mob, however, it will turn away from me, and walk towards you. What happens here, is that I will taunt the mob, expecting you to either 1) stop hitting it NOW, or 2) Feign Death, Vanish, threat wipe, etc etc, such that the mob walks back to me and I can continue hitting it.
I'm sure I speak not for myself, but for every other tank since Wrath, when I say that people who pull mobs away will continue hitting the mob, harder if need be. If you have played a tank and have been in such a situation, you know that the next thing that will happen, is that said mob, will walk back to you for 1 or 2 seconds, and then turn around and look for the DPSer who didn't stop attacking to bash his/her skull in. At this point, there is very little you (as a tank) can do except to move there ASAP and blow a second taunt, right?

Moral of the story: If I taunt a mob back to me, stop hitting it!

Of course, blowing a second taunt is not the end-all be-all solution, since warriors have many ingenious ways of handling such ridiculous nonsense *ahemBahemZ*. I thank the people who have so far managed to do what it takes to have the mob come back to me, such as K. When forced into such situations, however, you are forced to be creative to find ways to handle it...

For warriors:
As always, don't panic. At this point, your Taunt is already on cooldown, and the first thing you should do, is to check for your Charge cooldown. If it's available, Charge that offending DPSer mob, and introduce him to your Shield Slam and/or Revenge. If not, check your Heroic Throw. If it's up, use it. That should buy you a couple of precious seconds to let your Charge or Taunt come off cooldown. If Charge and Heroic Throw are both on cooldown, Intervene the mob, and you will charge towards that DPSer, and now, Concussion Blow or Shockwave it before pressing Mocking Blow to shift the mob's focus back to you, and finally Taunt it back when your Taunt comes off cooldown.
Certainly I don't expect you to master this overnight, so practice, practice, practice. Encourage your DPSers to pull aggro so that you can practice (within reason of course). Make sure your healer is symapthetic too.

For paladins:
Since I don't play a paladin, the best I can help you with (to my knowledge), is to hope the mob isnt too far from you, and use Hammer of Justice on it to stun it, and you should be near enough by now to bring it back under control. If that fails, use Hand of Protection on the offending party member.

For death knights:
If you used Death Grip to pull, and your Dark Command is now wasted used on that offending DPSer, you can either use Chains of Ice/Icy Touch on it, or if your frost runes are on cooldown and you don't feel like blowing your Empower Rune Weapon, feel free to sit back and watch that DPSer die. No I'm kidding =D. Why are you still reading this!? Chase after the mob and make sure it doesn't kill that idiot who pulled aggro!

And finally, for druids:
There's really not much you can do save for using your Feral Charge on the mob that decided the mage in cloth was juicier. If you used your Feral Charge to pull (shame on you!!) or have no rage for it, there's nothing else you can do except chase after the mob and Bash it while waiting for your Growl to come off cooldown, or use your Challenging Roar.

Hopefully, this will give you peeps an idea of what aggro is like, and how messy it can be when people pull aggro all over the place, and some ideas of how to handle it when it happens. For DPSers, if you are reading this, you now know that a tank's job is not just to sit there and take punishment, so do whatever you can to make his/her job that much easier. He/she will thank you for it.

Monday, July 6, 2009

Tidbits

Had first DnD game on Saturday. My Barbarian was able to dish out an impressive amount of damage, and he hasn't even unleashed his full potential yet.

Still no Nightfall title for me... yet. Am hoping we will get it soon.

S is now 5 achievements away from the Red-Proto Drake. Looking forward to it.

Wednesday, July 1, 2009

PTR, and what it means for warriors

Or, as we all know it by its full name, the Public Test Realm. No, I'm not referring to the WoW PTR, yet. Having suffered through 2 browser crashes, this is the third time I'm typing this all out. GAH! Anyways, what I'm talking about, is Dungeons and Dragons 4th Ed. The last of my DnD group has recently come back from the US, and this means that we are able to restart the DnD game. I'm sure they are all as eager as me to break out their gear and start adventuring again. This new game will feature me as either a DPS Barbarian, smashing the faces of baddies, or as a prot-warrioresque Warden, defending the frontlines while my party reduces enemies to dust. Having met at our Dungeon Master's place for a "PTR" combat round last Saturday, I have gained some insights that will hopefully allow me to maximise my own characters when the real game begins this coming Saturday.

Now that we're done sidetracking, its time to move on to the real WoW PTR. As you may, or may not know, the 3.2 PTR is all the rage nowadays. With a multitude of changes promised, it's quite safe to say that warriors are one of the classes receiving the least overhauls. However, one of the dangers of writing about the PTR is that what is discussed here could very well be old news tomorrow. That notwithstanding, let's look at some upcoming changes that I know you'll all like:

Protection
  • Devastate now causes 60% weapon damage (up from 50%) plus 121 (up from 101) at max rank. Lower ranks increased accordingly.
  • Shield Specialization now has a 20/40/60/80/100% to generate 5 rage (up from 2) when a block, dodge, or parry occurs. (Old - Only proc from blocks)
Glyph
  • Glyph of Command - Increases the duration of your Commanding Shout ability by 2 min.
  • Glyph of Battle - Increases the duration of your Battle Shout ability by 2 min.
Item
  • Item - Warrior T9 Melee 2P Bonus (Berserker Stance and Battle Stance) - Berserker Stance grants an additional 2% critical strike chance, and Battle Stance grants an additional 6% armor penetration.
  • Item - Warrior T9 Melee 4P Bonus (Heroic Strike and Slam) - Increases the critical strike chance of your Slam and Heroic Strike abilities by 5%.
  • Item - Warrior T9 Tank 2P Bonus (Taunt) - Decreases the cooldown on your Taunt ability by 2 sec.
  • Item - Warrior T9 Tank 4P Bonus (Shield Block) - Decreases the cooldown on your Shield Block ability by 10 sec.

Blood Frenzy - 10% attack speed modifier now only affects melee attack speed
Armored to the Teeth - now Increases your attack power by 3 for every 108 armor value you have. (Old - 3 AP every 180 Armor)

There is also this, as quoted from here, by GC:

There are some mechanics we'd like to change with warriors, as I have already stated. Having to spam Heroic Strike is definitely one of them. Rage starvation is never fun (which is not the same as "I can ignore rage.") This is a slightly different argument that whether or not warriors have the stats they need to do the job, which seems to be the bigger concern in this forum at the moment. I am personally not particularly interested in who is the "easier" tank. I don't think any of them are significantly different from each other. You still have to know when to use your cooldowns, when to swap your gear, how to coordinate with your raid and when it's you that's the problem and not your class.

I think it's easy to argue against your point that warriors have not gotten a pretty hefty overhaul this expansion. We changed the warrior Protection tree a lot more than the paladin Protection tree or the Feral tree. We made you press Shield Block less often and Shield Wall more often. We changed Thunderclap and Devastate and Shield Slam and so forth. My point here is: don't dilute your arguments. I hear a lot of players saying that warrior survivability is lower than other tanks. Okay, that is feedback we can use. I hear them saying, as you did, that some of the mechanics still need to be updated. That is feedback we can use. Saying you are neglected or somehow other tanks got more changes than you or whatever... that is hard to use. We don't balance around "neglect." We balance around numbers. Theorycrafted numbers and simulations are valuable. Actual encounters with a boss are even more valuable.

Supplemented by GC with this:

I’m not sure that statement is accurate, but here is the problem. There are A LOT of warrior tanks. They are tanking every fight in Ulduar. If warriors were too low and if we buffed them, I don’t see how that would increase the numbers on the other tanks. I don’t think the conclusion to be drawn is that warriors are overpowered. I think the conclusion to be drawn is that warriors were the traditional tank and lot of established guilds have established MTs who see no reason to reroll the FotM. It’s not actually a goal to have 25% of each tank in Ulduar, but is also seems strange to buff the most popular tank. Won’t that just make them more popular? Again, don’t misinterpret that as GC sez suck it up warriors. It is something we have to keep in mind, however.

Block is a systemic problem. We're not sure we can make it a very compelling mitigation stat in a world where tank avoidance is so high and bosses hit so hard. However I will say that the Coliseum fights should focus less on the blow-your-cooldowns-or-die style of encounter.

Rage starvation is a problem. Frankly, we're not sure a model where you have to get hit in order to tank is that compelling anymore. Something that has come up a lot is changing rage (even for Prot) to damage done. This is a slight nerf to the PvP mechanic of being punished when you hit the warrior, but there are other ways to solve that as well. Again, we're talking a big change here. I'm not sure we're comfortable jacking with such a core mechanic before 3.2. (Source)


However, the most important change that I want to talk about, is this:

  • Block Value: The amount of bonus block value on all items has been doubled. This does not affect the base block value on shields or block value derived from strength.
  • On-Use Block Value Items: All items and set bonuses that trigger temporary increases to block value have been modified. Instead of increasing their block value amount by 100% like other items, they have all had their effect durations doubled. This applies to Glyph of Deflection, Gnomeregan Autoblocker, Coren's Lucky Coin, Lavanthor's Talisman, Libram of Obstruction, Tome of the Lightbringer, Libram of the Sacred Shield, the tier 8 paladin Shield of Righteousness bonus, the tier 5 paladin Holy Shield bonus, and the tier 5 warrior Shield Block bonus. (Source)
What this means is you'll see bigger Shield Slams (yay!) and more threat all around (from the buff to AttT). What this also means, is that there will be warriors who don't know how to tank, but are now marginally able to hold aggro, with this change. IMO, more threat is good, but this will increase the number of warrior 'tanks' who have no idea how to tank properly in the first place, but claiming they can tank.

That aside, I'm going to agree with Matt Rossi here, that all these changes are starting to feel more and more like a band-aid fix on warriors main tanking cutting edge content. Having been through all that, my warriors feel lacklustre when it comes to tanking Ulduar bosses. Sporting one of the lowest Effective Health (EH) values and lowest avoidance values among the four classes, I would say that if raid content continues this trend, warriors could be effectively dead by Coliseum. After all, if you can't stay alive, you can't tank. All is not lost, however, since "the Coliseum fights should focus less on the blow-your-cooldowns-or-die style of encounter", which probably means that warriors can go back to stacking EH, instead of avoidance like in Ulduar, in order to make them marginally useful. Having H in EH gear for Ulduar-10, I could already feel the pain of each boss hit, and had to swap in some avoidance gear to stay alive. That said, my primary gear set has been, and will continue to be, based on high EH, and maybe, just maybe, we'll see a reversion to EH being better than avoidance for future raid bosses.

Sunday, June 28, 2009

Woe betide me

Tried zerging Sarth +3D on late Friday evening/early Saturday morning with me tanking. Almost had him a few times, best attempts were 100k HP remaining, or 3%. A few wipes caused by me, some by others, kinda normal for a learning raid. Called it a day and decided to try another time.

Did Ulduar-10 on Wednesday evening again with me tanking. Wasn't so bad; cleared FLV, Razorscale, XT, Kologarn and Auriaya with a few wipes here and there. Bear in mind this was an impromtu raid with people who have never played with each other before, and with undergeared people and people who have never stepped into Ulduar before.
Continued Ulduar-10 Hodir, Thorim, and Iron Council yesterday evening. To say that it was a fiasco (on my part) was probably an understatement. Some wipes caused by me, some by others; a bit more than I would have expected, but then again its a learning raid for some of us. We ended up calling it at 4am. We started at 10.30pm, and only killed one boss in all that time. Not good. Someone called me a bad tank. Maybe I am, maybe I am.

Note to self 1: Don't ever try to tank when exhausted/sick. Bad for me, bad for everyone.
Note to others 1: Don't ask me to tank when exhausted/sick.
Note to self 2: Never agree to tank when exhausted/sick.
And the list goes on...

Friday, June 26, 2009

Parry, or rather, Parry-haste

Since you people have been so good, I decided to reward you with another post :)
Here's all you ever wanted to know about parry. What I'm interested in talking about, is this hidden mechanic all tanks used to know and fear (ok maybe not all, there will be some scrubs who choose to remain in the dark about important things): Parry-haste.

What Parry-haste simply means, is that when you parry an attack, the remaining time on your current swing is reduced by 40% of your weapon speed, unless this would result in a reduction to less than 20% of your swing time remaining.

For example, I'm using a 3.00s speed weapon, and have just started my weapon swing. At the same time, I parry a mob's attack. My swing speed for this next particular attack, will now be reduced by 40%, leading to a new speed of 1.80 seconds.
As another example: I'm using a 3.00s speed weapon, and I am 2.00 seconds into my weapon swing. At the same time, I parry a mob's attack. The remaining time on my swing timer is now 1.00s, and according to parry mechanics, this is reduced by 40% of my weapon speed which is 1.20 seconds. However, this violates the rule "unless this would result in a reduction to less than 20% of your swing time remaining," and therefore, my new remaining swing timer is instead reduced to 20% of my weapon swing speed, which is 0.60 seconds.
As a third example: I'm using a 3.00s speed weapon, and I am 2.50 seconds into my weapon swing. At the same time, I parry a mob's attack. 20% of my weapon swing speed is 0.60 seconds. Since I have gone beyond 20% of my weapon swing speed remaining, I will instead continue to land my attack 0.50 seconds later. It's like the game says (and I quote Disquette from EJ here): "Hey, parry can't reduce you below 20%, so just let the swing land like it's supposed to."

This has been extensively verified, especially at EJ here, starting from post #7, and I hope that clarifies it a little for you people new to this.

Lets reverse the situation a bit, and imagine you were swinging at a boss, and the boss parried your attack. (Yes I can hear many of you going "Aha!")
If the boss is one with an infamously fast weapon swing speed, such as Prince Malchezaar in phase 2, or Morogrim Tidewalker in SSC, you could find your main tank dead very very fast even without crushing blows, if you constantly attack from the front and aren't expertise capped. Now, in Wrath, crushing blows no longer exist, but raid bosses are hitting harder and harder. Imagine having your main tank take 12k 5 times in two seconds from XT-002 in Ulduar. Bad, isnt it?
I can't stress it enough: Never ever DPS from the front of a boss unless you absolutely have to, such as in Kologarn or Mimiron in Ulduar. You lose DPS, and risk killing your tank. If you absolutely have to do so, any extra expertise gear you have lying around will be doubly or even triply valuable.

As a tank, trying to reach the expertise cap of 13% for Parry is unwise and ill-advised, because it will more than likely gimp you in other areas. Strive for as high a number as you can get, without compromising other stats. Parries are to be expected, so try to minimise them as much as possible. Your healers will thank you for it.

Unorthodox tanking

A while ago, I mentioned that Unrelenting Assault was something of an unorthodox tanking talent. Matt Rossi has tried it out not so long ago in a spec something like this, and I can't seem to find his post again, but I vaguely remember what he said. According to him, it was fun, but the rage coming in didn't seem to be sufficient because his Revenge was stunning almost everything in sight.
Let me explain. What he basically did, was combine UA and Improved Revenge, such that he would be basically spamming Revenge every GCD.
Fast forward abit: I was in my second warrior, X, DPS'ing a Naxx10 raid, just killed Grobbulus, and about to proceed to Gluth. Since it was a raid mostly composed of friends, I volunteered to kite tank the zombies that Gluth spawns. Throwing on my tank gear, I realised, to the horror of horrors, that X has dual specced into PvE Arms and PvP Arms. "Oh well, how hard can it be, right?" was what I thought to myself. In we go, and to my surprise, I actually had a lot of fun spamming Revenge on the zombies.

Taking what Matt did a step further, using my same warrior X, I managed to tank the whole of heroic Gundrak in the cookie cutter PvE Arms spec. Threat output was slightly lower than normal, and damage taken was quite abit higher than I would have liked, but Revenge spamming was seriously fun (keep in mind that Thunder Clap and Cleave are essentials in holding mobs too, and even more so in this case). Kudos to B and Z and whoever else went with me (I can't remember, sorry).

As a final note, UA is NOT meant to be a main tank/progression tank ability. It can, however, provide tons of fun if you do choose to mess around with it in a 5-man or 10-man farming raid offtank (make sure your party members are sympathetic though!).

Midsummer Fire Festival

In case you're wondering where I've disappeared to for the past 6 days, I've been working on the Midsummer Fire Festival. Since this is the only holiday that I ever did, and probably will ever do, I decided to do a little something more this year. Last year, I only had 4 toons, that did most of the fires, while my rogue did all, inclusive of stealing the enemy capital cities' fires.
This year, I am proud happy to announce that all my 8 toons now have the achievement "The Flame Warden", along with the brazier and the pet from the vendor. It's taken awhile, but it was kinda fun while it lasted =D