Ok, thanks to @tehzle, we have a modification of my original sequence that’s basically at sim for AoE and extremely close on ST on Auto and I got it to sim on Manual. Updated in the OP will be the new builds, and sequence 1.5. Many thanks to @Simarlis for helping with testing!!!
It’s defaulted to auto, but as always I recommend using the Manual versions.
AoE:
ST:
Version 1.6 at the top, slightly even more DPS.
im sitting at 5 targets around 133k dps. nice job
Thank you @orbalisk @tehzle @Simarlis . We appreciate you all. You’re such assets to the wow community.
pvp tchanges the 7th
Developers’ notes: Our goal for Arms Warrior is to increase their overall damage as their consistent pressure has been lower than we would like. We’re also reducing the effectiveness of their Colossus burst window as its damage was condensed into too small of a time period.
Amazing how they can pull arms out of a cave and put it right back in there within 2 updates. Arms became a kitty in plate again 
I just wish Arms dmg wasn’t so bad when you’re fighting a boss in your M+ build, while doing an M+ >_<
AOE wise it’s perfectly fine. I guess I’ll see if I get lucky with some of the Arms BiS pieces to see if that makes any real difference.
Been using your prot one for forever.
For some reason this one just freezes and says spell not learnt for me.
Did you check the blocks and see that it didn’t import corrupted? It shouldn’t have any blockers like that. 
i’m still looking into it but don’t get your hopes up since it’s at sim already in manual. BUT i can tell you that i’m watching at least one arms main on twitch and he’s doing decent on bosses with correct gear in both specs (slayer and colossus).
i’m still trying to figure something out for the aoe macro because i had a version already that was doing even better. problem with that version was it was garbage in raidspec since it was messing with the correct priorities there. THAT could be fixed though if people would just use sweeping strikes with the mod and just run the single target macro.
Might have been cause i was in pvp talents (colossus). Seems fine now!
Yeah I’ve watched Critcake who was doing a +18 key and he was doing pretty good dmg. I’m just trying to watch to see what he’s doing, but I do know Arms is very crit heavy, so maybe more crit 
wheres the pvp sequence?
Doesn’t exist.
/20char
oh my bad said pvp 1.2 at top 
Yeah, the sequence will work with just about any pvp build. Use change your build. Should be good. Arms ST DMG isn’t super great compared to fury imo.
Dear Author, I have been following your works. However, when I tried to use the code of your “Weapon Battle”, I found that it didn’t work. I don’t know if it’s due to my operational error or something else. Could you please help me? Thank you very much. Additionally, the macros you created are extremely well done.
There may be a translation issue. What are you trying to say? I don’t understand.
All right, so one thing, well, actually two things, I’ve noticed so far with the sequence, specifically while testing the AoE setup since I’m focusing more on Mythic Plus than raiding. Between the two to three minute mark, you become rage starved. You end up basically just auto attacking for a few seconds, which makes your overall DPS dip quite a lot. Once you finally generate some rage again, the sequence picks back up as your spenders come in and your generators start becoming available. What’s odd is that I think I’ve found a possible cause, but I’m not sure why it happens.
At the start, you use Avatar and then Bladestorm, which is completely normal since that’s how the sequence opens. But for some reason, Bladestorm will be fully available later in the sequence and it just will not fire. You have to manually press it to keep things flowing. Even stranger, there are moments when both Avatar and Bladestorm come off cooldown, and instead of using Avatar first, the sequence fires Bladestorm. It should be Avatar followed by Bladestorm to take advantage of the damage increase while spinning, so the behavior does not make much sense. I am still trying to see if there is a consistent pattern or if it is just happening at random.
So far, those are the two main issues I have run into. I do not know if this is something that can be investigated to see where the sequence might be skipping, or if it is just one of those quirks with GSE that cannot really be fixed. If you notice it, you may just have to use the ability manually to keep the sequence rolling. Since Bladestorm generates rage, using it on time might help reduce the rage starving problem as well. I am continuing to test, so it is possible I will find something that changes all of this, but that is what I have seen up to this point.
rage starvation may happen occasionally due to the nature of arms having only ONE skill (Overpower) that doesn’t cost rage while all others are spenders. in aoe, you want to press cleave with sweeping strikes up as much as possible. since we have to automate the sequence by priority and can’t do something like “if >amount_of_rage do X” we rely on procs and the priority of the buttons that don’t cost rage to circumvent the downtime window. this will usually go down around the 20% haste mark and may also depend on the speed of your button presses.
What I’m doing is replacing /cast [mod:shift] Pummel with /cast [mod:shift] Bladestorm – even with it being part of the automated sequence.
The reason for this is due to Bladestorm sometimes not wanting to fire off when it’s off cooldown. Also I have ` set as pummel and it instantly goes off when I use it.
So will run some more dungeons, but I do indeed more haste & crit on my character to be able to really seen the sequence and the build shine.
