Metalocalypse
10-26-2008, 11:37 AM
Hi all, I've been boxing for a while now, started with AHK and recently have fallen in love with the ease of hokeynet.
Up until now I used some code that I always thought was ok to use, since I found it on this site and never saw any negative posts in relation to it. However I was made aware of it being a 'grey area' way of doing things when reading into FTL setup.
Here's what I did/used to:
1) For formations I used one key, 2 toons strafe left/right, 2 toons strafe down and left/right (and other such combinations for formations).
2) For assisting I bound my assist macro to '=' and in my AHK script this button would be hit in conjunction with w/e other button I would hit.
It was suggested that my way of doing was 1 keypress resulting in 2 clientkeypresses. Which could be seen as form of automation. This got me worried, since I never saw it as such and had based my code on threads I read in these forums. I only used the above instances, movement and an assist, I don't use waits/sleeps or anything of the sort. I don't see the difference between modifier keys or normal keys since a window would need to be sent the pressing of the key to achieve the result you want.
I reread the wiki on AHK, it still mentions this:
Targeting is a major concern in any form of multi-boxing. AHK allows us to implement an auto-assist mechanism
relatively easily without the need to macro all of our abilities to include targeting.
The idea is to create a special key that you bind an assist macro to and to broadcast this key before
broadcasting the key that was pressed. An example assist macro can be:
/assist party1
/assist focus
Bind the assist macro to a key inside your WoW interface, for instance "=". Prepend all your broadcast keys
with "{= down}{= up}" effectively simulating an assist before using any commands. Not only that, in the legal issues this is stated:
Currently Blizzard allows the use of 3rd party key-broadcasting software, see GM Conversations ('http://www.dual-boxing.com/forums/../wiki/index.php/GM_Conversations'), however, automation is against the Terms of Use ('http://www.worldofwarcraft.com/termsofuse.html'). Automation can be defined as any action taken by your character in-game that is not the direct result of a user action.
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.
The rule of thumb is to ask yourself if what you do in your script can be achieve with an in-game macro. For example the auto-assist mechanism discussed below can be achieved in-game by macroing every ability and at the start of each macro adding an assist command.
So in lieu of this information, I would have to redo my formation buttons (or don't I?), but I could still use my assist button together with my cast button like:
<Hotkey 2>
<SendLabel wow1, wow2, wow3, wow4, wow5>
<Key Plus><Key %Trigger%>
Where plus is bound to my assist macro and the %trigger% is the hotkey I hit.
Could somebody give me a yes/no on this please?
Up until now I used some code that I always thought was ok to use, since I found it on this site and never saw any negative posts in relation to it. However I was made aware of it being a 'grey area' way of doing things when reading into FTL setup.
Here's what I did/used to:
1) For formations I used one key, 2 toons strafe left/right, 2 toons strafe down and left/right (and other such combinations for formations).
2) For assisting I bound my assist macro to '=' and in my AHK script this button would be hit in conjunction with w/e other button I would hit.
It was suggested that my way of doing was 1 keypress resulting in 2 clientkeypresses. Which could be seen as form of automation. This got me worried, since I never saw it as such and had based my code on threads I read in these forums. I only used the above instances, movement and an assist, I don't use waits/sleeps or anything of the sort. I don't see the difference between modifier keys or normal keys since a window would need to be sent the pressing of the key to achieve the result you want.
I reread the wiki on AHK, it still mentions this:
Targeting is a major concern in any form of multi-boxing. AHK allows us to implement an auto-assist mechanism
relatively easily without the need to macro all of our abilities to include targeting.
The idea is to create a special key that you bind an assist macro to and to broadcast this key before
broadcasting the key that was pressed. An example assist macro can be:
/assist party1
/assist focus
Bind the assist macro to a key inside your WoW interface, for instance "=". Prepend all your broadcast keys
with "{= down}{= up}" effectively simulating an assist before using any commands. Not only that, in the legal issues this is stated:
Currently Blizzard allows the use of 3rd party key-broadcasting software, see GM Conversations ('http://www.dual-boxing.com/forums/../wiki/index.php/GM_Conversations'), however, automation is against the Terms of Use ('http://www.worldofwarcraft.com/termsofuse.html'). Automation can be defined as any action taken by your character in-game that is not the direct result of a user action.
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.
The rule of thumb is to ask yourself if what you do in your script can be achieve with an in-game macro. For example the auto-assist mechanism discussed below can be achieved in-game by macroing every ability and at the start of each macro adding an assist command.
So in lieu of this information, I would have to redo my formation buttons (or don't I?), but I could still use my assist button together with my cast button like:
<Hotkey 2>
<SendLabel wow1, wow2, wow3, wow4, wow5>
<Key Plus><Key %Trigger%>
Where plus is bound to my assist macro and the %trigger% is the hotkey I hit.
Could somebody give me a yes/no on this please?