Thread: Sending Keystrokes on Any Action

Originally Posted by Jenzali

@Pliaksi - You are absolutely correct, and I have decided to no longer use anything related to mouse movement to achieve this. This is just too dangerous and I don't want my account banned.

The solution I will go with is to spam only on actual keypresses or scrollwheel clicks.

It's not so dangerous if you simply build in a random lag/jitter to the keystrokes. Easily done with an extra line or two of code in AHK.

Originally Posted by Khiseer

I use this AHK-script for my prospecting and disenchanting

Code:

WinGet, wowid, list, World of Warcraft

9::
KeyWait, 9, D
   ControlSend,, 9 , ahk_id %wowid1%

Return


8::
KeyWait, 8, D
   ControlSend,, 8 , ahk_id %wowid1%

Return

It works really good. (when im pushing 9 out-tabbed. it pushes 9 in wow that i got my de-macro on. and same for prospect but 8 on that)

A tip is that u just press that buttons or bind them for another keystrokes and just watch a movie or something and press it every 3 second.

This seems a bit unnessecary to be honest. You can achieve the exact same efect by having your video player as always-on-top, or having your WoW window minimised to just "header" but still having the focus on it.

I went looking for some more help on MMOwned for those interested in using this kind of script. LF Help in modifying an autohotkey script

I said:

1) I need a way to distinguish between my 2 World of Warcraft clients and only send the keypress to one of the client. This is not absolutely a must have but it would be nice.
2) I want to make the keypresses that it sends more random. Prospecting/milling takes about 2 seconds to cast, so it would be great if there was a way to randomize the time in which it sends those keypresses within that 2 second window. I'm using it for a legitimate use where it only sends the keypress upon mouse movement, but I simply don't want to deal with the inconvenience of Blizzard banned me thinking I was botting.

Edit: Something I realized is that adding a delay to your AHK script is apparently against Blizzard's ToS, so please don't include that part.

For AutoHotKey this means that any kind of delay introduced in your script between sending commands is classified as automation and will get you banned. Please avoid using any kind of delays in your scripts as not only will it get you banned but if Blizzard finds that people abuse AutoHotKey to achieve automation then they may decide to ban AutoHotKey altogether.

http://www.dual-boxing.com/wiki/index.php/AutoHotKey

@Jenzali , this is interesting. I sent in the same ticket that you did and got this:

Originally Posted by GM Prynovarr

Hey there,Unholyshield!

I am very sorry that I was unable to speak with you while you were online, and for the time it has taken to respond to your ticket.

Unfortunately this isn't a ruling that the Game Master team can make without further information. Your best bet is to use our Interface and Macros forum for this, as our Community team can give a better ruling, and a more detailed description on how this will be achieved.

We appreciate your patience and understanding, and wish you the very best of luck with your future gameplay experiences.

Actually I was trying to help him build a script of his own, but if you would like to have one posted here with random intervals, random events and all that - I can do ot without much trouble. I just need to get back to my work PC and this will be in 1-2 days.

[21:23] <Stede> ControlSend,,=,World of Warcraft
[21:24] <Stede> ^ above that line of code, use the following lines:
[21:25] <Stede> Random, rand,1,500
[21:25] <Stede> sleep rand
[21:25] <Stede> ^ those 2 lines will add in a random bit of lag between 1/1000th and 1/2 of a second

[21:23] <Stede> ControlSend,,=,World of Warcraft
[21:24] <Stede> ^ above that line of code, use the following lines:
[21:25] <Stede> Random, rand,1,500
[21:25] <Stede> sleep rand
[21:25] <Stede> ^ those 2 lines will add in a random bit of lag between 1/1000th and 1/2 of a second

Just to clarify, the script that I posted earlier is quite literally illegal as it is periodically checking if the mouse has moved, as opposed to direct human input.

If this was legal, then you could simply put your mouse on a rotating platform, so it's botting because it's not a distinct human input.

The scrollwheel is really as good as it gets in terms of spamming.

The random delays that Sinshroud is using may make it more difficult for Blizzard to detect you, but I would be almost certain that their Warden has means to track this down.

In short: never send keypresses unless you're pressing a key, or rotating the scroll wheel. Every in-game action must be the direct and immediate result of a human action. This relationsihp must follow either the one-to-one relationship (I press a key, the game receives a key), or one-to-many relationship (I press a key, multiple WoW clients all receive a key. This is used all the time in multiboxing).

I also posted this same thread at dual-boxing.com, many of the posters there are experts and determining what is and isn't automation. This is the response from one of the moderators:

I'm sorry, but there is no way to validate that that is an actual Blizzard response. It's a quote on a random message board. And if it is the response you received, all it says is it "may" be fine.

Feel free to bring it up with Svper, but as far as I'm concerned this falls into automation. Especially since looking at your code, the script is running timed checks to see if mouse position has changed and executing itself based on previous actions. It is not instantly or directly responding to user input. I could simply turn on my TV and put my mouse on my subwoofer and that script would still send actions to WoW.

You may think it's an innocuous timesaver, but you change the macro being activated to a combat macro and it's a bot. You zone into a Battlegrounds, it's a bot. You put the mouse on a subwoofer, it's a bot.

This forum is about multiboxing video games, not one about how to make gains without having to interact with games. If you want to use it, that's your prerogative, but that sort of topic doesn't belong here.