Opinions opinions maybe blizzard reads?
2 Likes
Heard somewhere that it’s a bug, so if you also think that it’s a bug keep the bug reports coming, maybe the devs will fix the issue.
Same as Hunters. As a sole M+ player, I’ve decided to just abandon my Hunter and Warrior and just reroll and focus on Balance Druid (even though I don’t really want too). It’s ridiculous to be capped and being overlooked in high(er) keys because of your class/spec. I’m simply not welcome because I play Hunter and Warrior.
I find that if you wanna play (push) M+ then Mages & Balance Druids always seem to be a safe bet and always get placed in at least tier A of classes and specs. Every. Single. Expansion/season.
If I wanted to play melee then I’d go with a Rouge which also pretty much always places in the top tiers of specs/classes in M+/AoE. Ret seems to be a safe bet as well these days.
2 Likes
I mean the warrior class in general, especially both DPS specs, are outdated compared to others specs when it comes to mythic plus. They are viable, but why should anyone invite a dps warrior for example compared to literally anything else?! Group leaders would actively handicap themselves and the group in doing so.
1 Like
The problem they seem to paint themselves into is this:
- They double and tripple down on making Fury Warrior only be about the rotationals, making its CDs pointless and (if able) you avoid using them as much as possible, they are that inefficient. This removes their ability to tune warrior AoE in a mass-target scenario against others with help of this part of the kit.
- As it is all rotationals, it is directly linked to its single target output. This is problematic, as if you want to increase the AoE, you increase the single target, and in raid that is a problem because it puts Fury ahead of other classes. As raid and M+ damage profile values don’t blend well, this imbalance is problematic.
The same problem as Fury having AoE burst was bad for raid balance, but what kept it (till it was removed) unique and quite strong in M+.
You could try to avoid the problem of ST being the way to increase AoE by changing meat-cleaver. Now that causes another set of problems. Firstly, it further cements the downfall of the AoE damage CDs. Making that situation worse off. Second, it starts to push Fury away from its niche. Increase the damage value of meatcleaver, and you get closer and closer to the two-target cleave niche of arms. Make meatcleaver hit more targets, and you start to press upon the 8t boys, or uncap meatcleaver and things just start to fall apart.
Now you got to address all the random procs and “synergies” in Fury. BT proccing reap, gushing wounds and what not.
You end up in a situation where Fury’s “niche” (as others do our job there, only better, and are uncapped - a tuning problem for sure and real) is just gone.
To be fair, they already removed the AoE burst niche, so I guess it is in theme with the rest of the changes done. Just make Fury another uncapped AoE DPS spec, that passively cleaves out damage without any thought or concideration.
I am like 90% sure that all the Thane lovers would sing Blizzard’s praises if they did exactly that. As that is what they seem to want.
Elune forbid if Bladestorm actually did the damage on its press. Nah, better it be rotationals that proc random things to do the damage. At random. But set random. So it is balanced. Random and no control is fun after all. Right? Right…
Just make Raging Blow do splash 50% of its damage uncapped AoE 30% of the time. Ez boring fix to the problem. We don’t prio that button enough.
2 Likes
If you are into pushing M+, just play a different class.
So because blizzard doesn’t do their job we should play another class? I’m the customer here and i demand what i pay for. Good tuning and not this what it currently is.
3 Likes