Sleep and keywait command

[Theanara]

Well i just need to ask about the legality off both commands in Autohotkey.

First you have the sleep command, which is an automated pause for a certain amount off time within the script.
for example:
i press the left key then it starts the following script:
move left on all chars
sleep for 400 ms
stop moving left on all chars.

this to always let them move the same space to the left.

(im not posting a script as i suppose this is illegal as its automating a process)

But what about the keywait command?
it will become something like this:
i press the left key (and keep it pressed)
all chars move to the left
keywait till my left key is no longer being pressed
stop moving my chars to the left


It is not a real automated process i suppose, so it should be legal and not against Blizzards rules, what do you think?

[thinus]

I am using Keywait to wait for key ups and staying far away from the sleep command. So I agree wholeheartedly with your views.

[Djarid]

Yup keywait is fine but sleep is a no no.


Blizzard have time and again said that if one keypress = one action the it is ok (even accross multiple accounts)

[Maparrra]

KeyWait isn't working too well for me. It's extremely unresponsive and I have to hold it down for 5 seconds before I see any movement(and no, not due to latency, it's just not moving unless I actually hold it down for a while - not even a little bit). Here's what I tried:

Numpad8::
#IfWinActive, World of Warcraft
{
ControlSend,, {Numpad8 down}, ahk_id %wowid1%
ControlSend,, {Numpad8 down}, ahk_id %wowid2%
ControlSend,, {Numpad8 up}, ahk_id %wowid1%
ControlSend,, {Numpad8 up}, ahk_id %wowid2%

}
KeyWait, Numpad2, U
Return

And it keeps going when I hold it down - but only in little burps and segments. I know someone is going to say latency, so let me just re-iterate: there is no distance moved at all if I only hold it down a short period of time. If it was latency, that would still get sent eventually and show some distance moved.

[splorygon]

KeyWait isn't working too well for me. It's extremely unresponsive and I have to hold it down for 5 seconds before I see any movement(and no, not due to latency, it's just not moving unless I actually hold it down for a while - not even a little bit). Here's what I tried:

Numpad8::
#IfWinActive, World of Warcraft
{
ControlSend,, {Numpad8 down}, ahk_id %wowid1%
ControlSend,, {Numpad8 down}, ahk_id %wowid2%
ControlSend,, {Numpad8 up}, ahk_id %wowid1%
ControlSend,, {Numpad8 up}, ahk_id %wowid2%

}
KeyWait, Numpad2, U
Return

And it keeps going when I hold it down - but only in little burps and segments. I know someone is going to say latency, so let me just re-iterate: there is no distance moved at all if I only hold it down a short period of time. If it was latency, that would still get sent eventually and show some distance moved.

You should start a new thread for your problem instead of posting in an existing thread which has nothing to do with your problem.
I think what you really want is:

#IfWinActive, World of Warcraft

Numpad8::
ControlSend,, {Numpad8 down}, ahk_id %wowid1%
ControlSend,, {Numpad8 down}, ahk_id %wowid2%
Return

Numpad8 Up::
ControlSend,, {Numpad8 up}, ahk_id %wowid1%
ControlSend,, {Numpad8 up}, ahk_id %wowid2%
Return

[Maparrra]

You should start a new thread for your problem instead of posting in an existing thread which has nothing to do with your problem.
I think what you really want is:

Uh, I think it's pretty relevant given the fact that we're talking about people switching from the Sleep command to KeyWait in order to avoid any disputes about the EULA. I'm not sure how much MORE relevant this could be Even if it wasn't, there's plenty of room for side conversation here about a subject with has at least some relation with the original topic. I don't see why not.

Either way, thanks for the code and I'll try it out later.