Fury's Execute Problem

Fury has had an issue that’s been bugging me since start of war within.

Put simply, all the buttons that on paper should be the most impactful and exciting to press are either used as filler or only pressed at the tail end of a buff falling off to avoid wasting resources. The perfect and main example is execute. Fury as it stands almost never presses execute. This to me seems an egregious oversight, as execute is what most people would say is the most iconic warrior ability throughout all of the games history.

There are two main reasons for this that I will talk about separately.


1. Execute needs to be the highest damage builder on our bar, period.

Historically the idea of execute was an incredibly hard hitting ability that you could only press under certain circumstances, and when you are able to press execute it should feel incredibly powerful. If you look at the guides right now on wowhead, based on the current mountain thane M+ API, execute is currently bottom of the priority list. Only to be used if both bloodthirst and raging blow are off cooldown, no charges of thunderblast, and not enough rage for rampage. It’s a filler ability. Bloodthirst does more execute damage than execute. I’ve done multiple keys where I never pressed execute once. Even if you are playing slayer, the hero talent tree that’s supposed to be built around execute, you only ever press the button if you have maximum stacks or marked for death / Juggernaut is about to fall off / Sudden death is about to expire and the target is above 35%.

This amount of priority mathematics is in my view completely ridiculous for execute. The only buttons above execute in priority should be cooldowns and rampage to avoid wasting rage. If execute’s damage was proportionally tuned how it was before, none of the above math would be needed: if you can press execute, press it.


2. Raging blow and Bloodthirst have way too many additional effects, execute doesn’t.

This I think is the main culprit for the problem of fury’s rotation being wonky.

Right now for example raging blow does it’s damage and also has:

  • Stacking crit chance for bloodthirst
  • Stacking damage for Rampage
  • Two separate chances to reset itself
  • Chance to proc Lightning Strike (Thane)

Bloodthirst then has:

  • Chance to enrage
  • Chance to cause cold steel hot blood
  • Chance to proc Thunderblast / Reap the storm
  • Extend enrage
  • Extra 50% damage in execute range
  • A small heal, that becomes huge with enraged regen.

The only thing like this that execute does is juggernaut, boosting its baseline to crit chance to 50%, and then even when that is fully stacked it is still not any higher on the priority to press unless that stacking debuff is about to expire.

Functionally the only way to solve this in my opinion is to grant execute all the same modifiers that raging blow has. For example it already shares the lightning strike chance, what if execute also stacked up rampage damage and bloodthirst crit chance? That way on paper it does more damage than RB, generates more rage than RB, and also you aren’t missing out on the stacking amplifiers when you press it. Immediately Execute becomes our best builder again and the problem is solved.


As a last side note, sudden death also needs some attention. Right now the only reason any talent setup takes this ability is because you are forced to take it to make slayer work. Sudden death should feel like hitting the lottery when it procs, like it used to. Sudden death could be easily fixed if execute was inherently better as listed above, but if for some reason that’s not possible sudden death could simply increase execute’s damage by 25/33/50% or whatever is appropriate to make it worthwhile to use.

There are other issues that Fury is feeling at the moment (5 targets, people skipping capstone talents, etc) but I wanted to keep this feedback specific and somewhat concise in hopes that it is useful and seen by the development team.

Fury warrior has been my favorite way to play the game since 2004, and right now it feels like the soul of the spec is missing. Please make execute fun to press.

8 Likes

This is really the sum of the execute problem IMO. Especially with Raging Blow - it has an absurd amount of effects tied to it.

Execute has to do more, and it needs to have some larger interactions with the spec beyond just buffing it’s damage.

Addressing baseline execute would obviously help this, but when you look specifically at Slayer I would definitely push for some of the Marked for Execution bonuses to be built into Sudden Death procs rather than being 100% based on consuming the marks.

4 Likes

The entire point of Execute is to empower our Bladestorm as Fury.

I will say the damage Execute deals while in Fury spec is lackluster though.

Agreed, fury needs to have it’s damage per cast to be readjusted to the following priority.

