Quote Originally Posted by 'jdraughn',index.php?page=Thread&postID=119778#pos t119778
Forgive me if this has already been covered, but im a little confused. From what I can see this works by you pressing a key, and that key is sent to one wow window, then alt-thatkey is sent to a second wow window, shift-thatkey sent to the third wow window, ect... But isin't alt-somekey two key presses? ctrl-alt-somekey = three key presses? I thought we were supposed to only press one key per keypress, otherwise we risk violating the TOS. Of course, as far as the game is concerned, we are only performing one action, so we are ok in that regard, but that still does not cover up the fact that we are getting multiple key presses for pressing one key.

I would like some clarifcation on this. I would very much like to use this way of multiboxing but dont' want to do it until I know without a shadow of a doubt that it is ok with Blizzard.
K it's still just one key = one keypress. Keymaps are just a different way of binding keys, much like a spread out macro. I use z for my spread out, and that z keypress goes to each client, but each client does a different thing, one moves forward, another moves back, one goes sideways, etc. The keys are bound to different things in game. Keymaps flip that on it's head, so when pressing the 1 key, one client gets it, but the other clients each get a different key, and will act only upon the single keypress they are given. The modifiers are part of each particular keypress, they alter the conditional behaviour of the macro they're bound to, and they'll follow the order they are given. if Ctrl-shift-Period is follow toon #3, then that's exactly what it would do if I were to press those keys.

Multiple keypresses are things with pauses, which are possible with software, devices, even my keyboard can do illegal things if I were to set it up like it. Fireball, wait 1.5 seconds, fireball again. thats considered 2 key presses. It's the pauses and automation that blizzard is against, they want 1 key to behave how one key should, doing only one thing, then be done, waiting for the next input.

Even key capping, having one input key on the physical keyboard = 2 separate keys in the client, while technically 2 keypresses, I think is totally fine with blizz, because it's something that the player can mimic by pressing two keys at once. I used to have a spread out macro that formed an X, the main toon stepped back, one toon went forward and strafe right, forward and strafe left, etc. The keymap took my one z key and turned it into Up arrow and strafe right at the same time. It's a little iffy teritory, but you'd still be OK. However, if you put a timer on it, so it pushed the Up arrow and strafe right for exactly 1.25 seconds, then stopped, no matter how long or short you hit z for. That's automation, because they count the key-up as another keypress.