Same here. As silly as it sounds, I enjoy the sounds of Slayer more. Yeah, Thunder Blast is cool and all, but I love how Slayer just sounds like blades of steel all the time, not only with Bladestorm but the sound whenever you get a stack of Marked For Execution.
Also, it feels…faster for some reason, even though it’s not. Maybe just the sound effects acting as a placebo in my head.
I ran Slayer in both M+ and raids in S1 but I’ve only done Mountain Thane for M+ this season. I haven’t tried Slayer yet but if it’s as far behind as people say it is, I probably won’t bother touching it. Thane is already lacking compared to almost every other spec in the game and it’s super obvious on some dungeons more than others. I was in a Cinderbrew with 2 Hunters earlier today who were both bursting up to 11M DPS on large pulls and I’m over here barely getting 5M even though we were all roughly the same ilvl.
I really want to push for 3K rating to get the mount, but it just doesn’t seem feasible as Fury, at least not without being hard carried by other classes and feeling like I’m not pulling my weight.
2 Likes
If they buff Ravager they’ll have to buff the other option on the choice node (bladestorm) that’s required for the other hero tree so that it feels like a legitimate choice. It’ll be so frustrating if they don’t. It wouldn’t surprise me if you are right though unfortunately. I don’t like these de facto non-choices for specific content.
Odyn’s fury definitely needs a rework since I doubt they’ll revert the titan’s torment change. I do like the idea of making it a choice mode with onslaught.
We do need more talent points available for sure. Too many 2 point nodes or required follow up nodes (like meat cleaver). I think the class tree is worse in that regard, but the fury tree is an issue as well.
1 Like
It’s very possible as fury. I’ve done all my M+ as fury and fury only. 100% through the group finder with random people, never in a group of any kind.
However they fix the issue, I just wanna use Odyn’s Fury again. My beloved needs to come back D:
2 Likes
I’d prefer this.
I’d be okay with Fury just having its capstones buffed and Meatcleaver made a soft-cap instead, but it’s really dull to have such a basic ‘ammo’ buff —applied via filler of all things— be all that stands between ST and AoE.
That said, I’m not sure I’m sold on the solution of just turning WW back into a short-CD and providing an AoE-Rampage, mostly because there are a couple things I’m a bit confused by:
- Meat Cleaver already tunes the AoE potency of our otherwise-ST skills separately from their ST tuning. They aren’t conflationary; any increase in ST damage need only adjust the modifier proportionately to have absolutely zero impact on AoE, and vice versa.
- At worst, it only means that each skill conveys its direct damage equally well, proportionately, to AoE, but it hardly seems an issue that, say, Raging Blow goes from 100% to 500% damage over 5 targets in the same way that Bloodthirst or Rampage or Onslaught do.
- I mean, sure, we could prevent that by having each skill auto-cleave per a different cap or formula, but…
- And therefore, given that removing Meat Cleaver doesn’t seem to provide any novel solution to tuning issues, I’m not sure how giving us even fewer unique builder casts in AoE would be preferable for gameplay.
- We could argue that there’d be some change to damage profile, but it seems like it’d be nearly nothing by the second WW cast (or, ~15 seconds in, pre-Haste).
- Moreover, Rampage already frankly looks like an AoE. Why wouldn’t it auto-cleave?
Still, I like the idea of seeing Whirlwind no longer be just a buff-generator applied by filler for an otherwise ST-identical rotation.
Aside: Ideally, I guess I just want to see AoE and ST on Fury be a situationally-paced sort of ebb and flow, even if ST vs. AoE itself would also have an impact. Perhaps the more-AoE-heavy end of things could be necessitated even in ST by DoTs or effect-extenders that allow one to bank for a burst or capitalize upon a good streak in ST. Something of that sort.
Hell, I might even like it if, instead of Fury having entirely free Rage on everything out of nowhere, it simply…
- Generated quite of lot of Rage compared to Prot and Arms and generated Wrath from each point of Fury spent (per “Wrath and Fury”) that could then be spent on Rampage (or alternatives, perhaps even including on-CD attacks, using the Wrath to skip X seconds of CD).
- Rage costs were variable (spending an additional half of excess Rage, up to double the normal cost, for proportionately greater potency in terms of damage and most effects.
- Had some passive that increasingly and accumulatively reduced the Rage cost on each other ability based on Rage spent, such that you might hold off on Whirlwind’s ST uses briefly before add spawns so that you could AoE nuke them the moment they appear or funnel that AoE into an Execute.
All that is likely a bridge too far, though.