Disappointed @ the Patch Notes for 11.1 and Prot

Classes Warrior
1

So…you ignore Brewmaster and Blood DK who have been suffering all season and then you BUFF Prot Pally (who really really didnt need it) and then you NERF Prot Warrior…? You take the best 2 tanks of the season, buff 1 and then try to DUMPSTER the other all while ignoring the much weaker ones…

" * Developers’ notes: Protection Warriors are currently constantly flooded with Rage which undermines rotational defensive decision-making and encourages constant dumping of Rage into Ignore Pain to maximize effectiveness. We’re taking a pass at reducing Protection’s overall Rage generation to make decisions on when and how to spend it more meaningful, without reducing Protection Warriors’ ability to tank effectively."

Warriors LIKE getting into a big pack on mythic Plus and and doing big pulls. We NEED the rage to be able to survive the encounters so that we CAN consistently activate Ignore Pain and keep Shield Block on CD. That is LITERALLY how you designed our class. It also makes the class fun to play. So I’m sorry, why exactly do you think we need more complex decision-making in our tanking? I’ll wait…

Dumpering rage generation makes us have to pull smaller. I am only fine with this if you go ahead with your proposed changes to REMOVE the timer from M+ and go to a death count.

8 Likes
2

I will admit it was one of the more surprising things they have in store for Warrior. It really doesn’t make sense to say “We think Prot warrior is good,” then proceed to nerf it rather harshly.

8 Likes
3

is it me or did they change the revenge spell?
was able to spam it easy now… ?

4

It’s only spammable in lower keys or really big pulls. In higher keys the damage is so high pretty much all your rage is going to defensives and revenge is only used on a free proc. That’s the funny part about ‘we want warriors to have to decide’… there is no decision. Shield Block is #1, Ignore Pain #2, Revenge #3… and that’s it. Everything else is CDs, procs, or situational.

8 Likes
5

The whole thing seems to go against class fantasy. All three specs of warrior should be blood thirsty and fast moving, wading into waves of baddies with reckless abandon. They could target prot damage or reduce sturdiness a little without “slowing” them down by throttling rage. Big L
Prot shouldn’t be hamstrung by rage. This change will 100% force people to stay with Mountain Thane and Colossus will be even more difficult to find an excuse to play.

2 Likes
6

Everytime they try to reduce resource generation on pretty much any spec there should be a big " are you sure" button, followed by an even bigger " are you really sure?" Button after you click yes on the first one

5 Likes
7

This sums it up in a nutshell. Lowering Rage gen, and making Ignore pain 30% more per cast is not an equal trade.

3 Likes
8

Honestly with the apparent tank shortage, nerfing any tank seems like hurtful move to the entire wow community.

5 Likes
9

These …challenged people should be focusing on bringing BM and BDK back up to playable.

BM has been a hot dumpster fire since Dragonflight when they NERFED whatever the stagger-clearing brew was called to 2 instead of 3. I mained a BM throughout Shadowlands and LOVED doing keys for the sheer amount of mob control I had …my survivability was already iffy @ times during big pulls but they pretty much got rid of that entirely when they cut the brews down.

I dont know much about BDK but I know that healers hate healing them now which wasn’t the case for years and years. Some spikiness in BDK is probably somewhat fun to them but not their healers LOL

10

Because they don’t actually play the game. They’re spreadsheet junkies watching rage capping on prot warrs and fundamentally misunderstanding why.

1 Like
11

we were pretty starved for rage before gearing up so this is going to also make the gear climb miserable for new tanks.

I got my prot pally ready to go (626) for next season if they go ahead with this and it’s crap.

12

Good thing there isn’t a shortage of tanks currently or anything. Wouldn’t want to discourage people from trying out a role in dire need of more players.

1 Like
13

On the changes for Colossus arms warriors, the excuse about removing Execute granting charges of Colossal might was, and i quote, and remember this was on the “Arms” section of the notes:

Using your hard hitting rotational ability regularly is core to the colossus play style, and Execute applying Colossal Might pushed Colossus away from that during Execute phases.

Basically “tell me you don’t play arms warrior without telling me you don’t play arms warrior”

So yeah. Whoever is behind warrior balancing definitely doesn’t play the class

2 Likes
14

well just to make sure i’m not completely off base here. I am a Mountain Thane Prot warrior; is there data suggesting that this might not affect me “as much”?
I will most likely still raid with this guy but i dont want my key performance to get dumpstered.

I’ve been using my prot pally lately (just farming 8s at this point) and with the exception of still being a big spikier than I care for …he’s not terrible.

15

The execute and colossal might interaction affects both Arms and Prot. Playing Thane, it doesn’t change anything. That being said, the other changes will still screw you as Thane.