Feedback: Slayer Warrior

Classes Warrior
61

It’s not a question of faith. For the proc to be disruptive, the Bladestorm would have to channel for a full second, and that second would have to begin at the start of the next GCD. Someone can correct if I’m wrong, but I don’t believe there is a single proc in the history of this game that has functioned that way, unless it was specifically specified as happening “on the next cast” or “after 1s” or something similar.

The point is, in this game, when something says “When using X, there is a chance for Y effect to happen”, then Y always happens instantly, during the GCD, unless otherwise specified. Is it possible they implement this in a completely asinine way that goes against this design philosophy for procs that has gone back 20 years? Sure, I guess, if we want to doom that hard. But it is extremely unlikely, and really not worth worrying about.

2 Likes
62

“While Bladestorming” is inclusive. There’s no distinction between a Bladestorm triggered by Slayer, one that is hard-cast, or triggered by another effect such as Signet/Blademaster’s Torment. Even on a technical level, they’re all the same spell, just overridden with different durations. Furthermore, both the “Bladestorm proc” and “Pummel while Bladestorming” are part of the same talent - Frenetic Flurry.

There is simply no logical or technical reason to believe they would work separately. Unless the devs went out of their way to make a completely new 1-second Bladestorm, which there’s no reason for them to do when the effect already exists elsewhere, it would appear extremely unlikely that this will work any different from any of the three other versions of automatically triggered Bladestorm.

As outlined above, the wording is pretty straightforward: “Overpower/Bloodthirst have a chance to cause you to unleash a brief Bladestorm, striking all enemies around you once”.

  • The least generous interpretation is “a 1-second Bladestorm” but even in that case, it’s still the same Bladestorm spell, which is hasted. Because it’s triggered by Bloodthirst/Overpower, it incurs a 1.5s GCD, and because haste applies to abilities and the GCD at the same rate, the Bladestorm would always finish before the GCD is over, thereby alleviating any concerns of disrupting the rotation.

The only potential problem, as also pointed out above, is there is the off-chance you want to do something off-GCD during that Bladestorm - Leap being the most obvious and likely. While this is a potential (if extremely low impact) problem, that’s feedback we can address at the time, and I don’t really think it’s important enough to warrant any amount of fearmongering - even if it does turn out to be the case, there’s always the potential for a /cancelaura, or simply playing smart enough to recognize situations where you want to delay pressing Bloodthirst/Overpower for a second in order to facilitate a bounding getaway.

I understand your apprehension, but I think in this case it’s mostly unwarranted. Either way, we can’t really confirm it until we get a chance to see it in action once Alpha begins this spring, and rest assured that if there is any disruption I’ll be beating down the devs’ door until they address it! If you want faith in something, you can have faith in that. :stuck_out_tongue:

7 Likes
63

I’m not saying it’s a different spell at all. Or that they aren’t the same talent.

I am saying that having the pummel/stormbolt addition during Bladestorm attached to the Bladestorm procing talent is a strong indication that the Bladestorm proc might mess with rotations.

And it’s not fearmongering to point out a potential issue before it becomes an actual issue. Now is the time to point it out, when it is easiest to address.

For the record I think you are most likely correct, but we don’t 100% know what’s going on behind the scenes so it is better I point it out even if I’m wrong.

1 Like
65

As a DK I’m envious. Y’all eatin’ good with this tree.

66

I saw that Bladestorm is returning for fury and got excited. I really enjoyed using it in dungeons as fury and I have missed it this xpac. Bladestorm is my favorite fury warrior aoe ability. Odyn’s Fury with Titan’s Tormet feels like a good button to press, but there’s something about Bladestorm where I wind up spinning around in a cyclone of death that feels furious and awesome. The slayer treee has piqued my interest since it interacts with Bladestorm for fury warriors.

2 Likes
67

Reminds me of when democrats vote in republican primaries and vice versa. :stuck_out_tongue_winking_eye:

68

Not much to get excited for in this one aside from the absolutely massive QoL change of being able to pummel and storm bolt during bladestorm. Compared to Colossus being locked out of everything twice as often as a current bladestorm build is now, the choice has already been made for Arms warriors which hero tree they get to run in M+ which is kinda disappointing to see.

69

Slayer is looking like the best out of the 3 imo. One question. How long do these “mini” bladestorm procs last for though?

2 Likes
70

i think its just “you strike all enemies around you once” type of deal and don’t actually bladestorm, wording on that is a bit confusing

1 Like
71

Gotcha hopefully its not too disruptive to the rotation. Maybe they should just call it whirlwind then lol.

72

Slayer, what can I say for the initial reaction to it outside of I LOVE IT.

It honestly just sounds fun, with no downsides to it at all. Exactly what a hero spec tree should provide.

Slayer’s Dominance being the return of Opportunity Strikes? Hell yes, as long as it’s a similar follow up attack animation swing after an attack it’ll look great.

