1 button IWT and dps

[Lax]

I must have hit a soft spot.

You do know that the articles in the news articles in there are made up right?.

Yes. I am glad you got the point of me linking to THE ONION that has a funny article about you! Lighten up! I never said the article called the man a tea partier, I said something relevant to what you're doing, then I added a link that that made me think of, and I wrote a poem! I'm happy that we can share and enjoy satire together.

as stated on wow forums, programmable keyboards that spam keys for a user are not permitted by the TOU and is a bannable offense. remember the n52 bans? the horrible number of people that got their honnor reset plus 72 hour account suspensions over the use of poor automation? the people who kept on doing it after their 72 hour bans, got permibanned. Your GM Malkorix is pretty clear that one key means one key in his quotes listed on the dual-boxing wiki, even if it is just one other key.

Because it sounds like you missed it, here's a quote from me on page one of this thread: http://www.dual-boxing.com/showpost....44&postcount=6

Here is what you need to know:
1. You become "automatic" when something happens without you manually adjusting some input control (key, switch, dpad, joystick, throttle, slider, motion sensor, etc) to kick off that action at that particular time. Example... some gamepads have a continuous fire mode where it will repeatedly press a button over and over at some time interval. Any delayed action is considered to be a part of this category.
2. You become a "bot" when you sense game information (e.g. player's health) in order to automatically respond to it (e.g. heal, switch dps modes, etc)

These are both not allowed in WoW, or most other games. Neither of these things are available in ISBoxer (or most other multiboxing software).

... so I'm glad that we're on the same page with automation. But that's not what I am talking about when I say "spam keys"... If you program your n52 to repeatedly press a key (or different spells in sequence for example), this requires delayed action that isn't happening at the time of them pressing the n52 key. I am talking only about pressing and releasing keys at the time you are pressing and releasing physical buttons or moving other physical controls (or in some cases, as with the Kinect, not even physical controls).

its nice to see the extension of the topic from binding IWT to a keyup event being legitimate or not, to all of the other issues you have experienced in your development of ISBoxer, however, it confuses the point and brings in items not inheriantly relevant to the arguement. Also, the addition of those topics does not shed light on how IWT activation on a Keyup event is a legitimate under TOU. It however seems more like a cry out that "look at all of these other things that may have been bad before that are ok now. by ok, i mean no one I know of has gotten banned by it, and by now, I mean so far..." My arguement attempts to establish the precidance for why IWT on a keyup event is not permissable.

This is irrelevant because it doesn't need to be on keyup. It can be done at the same time as your attack. You can press your IWT key at the same time as your DPS key. Like holding 1 and 2. You can also hold W and A to go forward and left (with the default WASD).

Some people prefer to separate that into one on key down one on key up. Okay. Why not? This is two separate input events. WoW fires these separate events for Addons, too. They recently changed hotkeys to fire on press by default, with an option to fire on release, probably because some WoW Addons did that and people liked it. Did you ever notice that sometimes outside ideas get incorporated into games, because they're good ideas?

Some buttons are physically toggle buttons, they stick down when you push them, so that you have to push it again to pop it back up. Pretty much all keyboards have logical toggle buttons -- caps lock, num lock, scroll lock -- so it should be relatively simple for you to imagine changing that digital control to an analog control. A toggle button is like a switch. So say I have a switch control (and actually I do on a few keyboards), should I not be allowed to make that control do something when I move it to the left, and then something else when I move it to the right? What if I move the switch to the left and to the right really quickly? What if I have a whole panel of switches! ... now, why exactly did you want me to have to pay for a switch panel when I have this perfectly good keyboard, a G13, and a Razer Naga?

My entire point of describing various types of input controls and ways of interacting with the game is because there are some really genuinely cool things that people are doing, that these so-called "litmus tests" from blue posts (which as you have so kindly made sure to point out, are not necessarily GMs, but that's entirely beside the point) that are so often quoted, may not even be relevant to at all. These input controls are based on the precisely same things that you're saying should not be allowed.

Blizzard are working hard on real problems, they don't want to police petty bullshit like whether or not you are allowed to use a joystick, dpad, foot pedal, Kinect, dial, switch, push button, toggle button, etc to control your character. They just don't want you to automate or bot. That is what is in the TOU. Keyup/keydown is not in the TOU and you are not setting precedent...

Edit: Also on topic, Steelseries advertises their Officially Blizzard-licensed Shift Cataclysm keyboard (another keyboard I picked up) with this specific capability displayed in the Cataclysm keyboard promotion:

3. Record a sequence of actions, with delays included, and map them all to a single key

Source: http://steelseries.com/products/game...hift-cataclysm