@OP
I honestly don't know where this post is going, if its for the OP really want something that isn't a TOU violation or if it is a "hey how did that one guy do that to me" kind of post...
@ualaa
your links are to the old website and do not redirect to anything other than the forum main page.
Anyway, here is some quotes that I found while looking for the blues guidence that you can add to your refference on the topic ...
"To very quickly start with the multiboxers, these players genuinely aren’t breaking any of the game Terms of Use as they still have to control everything that each one of the characters is doing – software can be used in order to replicate key presses multiple times across all the open game clients (which is why the characters will mostly perform all their actions at the same time), but there’s still a person at the other end of the PC pressing the buttons to determine what all the characters do."
http://eu.battle.net/wow/en/forum/topic/1710231935
ergo, if you didn't press the key when something happened ingame, you are violationg tou. another post regarding keyboard software macroing goes on to state the litmius test used.
"...So the question remains, is what you are trying to do possible within the in-game macro system..."
http://us.battle.net/wow/en/forum/to...3276242?page=5
Ualaa touched on this with Lax following up when he talks about keymashing vs. key spamming. While I can spam four different keys on my computer, I can only mimic that spamming ingame when those keys are macros in a cast bar slot and not movement nor ITW keys (macro with clickcasting). As stated before, you can physically spam 2 different keys, no one cares. however, if you spam 1 key and the action is 2 non combinable key presses being spammed, this is not allowed.
I think Ualaa talks about how keyup and keydown are two different key events and thus although you are physically pressing and releasing a key IRL, you are creating two seperate wow key events. I accept that when dealing with movement, this is allowed otherwise, we would forever sit and spin till a mouse stearing event would occur. (an interesting way to get rid of keyboard turners). However, no where in the game keybindings interface can you bind something to a "keyup event" Thus we can not accept that a "keyup" event outside of movement directional keys is a valid seperate key event even if it is considered as such by the OS, there is no precedance in wow. Thus it is automation by Lax's and the blues standards stated
Lets face it, the wow community and the blues aren't up to date with what people are doing who multibox as the conversations don't really get pass the whole "one person controlling multiple accounts" part on EVERY multiboxer post that is out there. The dual-boxer community needs to let go of these old tired examples that no longer apply to current feature use as justification for automation.
so where does this leave this forum hijack?
from the litmus test described above, there is no way for you to hit one key and have it hit the IWT keybind and press another dps keybind until we can bind actionbar slots to keyup events, or until IWT can be called from a macro.
Connect With Us