well, i'm fine with that.
Yeah, thats a good alternative. Charge should stay as it is.
I would have preferred the charge nerf over what they're doing with disrupting shout.
Strength Determination Merciless Forever
This is what a blizz blue said about charge and also they are putting pummel and disrupting shout on the same DR seriously blizzard its hard enough as a warrior to beat casters so now we going back to the good old days of free honor kill warriors for casters. fuck you blizzard always nerfing the wrong shit cos you listen to the 10 yr olds of wow not the proper players.
We're going to revert the Charge and Warbringer changes from the 5.4.7 PTR and make a different change. Here's some context:
We feel that Warriors are too disruptive vs casters in PvP at the moment. To a certain extent it's intended that it should be more difficult to get casts off if there's a melee DPS sticking to you, but Warriors just have too many options along those lines currently. That's part of the thinking behind the change to Charge: as a root, Charge would not interrupt casting, so it would be useful purely as a gap closer and rage generator, not as a way to lock down a caster.
We're reverting it because, although we do think it's a good change and something we're likely to revisit in the future, it's a bit too big of an overall change for 5.4.7. There's a bit of a ripple effect here; making Charge a root certainly accomplishes the goal of scaling back Warrior interrupts, but it opens up some secondary issues (such as "what happens when you Charge a target with Hand of Freedom active?") that we'd need some additional time to clear up. Put another way, we wanted to nerf Warriors' ability to disrupt casters, not their mobility, and at this point in time the Charge change would have been a nerf to both.
So instead, we're making a different change: Pummel and Disrupting Shout will have a 15-second shared cooldown. To be clear: Disrupting Shout will remain at its current 40 second cooldown, but you won't be able to use it within 15 seconds of using Pummel. Likewise, using Disrupting Shout will put Pummel on cooldown.
We may still come back to the Charge change in Warlords, where all sorts of other changes will have happened (especially to CC) that allow it to make more sense, and we can spend more development and testing time on making sure it doesn't have any unwanted side effects. For now, the shared cooldown on Pummel and Disrupting Shout will fill our original intention of making Warriors just slightly less difficult to cast against.
I'm sorry about the language but you have to be fucking joking Blizzard.
This new change is an even worse impact on PVE than the previous one. Many PVP warriors don't even use disrupting shout, but I bet just about every PVE one does. Ugh.
Crazy. Changing one of the if not the most iconic abilities in the entire game...9 years later. Makes no sense.
EVGA GTX 970 4GB SC | i5-4690K Quad-Core @4.5GHz CPU
Ripjaws 16GB 1866 (4x4GB) RAM | H80i Liquid Cooling System
Corsair RM 750W G+ Fully Modular PSU | ASRock Fatality Z97X Killer Motherboard
Cobra Series R Gaming Keyboard | Razer Deathadder Chroma Gaming Mouse
Samsung 840 EVO 120GB SSD | Seagate 7200 RPM 2TB HDD
ASUS Black 23.6" 1920x1080 2ms Full HD LED Monitor | Enermax OSTROGG GT Mid Tower
Then again two interrupts in PVP is pretty powerful, at least against spellcasters.
If anyone missed it.Pummel and Disrupting Shout will have a 15-second shared cooldown. To be clear: Disrupting Shout will remain at its current 40 second cooldown, but you won't be able to use it within 15 seconds of using Pummel. Likewise, using Disrupting Shout will put Pummel on cooldown.
warlocks: they have about 3 fears and cc effects from that pet that makes u sleep
mages: pet can use frost nova so can you and use about anoter 6 cc's
hunters: have disengages to stop damage and there leap of faith with a root and pets that cc
tbh warriors need 2 spell interupts to deal with all the bullshit spells casters have, guess wod is gonna be world of castercraft agian
I'm hoping they're gonna tone down the mass use of CC in WoD a bit.
- - - Updated - - -
I say this as an exclusively warrior player, this change IS for the better. CC DOES need to be addressed but nerfing charge isn't right in anyway. They need to remove access to shockwave and/or stormbolt for arms warriors.
Originally Posted by High Overlord Saurfangi7-860 @2.8GHz | Radeon HD 7770 | 8GB DDR3-1333MHz | Corsair CX 430W |
I didn't say that I am suddenly going to be fucked or I'm pissed off because I'm a bad player and won't be able to cope. I played warrior for a LONG time and I am fine with only having one interrupt. It's not a problem. This is a change I expected to happen eventually.
The problem is that they are nerfing PVE class mechanics MID-TIER for the sake of toning down DPS warrior control in PVP. Exactly as I said about the charge change, if they do this at the end of the expansion or start of a new raid tier, I have zero problems with it.
But changing something like this mid-tier when many guilds are still progressing on heroic SoO and especially Garrosh (a fight where double interrupts is very handy in a 10-man raid) is very irritating, especially when they were fine with the mechanic in every tier since the start of MoP and this is clearly a PVP-motivated change.
Sigh. I can see how now that they make a nerf that doesn't affect PVP warriors in a big way, you all turn around suddenly and it's like "Get out PVE noob, l2p!"
Funny how people turn their backs when it doesn't affect them any longer.
People will complain about anything.
"Disrupting Shout and Pummel now both share a 15-second cooldown when either ability is used. Disrupting Shout's 40-second cooldown remains unchanged but the ability will be unavailable for 15 seconds after using Pummel."
They should just make Disrupting Shout replace Pummel when you talent it, if they're doing this.
TBH it makes that talent tier more interesting for me — usually I just keep it parked on Disrupting because it's so much better than the other options. Now it's Piercing Howl by default, Disrupting iff I have a legitimate reason to interrupt in a radius vs. keeping a priority target locked up.
Entirely PvE perspective, btw.