Quote Originally Posted by MadMilitia View Post
When you check 'Do not progress to the next step for' and give it a value, it means you can spam click that button that entire length of time and it won't go to the next step.
While I don't personally agree with the nature of timing, I can't find much issue in an action NOT being sent to the game. Really, you're blocking an action to ISBoxer and it's kind of hard to see much difference between blocking a step from progressing and blocking which client receives a keypress like in round robin broadcasting at that point.

If you take it one further and check the box that says 'And only trigger once' it will only send the actions once, regardless of how fast or how often you repeat the step.
So will the ingame macro of /castsequence reset=* spell, nil

If you exceed the time listed in step one it then goes to step two.
Ok? This still doesn't resemble automation as found in the macro software in gaming mice/keyboards that I warned against. You are just trying to use a similar-sounding function to build a pro-automation argument. There's a difference between a response to "Do this" that comes back "I can't" {ISBoxer} and the response that comes back "I'll do it later," {true delays aka wait commands/automation}. ISBoxer has "repeating" too, that doesn't mean because it's ok to duplicate a keystroke to 5/10/40/800 windows once per press, then it should be ok to send a series of 5/10/40/800 keystrokes to one window per keypress.

FYI, the day they ban people for using LCore or Synapse, which comes with gaming hardware is the day they are publicly ridiculed and deserted.
They don't ban simply for using the software, they ban for violating the game's rules. Pretty much any answer ever given by blues {and many other game companies} on stuff like this all include the words "As long as it stays within the ToS."

You, as a multiboxer, should know the difference between good touch and bad touch seeing as we argue day in and day out how multiboxing isn't botting and we don't use automation. If you don't, here's The Rules Thread and here's the Blue Posts Thread.

You are trying to create a grey area where automation is ok, using multiboxing as precedent and disability as moral justification. There is a No Tolerance Policy here on discussion that advocates for violating the rules of the games we play. We've got enough drama around us as it is.

So let me spell it out since people are going to come to this thread in droves looking for answers on how to do macros for WoD -

Automation is not the proper response to creating macros, dealing with game changes or any other multiboxing problems.