IsBoxer IWT + DPS HotKey legality question

I have read constantly about "One button press needs to equal one action". After doing some research I have noticed that its quite normal for people to have their IWT keybind be send along with some DPS keybind. In fact many even toss in an extra keybind of MoveForward before the IWT to help with the melee pathing issues that go along with it.

So with this setup one button press would end up being three actions: MoveForward, IWT, DPS hotkey.

Its my understanding that there is no macro script to execute IWT or a move action. Thus the MoveForward, IWT, and the DPS hotkey would require 3 different key combinations to be sent at once to the client.

Am I just incorrect in my concerns about one button needing to be one action?

IWT (when targeting an enemy) will start your auto attack and move you in range to auto attack the enemy.
I'm not exactly sure how what you're saying is put into ISBoxer, can you give a specific link to someone's ISBoxer command that is doing what you are saying?

it's fairly common to have 2 step keymaps with 1 step on keydown and 1 step on keyup, I suppose that's technically 2 things for 1 key ?

I'll quote Lax on this:

Quote:

---

No, that is not automation. "1 key = 1 action" was part of a longer explanation by a Blizzard poster, and the boiled down phrase "1 key = 1 action" is misleading. They essentially want you to not be a bot, and not otherwise violate the rules of the game.

The game already limits you from doing more than one thing, e.g. by Global Cooldown. If you have a button that presses both W and A so you move forward and turn, while you only hold one button to do that, nobody is going to blink an eye at you. Similarly, if you have a button that presses both 1 and 2 when you press 1, nobody is going to say you're botting because of that. You can set up /castsequence macros in the game and other similar mechanics via WoW's macro system, so you don't really have to make it press more than one button if you don't want it to.

---

I think the hotkey example is fairly good. I could definitely assign a button on my naga to press Cttrl+1. That is 2 button presses from a single key just as well, yet I doubt anyone would have an issue with that.

Quote:

---

Originally Posted by Syclone

I have read constantly about "One button press needs to equal one action". After doing some research I have noticed that its quite normal for people to have their IWT keybind be send along with some DPS keybind. In fact many even toss in an extra keybind of MoveForward before the IWT to help with the melee pathing issues that go along with it.

So with this setup one button press would end up being three actions: MoveForward, IWT, DPS hotkey.

Its my understanding that there is no macro script to execute IWT or a move action. Thus the MoveForward, IWT, and the DPS hotkey would require 3 different key combinations to be sent at once to the client.

Am I just incorrect in my concerns about one button needing to be one action?

---

At no time has it been stated by Blizzard that "One button press == One Key being sent to the game client".
There is nothing stopping you from pressing 50 keys at once on your keyboard (other than the size of your hands maybe - I can get comfortably get 4 keys with one finger). How the game interprets the deluge of keystrokes at the same time is up to the game. Same with if you happen to configure your programmable gaming keyboard to, on one press of a button send 10 different keys to the game at the same time.

The "one button press needs to equal one action" is meant to be taken as your one button press is not allowed to execute a programmed sequence of keys, with the no doubt needed timed gaps in order to get a desired result, which happens to be very bot like. This is what they are not wanting.

If you have 10 keys as a result of one button press, then those 10 keys need to be sent to the game all at the same time, which actually meets the "one button press equals one action" requirement. That one action is to send 10 keys at the same time to the game.

As others have pointed out, it's a generic phrase, and, even if it was said by Blizzard, it's incredibly vague. I say this because... Can you actually define what an in-game "action" is? Go ahead, try it.

Are any of the following considered in-game "actions?"

• Targeting
• Assisting
• Setting a focus target
• Toggling the in-game map
• Casting a spell

All of the above can be individually bound to keys in the game's key bindings menu, so should they be defined as an action? Why or why not?

Code:

---

/focus Character3
/target Character1
/assist
/use Trinket (off the GCD)
/cast Spell
/script ToggleFrame(WorldMapFrame)

---

Six actions in one macro?! No way!
And it can be bound to a single key press?! Impossible!

If you'd like, you can add even more in-game "actions" into the above macro, so where does the "one key press = one action" statement fall now?

Yeah, I have assigned Assist+IWT onto a programmable key on my keyboard since for ever with no issue. Its not a big deal thing and there is also that WoW setting "Interact on Left Click" which already automates the process for your main char anyway. I have been wondering though why they never put IWT into the API.