Also on AOL
- Autos
- Technology
- Lifestyle
- Gaming
- Finance
- Entertainment on AOL
- Lifestyle on AOL
- Sports on AOL
- Travel on AOL
- More on AOL
Featured Galleries
Joystiq
© 2013 AOL Inc. All rights Reserved. Privacy Policy | Terms of Use | Trademarks | AOL A-Z HELP | About Our Ads

Reader Comments (Page 1 of 1)
1-08-2010 @ 3:18PM
Josin said...
I really think GC is overreacting to forum QQ with this whole decision. Prot warriors aren't sitting atop the Arena brackets, and most of us aren't going on mad killing sprees in PvP Battlegrounds. When other classes have gotten nerfed for PvP reasons, it's been because they were doing one or both of these. We're doing neither, generally speaking.
Simply being "frustrating" doesn't mean players need to be nerfed. Warlocks and rogues frustrate me in every PvP environment I enter. Are we going to take away their fears and stuns? No, probably not. Warrior utility is a very fun aspect of playing a Prot-specced Warrior. I LOVE the fact that I can draw attention away from my teammates by being an annoyance. If my cooldowns are properly handled, I can survive quite a lot of punishment. (Not as much as a not-OP-at-all protection-specced class that will not be named, mind you, but still quite a bit.) But the tradeoff for that survivability is that I'm not going to get a lot of attacks in, and when I do, they're not much to write home about.
Now, apparently some folks have found a way to gear that counteracts these damage deficiencies. To that I say, "Good for them!" They worked within the system and found a way to be effective damage dealers. Now, if they're being considered too effective, find a way to fix their solution to the problem, not "fix" US to undo their solution.
I'd rather see a limit put on ArPen (similar to the way Block Value was "fixed") than to have you guys mucking about in our abilities in ways that are sure to screw with PvE tanking, where we already operate at a deficit in nearly every measurable statistic. (We're not always last in a statistic, but we're never first.)
Reply