GameCommanderPro

[Aarelan]

http://www.gamecommanderpro.com/node/57

Explain this too. This looks like scripting to me.

I assume you mean automations when you say scripting, as scripting is build into World of Warcraft, and is obviously not a problem (ie. macros, /script, mods via lua, etc.).

Let me say now that GameCommanderPro is completely legal and uses no automation.

GameCommanderPro only sends keystrokes to World of Warcraft. It only sends 1 keystroke to a window for each user keystroke. The fact that it looks like scripting is exactly the point we are making when we say that GameCommanderPro makes multi boxing more accessible. To take an example from your post,

Self Buffs
----------
KeyReset 6000
<<Vindicaer,Callidaer,Eversaer,Culexaer,Venenaer >>
if %KeyCount% = 1
Cast Buffs On Vindicaer-Target
<<Eversaer,Culexaer,Venenaer>>
macro /script CancelItemTempEnchantment(1)
endif

if %KeyCount% > 1
<<Vindicaer>>
Cast Righteous Fury on Vindicaer-Target
<<Eversaer, Culexaer, Venenaer>>
macro /use Lesser Firestone
macro /use 16 (16 is macro code for weapon hand one)
KeyReset
endif"

Although this is edited as one script its broken down into several macro and generates key bindings for each. The names in "<<>>" simply tell the key mapper which windows to send to. The "Cast" command generates a macro for WoW and a keystroke to invoke it. The "if" and "keyreset" statements simply provide a mechanism for casting a different spell on each press (see /castsequence on WoW website for details of how to achieve this).