Arms is actully pretty damn fun

I literally told the point of playing alts

Guess you accuse others of what you do, in this case, inability to read

Its not

sure thing

What accountability? are you the owner or the judge of this forum?

Wow Police? lmao, got quite the big horse to be that up high mate

Slayer Arms is fun, but that’s about it. Arms in general still has that weird rage issue where we barely touch Execute (you know, our suppose to be massive damage attack), unless it’s a sudden death proc. Hence why I say Slayer is fun. You get a fair amount of dopamine from SD causing reap, (something they are planning on taking away in .5 patch).

Pretty sure Syeg is talking about PVP, which to be honest looks completely dead in the water this season. Has been a bit of a meme for too long, so it’s understandable that people are getting upset and frustrated. Even on the PVE side, as mentioned above, we keep having most of our class issues ignored or screwed with in a negative way.

1 Like

Exactly the problem

We were also getting that with the 100% crit from MS after demolish…

and guess what, they took from us as well, what a joke name for a skill, “demolish”, it doesnt demolish crap anymore

Happy for you my friend. I’m glad the buffs and top tier players are succeeding. My personal feeling is the spec doesn’t feel correct at the moment and it bothers me given how long I’ve played the spec

Only in multitarget builds, which kind of makes sense if you’re not investing into Execute talents. 12.0.5 will make it a lot more sensible though, as Colossus will just hard prio Slam and Slayer will continue to lean on its frequent SD procs.

  • This also has the very welcome added benefit of no longer trying to weave Cleave into the single target rotation.

SD-Reap is staying, it’s just going to be a multitarget proc now (during Sweeping Strikes, so still practically always).

Yeah, that is as toxic to do like Whirlwind spam was back in (Legion, if I remember correctly), the day.

Where are the patch notes that confirm that? Or is it just poor wording on their part?

About 2 weeks ago on the PTR they made the change.

Fury has a similar behavior where if Meat Cleaver is active and your Sudden Death Proc hits more than one target, it triggers reap.

That works I guess. Sucks we’re gonna lose more ST from the reap proc.

That still godawful for pvp

such lame change

I would expect some eventual tuning, as each spec is affected differently.

  • Arms recoups single target damage from the Mortal Wounds change, though it does lose some AoE in the process (not as much as you’d think, since the Bladestorm buff compensates for part of it).
  • Fury loses more single target, while its AoE actually gains a small boost.

Yeah, not as much as I’d like.

And yet somehow it’s almost never thematics that gets people on the “Arms must be revised!” wagon, just “X could be easier and therefore should be easier (never mind what control that would reduce)”. /sigh

I’ve never thought of that as a problem, especially now that MP is (A) trivial and (B) can only be spent on MS anyways. Heck, I liked when Cleave could proc Fatality for similar reasons (greater average %AP per use over Slam, given Fatality), even if that meant Slam had even more things prioritized above it.

WW spam was in Legion simply because proc chances on the Mastery at the time scaled with the number of hits (3 for WW itself back then), iirc, and then in BfA for Test of Might under essences that’d speed your main CDs along enough not to need Cleave for Deep Wounds anyways, and potentially even under Seismic lego in Shadowlands (especially with Spiteful and Korayn soulbind to just have Bladestorm ad nauseum and ridiculously high AoE sustain). :sweat_smile:

Even if they manage all the same ST damage regardless, I just don’t get why they’d want to reduce the Bladestorm prep from ST actions or waste the visual spectacle (however mundane) of Reap going off from every Sudden Death.

Haven’t we mostly had the problem of too little ST from our AoE builds? Wouldn’t we therefore want to compress AoE and ST capacity into each other, not split them further.

I see one glaring problem though with their changes coming in 12.0.5.
If and when they buff ST to not be on the lower end for both specs, whenever a second target is present your funnel potential will shoot up like nobody’s business when SD procs are able to hit a second target via SS/IWW to force those reaps.

It could potentially be a balancing nightmare in the making, leading both specs to be hamstrung pre-emptively for their ST potential due to that increasing higher than they want in other avenues.

2 Likes

And given Collateral Damage, it’s not like they didn’t know this could/would(/has) happen(ed).

2 Likes

As a career Fury fanboy, I’ve actually been dabbling in Arms a bit the last couple days to see what all the hubbub is about, and honestly it is pretty fun.

The AOE methodology of Cleave on CD, and weave Sudden Death procs and MS for Reaps feels pretty satisfying when everything’s gelling.

