Macro using Heroic Strike

I am using the following Macro:

#showtooltip Mortal Strike
/startattack
/cast Heroic Strike
/cast Mortal Strike

This has been working for the past week. I have been playing most of the afternoon, and during my Prey Hunt, suddenly it will not work.

Looks like it stops and an error displays “Spell not Learned.” My guess they just made Heroic Strike not even available for consideration for use until it procs the upgraded Slam. The macro halts at that point, and Mortal Strike will not cast.

Anyone else use a macro for Heroic Strike?

1 Like

No, because it takes very little attention to hit your slam keybind when it procs.

2 Likes

The whole point is that he doesn’t want to do that.

6 Likes

Welcome to life, you don’t always get what you want.

But you can try to find a work around, and share ideas with other people on the forums.

6 Likes

Don’t know what has you angry, but don’t take your life’s failure out on me.
It was not a “I want” post it was a simple question about /cast command used in a macro that suddenly stopped working.

3 Likes

IIRC there is a condition that will break macros like that, and you’ll likely need to relog or /reload to fix it.

Some folks on the beta were testing some ways to automate using Heroic Strike – I’ll try to find the post. Just kidding all the beta posts are gone now.

Might be worth trying something like:

/cast [known: Heroic Strike] Heroic Strike; Mortal Strike
or
/cast [known] Heroic Strike
/cast Mortal Strike

Sorry I forget the exact syntax – you may need to tinker with that some. There is a [known] flag that might help. I think you’re always going to run into situations where the macro can break though.

EDIT: Archimtiros posted a functional macro below for those interested.

4 Likes

dont worry about greil, their the only warrior glazer. im honestly starting to think theyre the one in charge of warrior tuning and design and thats why warrior sucks so bad

5 Likes

Could be conflicting addons or the blizzard base UI breaking could be other factors like them fixing the option to do something like this on the back end. I know a simple /cast bloodthirst macro glitched out on me on wednesday and I had to drag the ability from the spellbook mid fight. Although it bricked on entering the raid did not test if it worked afterwards.

Ah yes, being realistic about expectations on lazy macros is just another glaze attempt got ya :dracthyr_blob_dance_animated:

If only you were so lucky Arms would be cracked out of it’s gourd and Fury would be redesigned away from the proc ridden mess it currently is.

2 Likes

Start attack is not necessary and has not been since around Cataclysm.

That aside, the actual macro to do what you want is

#showtooltip
/use [known:Heroic Strike] Heroic Strike; Mortal Strike
11 Likes

Thank you, that actually worked.

1 Like

Could have done that from the start without being a dweeb

5 Likes

I’ll try it, i really need it, seems like nobody likes to press slam… only cringe greil is pretending this is not big deal :joy::joy::joy::joy::joy::joy:

Life saver, thats the first thing i’ll do when i get home today

You can associate that with any ability by the way, not just Mortal Strike, you could even mix it with Charge (though I personally prefer combining Charge and Victory Rush).

Get creative enough, and you never actually need to press Slam if you don’t want to.

  • A few players have reported that the macro stops working for awhile. I’ve never had that happen to me personally, so I feel like it’s probably an odd addon interaction, but relogging fixes it regardless.

i pay you real money if you make a rotation macro where i don’t ever need to press slam, literally removing it from my bar

1 Like

Pretty easy to do tbh, just depends on how optimized you want it to be.

Can i make a macro where everytime my overpower is on CD slam is used instead?
And everytime heroic strike is up my mortal strike buttom uses heroic strike.

2 Likes

I’m not a macro Guru by any stretch but…

I think you coulld do

#showtooltip Overpower
/cast Overpower
/cast Slam

#showtooltip Mortal Strike
/cast Heroic Strike
/cast Mortal Strike

My understanding is the macto will try to use line 1 before it tries line 2. if line 1 ability is on cool down, it will default to line 2.

otherwise as mentioned above:

as mentioned, you could also swap mortal strike for OP and use heroic strike instead of slam, so

#showtooltip
/use [known:Heroic Strike] Heroic Strike; Overpower

I haven’t tried them (yet) but might be worth a shot.

This explicitly and purposefully does not work, because macros are not intelligent and cannot read cooldown, charge, or resource information, to avoid automating rotations. It will simply try to cast Overpower and never progress to using Slam.

This only works because of a quirk with the way ability overrides work. Heroic Strike is not actually known until activated by its proc, so the game will skip the invalid spell (just like if you put Aimed Shot there instead) and only attempt to cast Mortal Strike instead. Once the proc is spent, Heroic Strike is “unlearned” and the macro defaults back to Mortal Strike.

It’s the same logic that allowed Dragonflight Season 3 builds to use a macro to alternate between Bloodbath and Rampage. It’s not technically intended, but it’s not quite a bug either; just an unforeseen interaction. If instead of an override, Heroic Strike was a permanent spell in your book that only became available during the proc (like Classic Overpower always being known but only usable after a dodge or parry), then the macro would not work as it does.

1 Like

You are absolutely incorrect. Macros execute until a condition passes; this is not a quirk this is just how it works. One spell for one press – when a condition succeeds then the spell is cast and exits. This is the reason you can make key modifier macros:

/cast [mod:ctrl] Rend;[mod:alt]Battle Shout;Sweeping Strikes

The bracket is a [condition] and if false proceeds to the next entry. The above is equivalent to:

/cast [mod:ctrl] Rend

/cast [mod:alt]Battle Shout

/cast Sweeping Strikes

Cooldowns, particularly with cast sequence, will fail to the next statement even through multiple cast sequence lines. You can get pretty creative with macros but you’re still on the hook for pressing once per action.