My full AutoHotKey script.

[-silencer-]

I've seen so many questions on how to write or just setup AHK scripts, I'm posting my full AHK script here. I've recently re-written the entire thing, and although I've had no problems with initial testing, it's possible there's an error or two due to the massive amount of key combinations it's able to broadcast. There is absolutely no automation in the script - it's strictly key broadcasting with no added risk.

Here's the functionality involved:

- It is completely flexible with no modification needed for running different amounts of instances of WoW once you've got it set up for your at least your maximum amount. It's currently written to handle up to 6 instances of WoW at once (the amount of accounts I've used at once), but it could easily be expanded by adding a few lines to support as many instances of WoW you want. It will work perfectly fine using less than the supported instances. I've had it running with just one WoW instance, two, three, five, and six with no issues.

- F1 is my "formation spread" key, so it is broadcasted as a keypress down, and not broadcasted as a keypress up until it's released. This means the longer you hold the key, the farther apart your characters will spread. It broadcasts to all instances, so you'll probably want to unbind F1 on your main, and bind F1 to a different movement key on each of your alts. I have a commented section (using ;'s for commented lines) to go back to standard F1 broadcasting.

- All standard alphabetic keys are NOT broadcasted. I'm bad about forgetting to suspend AHK when I chat, and I hate character screens, social windows, bags, etc popping up while I'm chatting.

The commented section in the top of the script describes the functionality:
;================================================= ====================
; AutoHotKey Script by codeX* (aka -silencer-)
; - Flexible number of WoW instances. You can run from 1 to 6
; instances of WoW with no functional changes needed. All you
; have to do is reload the script.
; - Delete will toggle suspend script on/off.
; - The following keys are broadcasted:
; 1 to = (plus Shift, Control, Alt modifiers)
; F1 to F12 (plus Shift, Control modifiers)
; Note: F1 is my "spread" formation key, it works differently
; A to Z (only with Control modifier)
; Numpad Keys (plus Shift, Control, Alt modifiers)
; Arrow Keys (plus Shift, Control, Alt modifiers)
; Space (plus Shift, Control, Alt modifiers)
; Backspace (plus Shift, Control, Alt modifiers)
; [ ] (plus Shift, Control, Alt modifiers)
; 58-key X-Keys Pro Set (All have Shift+Control+Alt modifier)
; A to Z (26 keys)
; 1 to 0 (10 keys)
; Numpad1 to Numpad0 (10 keys)
; F1 to F12 (12 keys)
; Up, Down, Left, Right Arrow Keys
; - These keys are NOT broadcasted:
; NumLock & NumEnter
; A to Z, Shift+A to Shift+Z, Alt+A to Alt+Z
; Alt+F1 to Alt+F12
; Enter, Tab, Escape, ~, \, Insert, Delete, Home, End, PgUp, PgDn
; PrintScreen, ScrollLock, Pause, CapsLock, <, >, /
;================================================= ====================

Note that none of the alpha characters are broadcasted - I can't stand windows popping up while I'm chatting if I forget to suspend AHK. However, the alpha keys are broadcasted with Control modifier. Although I don't have an X-Keys Pro yet, I wanted the functionality ready when I decide to purchase one. There are 62 keys that are broadcast with the Shift+Control+Alt modifier, with the intended use to be with X-Keys Pro. I use these for my G15's 18 macro keys. There are no broadcasts using two combined modifiers, so that could be added for extra broadcasted keys if you have a full X-Keys keyboard you'd like to use alongside a regular keyboard.

If you have any questions, feel free to reply here.

Enjoy.

I didn't check the number of lines, but this is a large text file, so I can't post the full source here. Download it and take a look if you're interested.
(Attachments here have size restrictions, and it's 90kb uncompressed. Download this zip file, decompress, and load up my AHK script for massive key broadcasting goodness.)

[1Kurgan1]

Thanks for writing this script seems very nice, but I am completely new to this.

I am running a Warlock/Hunter combo and here is what I have noticed.

Lets say 1 is Shadow Bolt/Auto Shot, If I hit the 1 key it will try and activate both, but Auto Shot will never fire off. Now lets say 2 is Corruption/Raptor Strike, If I drag the mob by the front of my Huntard he will Raptor Strike.

I am assuming the problem is he will not grab the targets at range, is there anything in these commands I am missing that does this? Sorry if this seems like a n00b question, any help would be fantastic.

Also will it matter if both WoW's are running from the same drive/install or can they be on different ones?

[-silencer-]

Sounds like you're not using macros in-game on the /following toon to properly target the enemy.
Two simple solutions:
Have a key with this macro: /target nametarget (where "name" is your main character). Press that key after you target a new mob to have your /follower now target that mob, then continue on with your attacks.
Or..
For all /followers, change all your skills/spells to macros like this:
/target nametarget (or party1target, or focustarget.. depending on how you set up your macros)
/cast skill

Multiboxing is more than just loading up an AHK script. You have to configure a ton of in-game macros to properly target and use skills. The AHK script simply sends a keypress to all instances of WoW.

It doesn't matter where the WoWs are running from, as long as they are already running from the same computer when you kick off the AHK script.

[Beasthorn]

Thanks for taking the time to code this up and post it. I started using it last night and it is working out great. I had been limited to only the number keys + alt and I was just about out of room. This makes AHK very easy to use and is allowing me to bind a lot more keys

I really like the suspend key, I no longer randomly cast spells while entering way points in my map.

[wowphreak]

Ok something I dont get about the script

killbroadcast gets set to 0 at the start and for every key basically yeh check "If(%killbroadcast% = 0)"
but I dont see any place where it gets changed to anything else

Whats the point of "If(%killbroadcast% = 0)"?

[Grym]

Excellent, ty for the file.

Im still a nub learning how to 3 box but having fun so far. Before I multiboxed, I had all major spells on the numpad (Im a lefty so wasd setup is bad for me) so Id like to replicate this triboxing. The problem Ive had with my own AHK script is to get /*-+ on the numpad to broadcast.

The basic part of the script is:

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

Thanks for any suggestions.

[Lokked]

The numpad keys are listed as follows:

/ = NumpadDiv
* = NumpadMult
- = NumpadSub
+ = NumpadAdd
. = NumpadDot
<Enter> = NumpadEnter


Of course, this is all depending on your having your Numlock ON.

You can easily find things like this at http://www.autohotkey.com/docs/KeyList.htm.

[Grym]

Tyvm

Now back to trying to run (more efficiently now) a warr/druid/lock combo.

[Randon]

Hey guys, this might be a stupid question, but does it matter with this script which instance of WoW I want to be my main one? 'Cause no matter which order I start up WoW in/log on in, when I run the script it always brings my WoW2 into activity. Does this mean it thinks it's my main window? If so, how do I get around it using this script?

[-silencer-]

Hey guys, this might be a stupid question, but does it matter with this script which instance of WoW I want to be my main one? 'Cause no matter which order I start up WoW in/log on in, when I run the script it always brings my WoW2 into activity. Does this mean it thinks it's my main window? If so, how do I get around it using this script?

It doesn't matter which WoW window is your main with this script - it sends the same keystrokes to all WoW windows. The Wow2 activity you're seeing is just due to the way it recognizes the WoW windows when you kick off the script. For example, when I run 6 instances of WoW and kick off the script (with WoW1 being my main), it goes in this order: WoW1 -> WoW6 -> WoW5-> WoW4 -> WoW3 -> WoW2. So, WoW2 is the final window the script recognizes - I then just go back to the WoW1 window and play from there.

I'm in the process of cleaning up the script and adding more to it, but that probably won't be done until well after I'm done testing WoW on the SSD I should be receiving today. Expect test results later this weekend.