For fury - As much as I enjoy getting a double bladestorm on a big trash pull in M+, I reallly hate the rng element attached to our best legendary. It just doesn’t feel very good to use at times. Especially when you aren’t running Fresh Meat. I wish Signet would just tell you what your next proc is going to be.
2 Likes
RNG bladestorm is often pretty awkward, yes. I’m not a huge fan.
5 Likes
Yeah, it sucks when you want one proc over the other, but warriors have always been designed with some core RNG in mind. Tactician in Arms, Sudden Death in all specs, Shield Slam resets, Gladiator had a (minor) reset, Fury has Raging Blow charge resets (and was previously built on the RNG of getting Enrage at all). We are a slot machine; just keep pulling levers until some DPS comes out.
4 Likes
Yeah, getting the proc you dont want can be quite frustrating at times. But i prefer that kind of rng where when i press the button i get something, instead of like praying every rampages that i’ll get the siegebreaker proc.
Yeah is anoying when you dont get the right proc
My only issue is that warriors need buffs to other legendaries so we actually have other valid options.
Even something as a legendary that lowers the rage required for a full powered execute or rampage
1 Like
Well we have that new venthyr legendary that looks promising for ST. Sucks that it’s gated behind a specific covenant. I hate the idea of covenant leggos 
3 Likes
its way too strong its most likely gonna get nerfed.
It already got nerfed once, and it’s not optimal for Arms, and laughably bad for Protection.
1 Like
That’s part of the reason why I was really hoping we’d get to equip multiple legendaries like in Legion.
1 Like
i just wish they’d buff our other leggos
1 Like
Now they are buffing execute for protection however I don’t think it is enough. Dps is lacking for prot but especially single target, I would purpose adding sudden death as a talent option.
I actually quite enjoy it. I really like being able to use avatar as a fury warrior (way less about the buff than becoming a stone giant hurling two giant weapons around). For real, though, if our relevant cooldowns availability were a little bit better, the gameplay would feel crazy awesome
1 Like
I would like it more if it just procced Battle Cry everytime as Arms
I guess it’s alright. I wish Executioners precision one was good though. That’s my favorite playstyle ever Arms towards the end of Legion was so fun.
1 Like
I strongly dislike Signet for both Arms and Fury. It feels awful to play with.
1 Like
To provide a little more detail, I don’t terribly mind that Signet is random, nor even that its two random effects are good at different things (one more for AoE, the other more for ST). It’s specifically proccing something that makes you unable to use abilities that makes it feel so awkward to use. It’s more annoying than Bladestorm itself, because at least there you know you’ll need to dump rage first or etc, but holding Recklessness because you need to interrupt and might get Bladestorm is weird.
1 Like
I absolutely love it, but yeah getting Bladestorm for single target feels kinda bad.
Especially when you have to cancel it for Rampage or Condemn when those come up in the middle of the BS.
I don’t care for it either. Makes me wish the other legos were more broadly applicable so I could forgo Kings.
Alternatively, I’d happily take either of two options:
- Tormented Kings now always procs the effect with lowest remaining duration (no existing effect being 0 duration and thus highest priority), starting from whichever you do not have learned, or
- Tormented Kings now grants a much higher duration, but only procs from the spec-native skill, again allowing Arms to take In for the Kill or Deadly Calm, and Fury to take Meat Cleaver or Dragon Roar, if they so desire. (I realize both competing talent pairs need their own fixes.)
As for the Bladestorm procs, I just wish the proc was burstier, concluding more quickly without facing proportionate loss to total damage. Though, I could say the same for Bladestorm proper (which I feel should be shorter and shouldn’t cause its CC immunity period to be reduced by Haste, assuming a fitting animation could be appended over the duration that would remain after the Haste-reduced loss to character control).
You do not cancel for RB.
Depending on haste levels the bladestorm procs can have huge burst considering that instead of reducing the duration of the effect haste adds more ticks to the 4 second window, during lust it’s the highest burst button we have even on single target.
1 Like