Originally Posted by
Lucky_
It's also pointless to argue with someone who is so sure of his own righteousness, he gives no thought to even a possibility that he may be wrong. Nontheless, let me try hitting the head into that particular wall one more time.
We are talking about arms. In TBC, arms BF buff spec was hardest DPS spec to play in the game bar none. If you did not choose your skill ordering properly, you either fucked up your slam timings, or you burned too much rage on HS at wrong points and didn't have enough to upkeep MS>Slam rotation. Blind following of 45 rage rule was a road down into mediocrity and a replacement for SWP raids due to lackluster damage.
You chose your skills based on situation, or you watched your DPS plummet. Fury was obviously "hammer my head into the keyboard" since it played like ret does now - when skill lights up, you use it. But we are talking about ARMS here.
Rage starving was a viable approach because warriors were top dogs of PvP in S1-S4 damage wise and in general standings. Always. Denying this is ignorance of top order. In general, if warrior was allowed to stay on his target and hit it, it died. Quite fast in fact. Which is why rage denial and kiting were the main approaches to handling a warrior, usually ending up with warrior being CCd a lot of % of time spent in arena compared to all other classes.
Again, this had nothing to do with "lameness" of the approach, and everything with the fact that if warrior stayed on his target and knew how to play, it died. Fast. And the reason why warrior is hilariously OP right now is that juggernaut brought warrior into "completely unkiteable unless you have a frost mage" category, while keeping the "if warrior is on you long enough, you're dead" aspect.
Notably, the reason why dual betrayer TG warriors were not quite as successful in 2s as arms is now is because of kiting. If TG stayed on top of something while carrying good weapons, it died faster then now to arms. But back then warrior was actually kiteable, AND you could force defensive stance more easily.
Now, warrior is just "been outplayed? Hit charge" class. Which is the reason people faceroll with warrior-paladin to top of the 2s while having no clue.
This alone shows just how bad you are and how little understanding you have of warrior class in the past.
Points you completely ignore:
1. Charge and intercept are on DIFFERENT COOLDOWNS.
2. Charge in combat lets you gain rage, making it a net rage gain every time you charge rather then a net loss. Being followed by largely instant white it gives enough rage for execute on a spot.
This makes the world of difference. Before you really did need to wait the full CD on intercept before you could do it again. Finally you often lacked rage due to having to burn it on intercept and not getting enough in general during kiting, so white hit that followed intercept did not generate enough rage for meaningful damage. Now you can literally take away half of enemy healthbar after every charge with fair degree of reliability. And that is what breaks the class - it makes kiting the warrior almost more dangerous then just letting him sit on you.
Also, if you fail so much that your charge is on CD and you need to get to enemy yesterday, you can just switch to zerk, press intercept, switch back to battle. The rage change to stance dancing made sure you are not meaningfully penalized for it either.
This is where I admit my cluelessness. I completely forgot the snare removal part. Don't have that much need for it in PvE.