Rampage > Execute > BT > Raging Blow.

Ideally the amount of additional talented effects for BT/RB are flat out removed or redistributed.

For instance without any further tuning right now you would end up making this the priority by just changing Slaughtering Strikes to stacking up from BT and Execute. Have BT add 1 stack and have Execute add 2.
This alone would pump both of these abilities to a higher priority than Raging Blow and would enable fury to go back to it’s roots of the BT - X - X cycle while also removing the degenerate brutal finish raging blow reset spam after each bladestorm since Unhinged would stack it for you anyway partially.

Realistically though fury needs a bigger changeup to it’s talents in reducing the importance of Raging Blow which should just be a filler attack that does average damage (less than BT).
BT needs to hit harder to give it a reason to hit on cooldown over RB.
Execute needs it’s balls back so it’s actually something you want to hit as soon as that button lights up as right now it’s a lame dog of an ability.
Rampage needs to feel important as a rage dump to slam when it’s available as opposed to overcapping rage to dump raging blows to make it hit harder being the go to in some situations.
People harp on about Arms being ragecapped, but fury wastes more rage on average by just being overcapped while playing it correctly.

6 Likes

I guess the point of the post is simply that the point of execute should be huge damage below 20/35%

Empowering bladestorm (only with sudden death and only capped to 3) should be icing on the cake of why you press it

All my homies didn’t believe me when I said execute was literally at the bottom of the list of buttons I press as fury. It’s basically not used as thane.

2 Likes

Real and true, partly why I play thane, I’d use execute again if they’d add annihilator back, I hate pressing raging blow. I have to waste 1 talent point into execute and it’s not even worth using, gimme my point back.

We can blame Juggernaut for this, (and game design devs). They’re too scared to let execute be a strong signature ability, because they don’t want us to have fun with it. Same as Odyn’s Fury, just another “strong signature” ability.
Man, if my eyes could roll back in my head further? The more I dig into the nitty gritty of various classes, the more and more I really start to hate Blizzard’s class developers.

8 Likes

I don’t know why juggernaut specifically has traumatized them so much.

You let the thing stack to NINETY NINE of course it’s going to break some encounters. At this point though execute is so far removed from what it was in legion that juggernaut isn’t even relevant anymore. Back then execute costed rage and did more damage than any other button on our bar.

Now it’s just a filler ability, they could give us original juggernaut back and I still dont think we would press execute unless we knew the raid boss had a 3 minute execute phase

Because the class dev team seems too apathetic, and biased. Perhaps lazy as well. They seem to do a project on a class and then move on to the next. Most of the time not concerned with the good or bad effects of what was done. As a warrior player, we’re still feeling the sting of the massive nerfs from season 1.

2 Likes

Hitting execute as fury is just wasting your life away and you can never get that time back.

3 Likes

THE video is why.
youtube.com/watch?v=6hMqvb8QiUk

If they really wanted to keep juggernaut in some way, make it damage based instead of crit again, but it stacks up to 5 - after using the fifth stack it resets to 0 again, take away the needless timer on it (maybe it can expire ~30 seconds after combat ended)

I agree that Execute should be an exciting button to press for all warriors. It’s goofy to me when I see my Prot Execute hit way harder then my Fury Execute.

5 Likes

I could write up a whole entire post about slayer honestly.

I think the premise of the hero talent tree is just broken, it shouldn’t be optimal to not press execute and wait for a rng stacking debuff to press the signature ability.

That and specifically for M+ the CDR on bladestorm is often not even helpful as it desyncs bladestorm from your other cooldowns, breaking the neat 45/90 pack cycle.

Often times the CDR just means you end up having bladestorm back when the pack is at 10% health and you end up holding it until 45 seconds anyways.

A beautiful solution to this in my opinion would be to make slayer baseline give you two charges of bladestorm, and pull some power out of it to compensate, like that one talent no one takes.

This way you can still use unhinged, and also the CDR on bladestorm becomes always valuable.

It would let you bank up some nasty execute range double bladestorm bursts on raid bosses too