Is delay allowed?

[sharpMouse]

Thank you for the link to blue quotes, it was very informative.

The delay is officially "not okay", but it is mostly about GCD and spell cooldowns. I use delay only for /assist macro and only because current targets of nearby characters are updated with some delay. I guess this is against the word of ToS but not against the spirit of ToS: minion character does exactly the same thing as main - picks a target.

Also the idea to split keydown and keyup events is illegal:

"Just make absolutely certain that you’re not making more than one keypress (for the purposes of the word ‘keypress’ this includes a single key press AND release with no delays), or including delays between key-presses with each action."

It works just because, in practice, generating several keypresses simultaneously is not punished.

[mbox_bob]

Actually I am doing the same. My program stops sending queue for some time and then continue to process sending queue.

I call it "delay" and may be it is wrong word but I guess Blizzard doesn't care about words.

Aye, they would not mince words. It would be called a bot. Because with enough stopping and continuing of the "sending queue", and the appropriate keystrokes being queued up, you could start it off, walk away from the computer, and the toon will continue to play the game all by itself. This is pretty much the definition of a bot.
You may not be taking it quite this far, but how are we to know? You yourself must realise all this already, otherwise you would have posed your question on Blizzard's forums.

I tend to agree multi step isboxer keymaps specially with "Do not progress to the next step for X time" is indeed the same as a delay

No, ISBoxer's implementation of "Do not progress....." is not the same. It does have a progression delay in the switching to the next step, within the ISBoxer configuration, however it DOES NOT EXECUTE the next step all by itself when that delay happens to have expired.
If you start a mapped key sequence in ISBoxer, and walk away from the keyboard, it will never finish that sequence, because it requires you to press the hotkey to progress the next available step. i.e. it stops sending any keystrokes to the game the moment you stop pressing keys on the keyboard.

[MadMilitia]

It's nuanced but think of it this way. You can't ever get isboxer to do something you yourself didn't initiate.

Sure, just like in WoW you can have 1 key do almost everything and many of us have tried but it's not the same at all as pressing one key and walking away from the computer while it works itself.

And this is exactly why the WoW API and CastSequence macros are severely limited. So you can't macro a gaming keyboard and write giant logical routines to do all your work. For example procs. Procs to be played 100% efficiently need to be done entirely at random of your normal rotation. You will never even get close to 100% efficiency with procs on a CastSequence macro. Not ever. Every lazy macro out there that uses CastSequence has a keymodifier that intiiates the use of the proc. Basically, the user is then pressing alt/shift/ctrl whatever and their 1 DPS button. This is no different than them having multiple buttons in their layout which they initiate.

Hopefully that makes more sense. This issue was sussed out over a decade ago. It's not as if you found IsBoxer and then found something illegal in it a decade after it has been researched.

[Sservis]

Also the idea to split keydown and keyup events is illegal:

"Just make absolutely certain that you’re not making more than one keypress (for the purposes of the word ‘keypress’ this includes a single key press AND release with no delays), or including delays between key-presses with each action."

It works just because, in practice, generating several keypresses simultaneously is not punished.

I'm assuming you're responding to others. I was very particular in that I said leader on key down and others on key up. Each character in that case is still just one action per keypress and this is fine. You can then create your own variable length delay by holding the key.

[aasi888]

I'm wondering if I can do this on a single key press:

keydown (Master):

/startattack
/cast Spell

keyup (Slaves):

/assist Master
/cast Heroic Strike
USE IWT hotkey

Is this allowed and is this how ISBoxer does this? IWT + Cast is done at the same time? I couldn't find anything in the docs: http://isboxer.com/wiki/WoW:Interact_with_Target

EDIT: Specifically I want to know if the key-up action you can see up here is OK (or do I need to separate the IWT from it).

[Sservis]

I'm wondering if I can do this on a single key press:

keydown (Master):

/startattack
/cast Spell

keyup (Slaves):

/assist Master
/cast Heroic Strike
USE IWT hotkey

Is this allowed and is this how ISBoxer does this? IWT + Cast is done at the same time? I couldn't find anything in the docs: http://isboxer.com/wiki/WoW:Interact_with_Target

EDIT: Specifically I want to know if the key-up action you can see up here is OK (or do I need to separate the IWT from it).

I would expect this to be fine the triggering of the actions to be fine. For what you're doing on the trigger, the question to ask is "Could I write an in game macro (or addon) that does that?"