[?] Multiple Steps under Mapped Key

Would someone be so kind as to point me to a guide (or something) that explains the uses, advantages and disadvantages of having multiple steps under a single mapped key? I know how to make them, how to remove them and I've even been using some ... I'm simply not sure that I'm using them properly.



[If a guide or something doesn't exist that explains ...]

Example 1:

• "Follow Warden", Hotkey: Q, !hold, press or release
  
  • Step 1 -> F1 -> all other
  • Step 2 -> F2 -> all other
  • Step 3 -> = -> all other

Example 2:

• "Follow Warden", Hotkey Q, !hold, press or release
  
  • Step 1: F1 -> all other
  • Step 2: F2 -> all other, = -> all other

Example 3:

• "Follow Warden", Hotkey Q, !hold, press or release
  
  • Step 1: F1 -> all other, F2 -> all other, = -> all other

(F1 to select self, F2 to select fellowship leader (always the same character), = to call an alias shortcut that calls /follow. Example keymaps are for LOTRO.)

Would someone be so kind as to explain the difference between these examples in terms of what ISboxer/InnerSpace are doing? Which of these examples should I be using (and why)?

[Ualaa]

Steps are subsequent actions that occur on different presses of the same key.



I have one which sends Q to two Slots, and E to two other Slots on press 1.
(And holds, while the key is held).

It then sends Q to one of the two Slots and E to one of those two Slots, on press 2.
(Again holding the keystroke while the key is held).

Q = strafe left.
E = strafe right.

End result, two toons move left and two move right, on press 1.
And on press two, one moves left and one moves right.
Creating a line.



If there is latency in your game...

I have set my Death Grip (which assists the active window) to be a two step action.
Step one is the assist.
Step two is the Death Grip.
It is set to execute an action on press or release.

The amount of time between pressing the key and releasing the key, gets the client a little extra time to assist the correct target.
Plus I can press the key, hold for half a second, and release... if latency is particularly poor.

Steps are subsequent actions that occur on different presses of the same key.

Ah. Let me see if I'm understanding correctly:

[Example 1]
Press "Q"
-> Step 1 executes, Client receives "F1", ISboxer advances to Step 2
Release "Q"
-> Step 2 executes, Client receives "F2", ISboxer advances to Step 3
Press "Q"
-> Step 3 executes, Client Receives "=", ISboxer advances to Step 1
Release "Q"
-> Step 1 executes, Client Receives "F1", ISboxer advances to Step 2

[Example 2]
Press "Q"
-> Step 1 executes, Client receives "F1", ISboxer advances to Step 2
Release "Q"
-> Step 2 executes, Client receives "F2" and "=" (in that order?), ISboxer advances to Step 1

[Example 3]
Press "Q"
-> Step 1 executes, Client receives "F1", "F2" and "=" (in that order?), ISboxer advances to Step 1
Release "Q"
-> Step 1 executes, Client receives "F1", "F2" and "=" (in that order?), ISboxer advances to Step 1

[Stuff]
... if I'm correct, that explains the behavior I'm seeing in-game (as I'm using [Example 1] at the moment) and I should start using [Example 3] in order to reduce my need to spam "Q".

[Ualaa]

You can configure it to execute a step on:
- Press
- Release
- Press or Release.

But essentially, however you set it to execute the step...
Each time it gets the signal to advance, it does so.

If set for Press or Release, you get Step 1 on press and Step 2 on release.
The other two, get you a step for each press/release cycle, executing the step either on the press or the release, but not both.

[Example 3]
Press "Q"
-> Step 1 executes, Client receives "F1", "F2" and "=" (in that order?), ISboxer advances to Step 1
Release "Q"
-> Step 1 executes, Client receives "F1", "F2" and "=" (in that order?), ISboxer advances to Step 1

The key presses are sent to LotRO at the same time, as though you pressed "F1","F2", and "=" at the exact same instant.