Possible WoW Macro?

[excepter]

Possible to make macro or isboxer command, spam Blast wave and AE?

[MiRai]

In World of Warcraft, if you wish to spam a spell or ability, then you will need to use a part of your body (e.g. your finger) to repeatedly press a key, button, or additional trigger.

[Ikevink]

If you are meaning a button that you spam that will basically blast wave when it's off cooldown, and otherwise it will arcane explosion, my strategy is to make a mapped key where "on key down" it attempts blast wave, then "on key up" it attempts arcane explosion, by setting it up as "pressed or released" in a 2 step mapped key.

[WOWBOX40]

If you are meaning a button that you spam that will basically blast wave when it's off cooldown, and otherwise it will arcane explosion, my strategy is to make a mapped key where "on key down" it attempts blast wave, then "on key up" it attempts arcane explosion, by setting it up as "pressed or released" in a 2 step mapped key.

This is actually handy, for all sort of classes.

Like, if you play a ele shaman, and you have f.ex "lava blast" set to a button: instead / in addition: also assign that same button (or link it to a macro) to when you "release" your f.ex "main single target dps macro button": it will then try to make lava burst go off. Sometimes it has a cd, but often, it procced and a instant version is available, which will then go off.
It increases your total dps etc by quite a bit.

You can also make this work for all your different classes/toons: if you got any handy "instant available spells" you would like to use as soon as its available, add it to the relevant "release button".

[Moorea]

doing different things on key up and down is imo crossing a line

[Psy-Crow]

doing different things on key up and down is imo crossing a line

I initially thought this, too, but I'm less concerned about it after seeing that the addon API supports it[1]. As far as I know, this is what's used by GnomeSequencer2 for its differing actions on key press vs key release. I do agree that it's a suspicious area and will be keeping an eye on whether Blizzard changes their mind about this. If they ever restricted the API around it, I'd take that as a clear sign.

[1]: https://wowwiki.fandom.com/wiki/UIHANDLER_OnKeyDown, https://wowwiki.fandom.com/wiki/UIHANDLER_OnKeyUp

[Moorea]

I initially thought this, too, but I'm less concerned about it after seeing that the addon API supports it[1]. As far as I know, this is what's used by GnomeSequencer2 for its differing actions on key press vs key release. I do agree that it's a suspicious area and will be keeping an eye on whether Blizzard changes their mind about this. If they ever restricted the API around it, I'd take that as a clear sign.

[1]: https://wowwiki.fandom.com/wiki/UIHANDLER_OnKeyDown, https://wowwiki.fandom.com/wiki/UIHANDLER_OnKeyUp

Those API won't let you cast spells in combat
Only way from addons to do things in combat is https://wow.gamepedia.com/API_SetOverrideBindingSpell afaik and there is no "up/down" modifiers there

[WOWBOX40]

Ive used this method for ages on isboxer, on my "/follow button":

step 2 (on release) = presses the button assiged to my "saved camera view that has the characters look behind themself", so that the slaves cameras allign when i release the key.

*can more easily herb using this method aswell, just got to backpedal my main a tiny bit.

[Wizeowel]

Ive used this method for ages on isboxer, on my "/follow button":

step 2 (on release) = presses the button assiged to my "saved camera view that has the characters look behind themself", so that the slaves cameras allign when i release the key.

*can more easily herb using this method aswell, just got to backpedal my main a tiny bit.

Sure but I think the point is more that you can't have combat actions on both keydown and on keyup.

I mean ISBoxer as standard has 3-4 different "keypresses" for your combat mapped keys.
keydown: assist and IWT (and move forward if you are using the IWT-melee-fix)
keyup: combat action

We would all be banned if that wasn't allowed.

And if you use GSE then you are often doing for example shield block, revenge and sunder as part of the same combat action. GSE sends 3 macros at once, and the one that isn't on cooldown wins. And since GSE is doing it, I am happy to risk doing a similar thing with my own ISBoxer set up.

However, personally I would draw the line at PW:Shield on keydown and Heal on keyup, because that is circumventing the mini-GCD you get from Weakened Soul in order to get a heal off anyway.

My conclusion is really that Blizzard doesn't really mind multiple keys sent, but they need to have that rule so that they can legitimise banning stand-still farming.

[Moorea]

because something is done for years isn’t making it ok; I removed auto assist once I realized it was doing 2 things for 1 key, and just put /assist in one of my ingame macro (with the side benefit of better control, I can switch targets with tank and start building aggro while dps finish a monster etc)