Single target feels pretty good with the little bit of a whack-a-mole mentality keeping it feeling far from a 1-button spec, but I know I’m likely not min/maxing the micro game of buffing abilities w/ other abilities. That said, still feels like pretty reasonable damage. The heroic strike slam upgrade isn’t anywhere as bad as people are making it out to be. Frankly it’s the one button I feel like I can confidently smash when it does proc (please let me know if that’s improper :sweat_smile:), and Slam feels about as special as RB for fury as a “got nothing else left to press” button. That’s not a bad thing. It’s a reliable filler spell.

The only real knock I’ve got here is cooldown management. The de-sync of Avatar, Warbreaker, and Bladestorm does feel incredibly awkward at points. Do I hit one if it’s up and the other 2 are still deeply on CD, or am I supposed to rage dump greed for the fastest resets possible and only send them all together?

Been playing Critcake’s slayer build as well, which is sparing me from the added awko taco of figuring out how Demolish would fit in on the CD queueing game as well.

EDIT: To put this in perspective, I was clearing DF power pots from my bars while getting all this set up. I’m picking this up as green as possible coming from exclusively playing Fury. Arms really isn’t in as bad a place as some of y’all are making it out to be.

2 Likes

Conceptually, using Cleave in single target is not inherently a problem, but it does become a problem when it muddles the rotation.

  • If your rota became MS > HS > OP > Cleave replacing Exe/Slam, that’s fine.
  • Our rota was something more like Cleave during Ravager > MS > HS > OP > Exe @ high rage > Cleave sub-35% > Exe @ low rage > Slam, which is unnecessarily jumbled.

I am an advocate for rotational complexity and nuance, not just rotational clutter.

I don’t see how these two things interact with one another? Sudden Death benefits and you’re still going to use it, but Reap itself doesn’t have any interactivity with Bladestorm.

Hence the Mortal Wounds change. If they do any follow-up tuning, splitting them up also allows Execute damage to be tuned more directly, since it no longer needs to account for Sudden Death being much stronger via Reap procs - in other words, stronger consistent Execute instead of just stronger Sudden Death procs.

Yep, I misspoke. Since it’s SD anyways, there’s no priority change.

Okay, but you’re applying DW to both targets in SwS atop getting the Reap extra into each.

It’d have been far easier to just have Execute always or never proc RtS in that case.

  • For instance, why not just have Execute always proc RtS (regardless of SwS) but, as part of the talent, reduce Execute’s own damage by most of the difference, and have RtS’s main target damage benefit from any benefits to Execute damage. Then it’s consistent despite offering some extra AoE and not forcing baseline Execute to be too weak to take.

Yep, I misspoke. Since it’s SD anyways, there’s no priority change.

Okay, but you’re applying DW to both targets in SwS atop getting the Reap extra into each.

It’d have been far easier to just have Execute always or never proc RtS in that case.

  • For instance, why not just have Execute always proc RtS (regardless of SwS or SD) but, as part of the talent, reduce Execute’s own damage by most of the difference, and have RtS’s main target damage benefit from any benefits to Execute damage. Then it’s consistent despite offering some extra AoE and not forcing baseline Execute to be too weak to take. You’d even have the fun little divide and conquer / Butchery aspect of rushing down one target to cleave others as a bonus. Just food for thought.
  • To be clear, this would not be for an RtS that still hits harder than Mortal Strike. Something more in the range of 200% AP, where cleaved attacks can stronger it multiple times for stacked damage (up to that almost 600% AP).

I feel like that would play hell on Arms’ rotation, since just spamming Execute would be even better than Cleave at that point, not to mention having very different levels of power between Arms and Fury that now has to be accounted for.

I don’t think it’s excessive to say that spamming a single button should never be optimal in any practical context.

1 Like

On ST yes, whenever 3 targets are present? Only ever use it through Cleave which will auto cast it and make it do 50% more damage from Fervor of Battle (assuming it’s talented).

From a basics pov, especially moreso when you’ve got your 4p.

Always pair up Avatar and Bladestorm with your next CS they don’t have to be paired with each other but just use them with CS and don’t be afraid to send cooldowns when a pack is low health (especially CS) as the follow up Mass Execution buffed cleaves will do a lot of damage.

Unhinged has a lot of value present on your main target when CS is applied since it’ll extend your CS debuff by a large chunk, if played right you can keep up a very long CS debuff on the priority target of a pack and everything else to a lesser extent with proper cleave/ms casts.

It’s really not that complex, more often than not you’ll just send them in CS windows or whenever possible if you’ve had a really good RNG string. The more you play with it the more it becomes second nature.

1 Like

Sorry, phone version ate my immediate edit:

I agree, but unless we want free casts of Execute to randomly deal more than double the damage of an actual 40-Rage cast, some degree of consistency would be nice.