I don’t want Bladestorm at all in Fury’s kit. They’ve proven every time it’s been there that it’s an unfun ability for the rotation and reduces uptime on enrage. There hasn’t been a single successful Bladestorm version for Fury and the only times it was taken was when it was obscenely overtuned or it triggered a second ability.
3 Likes
You’re entitled to that opinion, but it’s just that: an opinion. It is not objectively true that it has always been an unfun ability for Fury, I for one quite enjoyed it during SL. And I am not referring to when it was being used with Signet, as a proc.
It’s just disingenuous to try and say that it has never worked, when it absolutely has. Whether or not it has worked for you is a different conversation.
10 Likes
Got it you’re basing it on your feelings instead of actual data. Using Bladestorm at the beginning of SL “without signet” confirms that.
Is it on theme? Yes, although I feel like Execute has really lost its impact since becoming able to be used at any time with sudden death, so this isn’t super effective for me and it already procs quite a bit so I can’t really see how this is going to feel very impactful.
With that said, the interactions with Bladestorm are cool and welcome, so that I do like!
The talents that reset the cooldown of, and increase the reset chance of, Overpower? Like, why? It already resets enough as it is and I never really find myself waiting around for it to be useable, so this is just going to make the rotation more speedy and hard to keep up with. I am begging you to remove the requirement of pressing overpower before each mortal strike or cleave. Hope the regular talents get some love.
Agree with your whole post Archimtiros, cooking as usual. I feel like I absolutely HATE Tactician in the first place, and doubling down on it when it’s absolutely not needed just feels like juvenile design, sorry to be harsh.
2 Likes
From at least a fury POV I don’t like the heavy focus spent on maintaining an uptime on a channeled ability. Ravager fits the playstyle of fury far better. If bladestorm for fury in WW is going to function like ravager currently does but instead is a channeled ability. My suggestion would be that slayer for fury turns bladestorm into one of the following:
- into an aura buff that deals damage over 6 seconds that would still allow us to use other dps abilities (like immolation aura)
or - provides a buff with 6 charges that expends a charge every aa/ability to deal one tick of bladestorm damage
and frenetic flurry/imminent demise could add 1 second or charge to the buff.
This ability could also deal a little less damage than bladestorm (non-slayer and arms in general) to compensate for the fact that we can still use other abilities
2 Likes
It’s alright bud. You can have your opinion. I’ve played Both Arms and Fury a great deal for over a decade now and I can tell you bladestorm in my opinion feels perfectly fine for Fury. Even so it feels nice giving my fingers a break from the extremely high APM of fury’s current playstyle. If you don’t like it that’s fine, but I for one like having a moment or two that I don’t have to constantly be spamming.
5 Likes
I agree completely that neither it or the CDR are compelling bonuses right now, though a reasonable assumption would be that they indicate further baseline changes to Arms/Fury. e.g. Tactician going away or being significantly reduced from where it is now.
While this is a prime time to give feedback, we haven’t seen the whole picture yet, so I try to keep an open mind.
4 Likes
As noted in a previous post, the developers addressed this point in the Mountain Thane Q&A with Plka & Bajheera, acknowledging that some work needed to be done on the core specs to address that “BT vs RB problem” - we just haven’t seen it yet.
With Alpha just around the corner, I don’t think we should have to wait very long though.
3 Likes
A more detailed breakdown was outlined here, but TLDR is that it’s either an instantaneous background action, or a (almost certainly hasted) 1-second channel that finishes before the GCD sweep.
Either way, it shouldn’t have any impact on your rotation or “downtime” waiting for the channel before you can cast something else.
1 Like
Yes when anything interesting comes from pressing bladestorm/bladestorm procs, all of that is extremely boring % increases and we don’t even know yet how execute will feel in TWW. If you add all that on to current execute, which every fury warrior right now knows is useless outside of rage gen, its just not good. Did anyone really like season 1 DF tier set? Because thats one of the nodes essentially.
Flow of the entire tree is to pump out bladestorms.
1 Like
Please share the “data” you’re using to support you not liking bladestorm in fury’s kit and thinking it’s unfun. We’re all dying to see this magical unicorn data that supports your subjective opinions.
2 Likes
Yep. I’m just not seeing any class fantasy in this tree. Thematically it just seems like a combo of vanilla and cataclysm warrior play styles at those times periods.
I don’t know why they just don’t cut the cord and make it blademaster. Make the fury component utilise some cool stuff with ravager having a shorter cd and whirlwind or raging blow, then focus Arm’s on the blade storm stuff.
Add in mirror image and wind walk for arms, x3 heroic leap and passive 10% movement speed for fury and there you go. Something banal but at least more flavoursome than all… This.
3 Likes
You’d be surprised how many people really enjoyed it and continue to enjoy the Arms S3 tier gameplay as well.
The biggest issue is that it was simply bad. Like horrible. As in “objectively one of the weakest main-raid tier set bonuses in the history of the game” bad, even after they buffed it. This wasn’t all a matter of raw numbers, but getting Execute to light up more often is not generally seen as a bad thing.
3 Likes
I’m glad Fury’s getting Bladestorm back. I’ve always hated when they move it exclusively to Arms, on and off, over the years. Looking forward to seeing the updated Warrior tree arrangements.
8 Likes
I really like that idea with ravager instead for fury as for me that’s preferable since I can continue my rotation still and not waste rage. Honestly if this hero spec was called Blademaster it would make a lot more sense to me and be an og thing to call back on, would be more on theme for sure than Slayer which I’m just not feeling at all here.
4 Likes
Well… I do love execute, so I’m happy to see something happen with it, but why zero synergy in these for abilities such as slam that have basically been all but discarded at this point?
Fury getting bladestorm back should have happened a lot sooner, but I am glad to see it happening again.
Overall, I wasn’t expecting a ton from hero talents, so I’m not really disappointed nor surprised, but I was hoping for more than just minor kit synergies and more “glad stance” type things making a comeback.
1 Like
This tree looks like a lot of fun and can’t wait to try it out.
1 Like
Frenetic Flurry sounds like it will mess up the flow of either spec unless it works like Spinning Crane Kick does for Monks. Other than that, i like the tree so far, just have to actually play it to know for sure.
Another idea instead of tying the ‘AOEness’ to Bladestorm (which doesn’t really seem to be a ‘Slayer’ theme) is the idea to make execute cleave into multiple things.
I like the idea someone said that the Slayer should feel like Doomguy. What screams Doomguy more than a giant weapon(s) cleaving through swaths of enemies with big executes trying to get headshots with every swing?
Execute is key here. I think fast swings, tunneling into an enemy with giant executes that compound the longer you’re on an enemy is what I feel Slayer could be.
If a Slayer Warrior engages you, you have about 10 seconds and then you’re dead. And if you aren’t dead, you’re bleeding, battered, and feeling like you should die.
Thats what Slayer is to me.
Any ideas that could spin off that? The Bladestorm ideas are nice, but spinnyspin isn’t a theme applicable to the idea of a Slayer imo.