Poster: Trow at 1/14/2006 1:23:37 PM PST
Subject: Warrior issues that MUST be fixed |
| |
Alright, since Tseric is off thinking up cool new ways to buff casters against us I felt it was time to make a post not asking what new stuff we need but what things need to be FIXED before the other classes get their buffs.
1.)
Execute no longer works with Sweeping Strikes. No damage is delt to the secondary target BUT it still eats up a SS charge.
2.)
The pretty new graphic for retaliation HAS TO GO. The idea behind retaliation is that the attacker is so bent on attacking you that you trap them when you pop retaliation. Why was the new graphic implimented? When a warrior pops this melee just stop attacking him because they can see spinning glowing swords, wasting the cooldown. Now we have 2 useless cooldowns in PvP and they're on the same 30 minute timer. It's not like melee couldn't see the retaliation before 1.9, our hands started to glow red.
3.)
Charge intercept bugs out when we are slowed by any effect. Basically if we are slowed and we charge someone we charge off to the left or right of teh target for no reason and by the time we recover the stun effect is gone and we've pretty much screawed ourselves. Is this really that hard to fix? The follow command keeps people right in someone's back pocket. Can't the command be programed to impliment a "follow" command on the target and have it stop when we get into melee range of the target at which point the stun hits. Once the stun hits the "follow" command stops. Is this too hard to program?
4.)
I haven't tested this yet but I've heard this from many warriors that I have talked to, overpower is not critting as much. There are reports on the forum that the crit % on overpower is capped at the talent's 50% chance and does not factor in the players crit %.
5.)
The fury tree was nerfed this last patch? Why? Can we get an answer on this because 1.9 nerfed fury far more than it did arms. Was unbridled wrath really that overpowered? Is anything being done to compensate fury users?
|
| | http://forums.worldofwarcraft.com/thread.aspx?fn=wow-warrior&t=736255&p=#post736255 |
| |
Poster: Tseric at 1/14/2006 1:57:04 PM PST
Subject: Re: Warrior issues that MUST be fixed |
| |
Q u o t e:
Execute no longer works with Sweeping Strikes. No damage is delt to the secondary target BUT it still eats up a SS charge.
The prior issue with this is that SS was allowing Execute to hit players who weren't below 20% percent. There is conflicting functionality with this and the devs didn't want to implement a fix that would buff or nerf abilities. I will discuss more with them the results of this fix. As it stands, there is a different fix slated for a future patch.
Q u o t e:
The pretty new graphic for retaliation HAS TO GO. The idea behind retaliation is that the attacker is so bent on attacking you that you trap them when you pop retaliation. Why was the new graphic implimented? When a warrior pops this melee just stop attacking him because they can see spinning glowing swords, wasting the cooldown. Now we have 2 useless cooldowns in PvP and they're on the same 30 minute timer. It's not like melee couldn't see the retaliation before 1.9, our hands started to glow red.
I don't disagree completely, but you are taking this from solely a PvP angle. I will mention the effects you have stated.
Q u o t e:
Charge intercept bugs out when we are slowed by any effect. Basically if we are slowed and we charge someone we charge off to the left or right of teh target for no reason and by the time we recover the stun effect is gone and we've pretty much screawed ourselves. Is this really that hard to fix? The follow command keeps people right in someone's back pocket. Can't the command be programed to impliment a "follow" command on the target and have it stop when we get into melee range of the target at which point the stun hits. Once the stun hits the "follow" command stops. Is this too hard to program?
Again, an issue with conflicting functionality. Charge/Intercept is not intended as something to break a snare, but is not prevented by a snare. Probably being treated as a bug, but I will try to get more info on this.
Q u o t e:
I haven't tested this yet but I've heard this from many warriors that I have talked to, overpower is not critting as much. There are reports on the forum that the crit % on overpower is capped at the talent's 50% chance and does not factor in the players crit %.
Not critting as much since 1.9? or for some time?
Q u o t e:
The fury tree was nerfed this last patch? Why? Can we get an answer on this because 1.9 nerfed fury far more than it did arms. Was unbridled wrath really that overpowered? Is anything being done to compensate fury users?
Bloodthirst was buffed as compensation for enrage being reduced. The over-all DPS potential for 31-point fury warriors was maintained. Unbridled wrath was generating rage from rage-consuming abilities, which was not something the devs wanted to be occurring. The change was to make rage generate from rage-generating attacks (normal swings).[ post edited by Tseric ]
I spell emm. ayyy, child. ennn....
|
| | http://forums.worldofwarcraft.com/thread.aspx?fn=wow-warrior&t=736255&p=#post736396 |
Poster: Tseric at 1/14/2006 11:36:52 PM PST
Subject: Re: Warrior issues that MUST be fixed |
| |
Q u o t e:
In PvP, I am enraged most of the time ( which is both a good and a bad thing ) and with the new enrage I saw my overall DPS be quite lower than what it was before.
You were enraged most of the time, which is exactly why the damage output of enrage was reduced. Obviously you are going to see your DPS go down. You and many others were maintaining a constant state of enrage and dealing a crap-ton of damage.
Now go ahead, "pop" your jokes :P
Observational bias is part of science, life, etc.
|
| | http://forums.worldofwarcraft.com/thread.aspx?fn=wow-warrior&t=736255&p=#post737458 |
