Target cap needs to be addressed
Remove Meat cleaver and its cleave effect, and then balance their damage.
I feel like our AoE toolkit isnât that bad, itâs just most of it is tuned like garbage in this patch.
TBlast/Roar/OF/Bladestorm are all pretty good abilities on cooldowns combined with an extremely strong base cleave that we currently have. Roar is meh, OF is a joke. Slayer Bladestorm is honestly pretty strong - Slayer just has beans AoE outside of that since OF/Roar are bad.
In terms of the damage profile of fury I would personally like to see the following changed. Which would put you at the following cast priority for ST.
Rampage > Exe > BT > RB > WW/TC > Slam.
BT buffed slightly (more on this further) - It needs to be more important to hit on cooldown than it is right now where you tend to delay it until ~3x Bloodcraze stacks or sub 35% when itâs buffed by VC only then does it become a priority in your rotation.
Raging Blow nerfed - Itâs way too important in the rotation right now being the sole builder of Slaughtering Strikes it just causes weird jank priorities over other abilities which should be much higher priority than it when they proc.
Execute buffed alongside Slaughtering Strikes to also gain stacks from execute (2x Stacks instead of the 1x from Raging Blow), this alone would fix ignoring execute entirely as a button, seriously itâs silly how bad sudden death procs are for fury or how much you ignore execute outside of slayer stacks on target.
On second thoughts, maybe Raging Blow no longer adds slaughtering strikes and instead bloodthirst does allowing for more focus to bloodthirst without overly buffing itâs direct damage and then raging blow gets further relegated to filler as opposed to spam priority 1.
Meat Cleaver removed - Honestly the more I look at fury and itâs problems being hard capped on itâs AoE the more Meat Cleaver stands out as the problem as the devs have always been too scared of making this the actual niche for fury to excel at and since they wonât do that it would be much better with it just removed and furyâs AoE toolkit revamped with the following.
Storm of Swords portion of the annihilator build returned but only for WW/TC where theyâre significantly buffed but they have a cooldown of 6/7/8s, providing a stack of slaughtering strikes per target hit post 3+ targets (max 3) and stand as your AoE Generator, somewhat harder hitting and also tuned higher than slam on single target to keep them as the next priority for filler in ST.
An AoE rage dump added - Could repurpose OF for this making it baseline/earlier in the talent tree, retune it so it does 65~70% of Rampageâs damage while also having fall off 8+ targets (NOT HARD CAPPED), slap on all rampage mods etc to it like âenrages you on castâ, âgrants frenzyâ, and âbenefits from slaughtering strikesâ/âBrutal Cycloneâ etc.
Onslaught buffed - It now replaces Bloodthirst, now 9s cooldown (haste scaling), does double the damage/self heal/slaughtering strikes addition of a regular Bloodthirst further putting it up as a priority over every other attack. Naturally this would also effect unhinged as a result, put it to every 4th tick as a result so 1 onslaught on base, 2x on full extended so itâs exactly 1/2 casts of the base if BT is talented.
Frenzy no longer resetting on not being cast on the original target, this would just get rid of the pretentious mouseover macros people would use to get around this awful constraint. This doesnât exactly impose on the berserker who thrives on the field of battle theme either, if anything the current reset of it when switching to a target next to your previous one is off the theme fantasy. While removing that restriction also still punishes downtime like it should still as if youâve got nothing to hit surely your momentum will be impeded.
EDIT: On the second rage dump thought, they could honestly just patch rampage to also cleave x% of itâs damage to other targets around you as well, adjust the animation of rampage with larger slash trail indicators, maybe some wind pressure/dust effects added in the mix too so it doesnât look too magical while also having itâs centre of effect based on your positioning for ease of use.
Regardless of any other tuning and changes I do feel like this needs to happen.
Been scrolling through these posts, gotta wonder whether if thereâs actually someone in charge of fury, cause it seems lots of valid ideas are being brought up and nothing will ever change at this point.
I was doing keys with a marksman hunter friend the other day that was clowning my aoe damage. Iâd merc him on every boss fight but my overall suffered because of aoe. I told him my aoe is capped and heâs like so is his! I went and looked at hunter skills and was surprised to see that trick shots and explosive shot was capped at 5 yet he was doing so much more damage. Maybe itâs not just the cap thatâs the problem âŚ
Thatâs because Trick shots cleaves at 75% damage, compared to our 55%. Is it right? No, not really. Is it Blizzard showing biased or incompetence? Yeah, but thatâs not a surprise.
Almost as if classes and specs are designed to be more effective in certain areas⌠Again, the clown shoe level of mental gymnastics you go through to complain is staggering.
Youâre giving the devs more credit then they deserve. Design? If this was the case then you wouldnât have classes that can do great ST and AOE. Donât like the complaining, donât complain about the complainers goofball.
Doesnât stop it from being big time feelsbad.png. Particularly when âniche metaâ creates environments where the niche doesnât quite fit. Higher keys are reliant on massive pulling. If you canât keep up in that specific area, youâre not gonna get picked.
Dial up MM single target, adjust warrior sustained aoe. Problem solved right?
âOoohhhooooh but we canât homogenize classes or whatâs the point in having different classes??!!?â
Different playstyles resulting in similar outcomes allows for different playstyles to be competitive with each other.
Reworking the spec isnât even needed. Just have the abilities cleave for MORE DAMAGE, JUST LIKE HUNTER.
Itâs not hard at all. Our toolkit is not the problem. The problem is literally numbers and a lazy developer for fury. Iâm taking the approach of voting with my wallet and cancelling subscription at this point until they fix the issues.