Frenetic Flurry sounds fun, having a quick 1 tick bladestorm spin that won’t really impede on the GCD proccing off of OP or BT just sounds fun since i’d presume it would be a 1s (scaled with haste) tick of Bladestorm, now if this also provides a CC immunity during it would be interesting since Haste would lower the window of immunity provided for a faster tick, more a PvP thing really where a Slayer Warrior would opt for as little haste as possible for a longer iframe as a tradeoff for potentially less chances to proc it than a higher haste build could potentially have.

Relentless pursuit is insane, charges being a quick freedom is great.

In terms of how Arms is effected Talent wise for this as of current it puts a conflict in the spec itself if you’d take Deft Experience and Battlelord to take advantage of the additional overpower resets as opposed to Critical Thinking and Juggernaut for the rage refunds on execute and increased execute damage. However this is also subject to how the talent trees will be set-up and if fury’s bladestorm will be in it’s spec talent tree as noted or if it’ll end up being in the class tree instead to take over the hole from shockwave’s movement which could be a good thing in allowing more proper build diversity in allowing both dps specs to not lose as much Single Target for AoE throughput.

Slayer being a more selfish tree is nice to see, given that warrior’s are somewhat lacking in utility they need to have the damage to back it up to be brought in over others. Which I hope you guys keep in mind when balancing in the future, selfish with little to no group utility specs should have the highest throughput to make up for lacking tools to help the group.

The other two trees in Colossus and Mountain Thane also opening up group utility so they can be taken if that extra damage isn’t needed in a dungeon setting is fine.

Keen to actually test things as always during the beta cycle to provide more valid feedback.

Overall I really like the look of Slayer and in my first read of it, it just sounds fun af.

EDIT: I quite like how both Fury’s Hero talents put BT at the forefront to it over Raging Blow for most of the talents which further allows for equal parity between it’s two builds of Annihilator and Raging Blow.

4 Likes
73

Cool talents at the beginning, the rest is kinda meh. Remove the 2 talents that do the same thing, which is, reduce the cd on bloodthirst and overpower, literally useless. Especially overpower cdr.

Unless the capstone talent will make bladestorm cd match that of warbreaker more or less, otherwise that talent and anger management will be anti synergistic.

74

Even as someone who personally doesn’t enjoy current Bladestorm that much, this tree is absolutely sick. I love this. The best one we’ve gotten.

I do share the concern with Frenetic Flurry, though. I’d like clarification on whether if that’s going to randomly lock us into a second of Bladestorm or if it’s more of an instantaneous thing.

1 Like
75

My confusion is that the Dev note says that the intention behind Slayer is " the execution of their chosen target" and yet prioritizes Bladestorm, an ability that Fury had removed for good reason of it not working well in the kit.

3 Likes
76

I really miss feeling like a master of all types of weaponry, and not a RNG beyblade

3 Likes
77

The tree splits its focus between Bladestorm and Execute pretty evenly, it’s disingenuous to say that it is prioritizing Bladestorm any real amount more than Execute. Do you really want the entire tree to just be about Execute?

I love Execute just as much as the next guy, but an entire tree being around the one button would almost definitely be really boring, and really difficult to balance without making DPS warrior feel like complete garbage outside of the execute phase.

5 Likes
78

Something else I’d throw in here is that this tree is increasing both the damage and frequency of both abilities pretty substantially.

We also don’t know the extent of talent tree rework and how that will improve the baseline versions of execute and bladestorm for either spec, but especially for Fury.

I understand being hesitant about Bladestorm given its history over the past several expansions, but they can tune it to be good and use the enhancements in this tree for those who want it to make it a banger to press.

79

That’s what I was saying, it feels like bladestorm is the star of the tree so arms can be included/why we are getting it back and execute is kind of just there to make bladestorm better. Id of rather had something like odyns fury for our part of nodes

The other person can say oh well they split between execute and bladestorm evenly but its still pretty clear bladestorm is the priority

4 Likes
80

Up to 30% more damage on Execute + casting Execute more often with more SD procs + 5-15% crit chance + crit damage on Execute (depending on if the crit buffs stack with Marked for Execution stacks) = “execute is kind of just there” to you, huh

2 Likes
81

I don’t like how Slayer and Mountain Thane are clearly designed for either Annihilator or Raging Blow, but not both.

It’d be nice if Slayer was equally designed for Raging Blow builds, and Thane for Bloodthirst.

Overall, I haven’t liked the implementation of Annihilator. I think it’d be better to have one side of Fury tree focus on a fast playstyle (such as trying to Enrage every 4 seconds) while the other side has slower, more deliberate playstyle that extends the Enrage window (like how Raging Blow used to extend Enrage with the old Enduring Rage honor talent.) Annihilator didn’t make a slower playstyle, it just made one that spams attacks that aren’t Raging Blow. And in these new hero talents, like Dragonflight Tier, we’re seeing an imbalance between Annihilator and Raging Blow builds. Whether or not you want to play fast or slow Fury should be a matter of personal preference, not combat advantage.

1 Like