[WoW] What to do until /follow is fixed?

Hey, first post here :)

I've just got into the idea of playing two wow accounts off the same computer (It can handle it) and it works fine except the /follow disconnect problem that seems to be around. Enabling vsync didn't work and so I'm currently looking for a work around until it's fixed.

Obviously I could tab between the two client windows and move both characters, however I was wondering if their was an easier way to do this? Using priests so it doesn't have to be perfect, as long as it's the same direction and relatively the same position (like follow)

Regards,

Zaza

Strange, I was never disconnected when following =/

Is this the issue your referring to? Where you /follow anyone and WoW disconnects as if you clicked a bad item link? If so my heart goes out to you, that problem looks like its in a slog of voodoo for a while.

I find the coding logic behind /follow to be always interesting. Its obviously not just following the other character or even just taking pathing cues from the other character. But there is some upkick in communication that is blizzard to me as well. You can see this in how until recently patch characters interacted when they were walking near each other the speeds would change. Or how /follow-ing a mage would prevent them from blinking.

And if you think about it, pet pathing is pretty damn spiffy in WoW, even though its comical and irritating at times.

Yes hpavc, that's the issue I'm referring to unfortunately.

It's maint/patch tonight (for the EU at least) so it's possible, although incredibly unlikely, that it will be fixed... not exactly getting my hopes up though.

From what I can tell, there's communication between the follower and the person being followed which is building too high and the server is kicking the follower off to reduce this load. If you wait a while and try again, it takes longer to get kicked (about 3-4 minutes at a rough estimate) and the more action you take the faster too, however standing still seems to actualy work in an opposite way and increase the rate of being disconnected, which seems contrary to logic (,since standing still would surely require no communication?).

Does anyone have any alternative solutions until this issue is fixed?

Thanks



;Edit

Well, I've edited my AHK script to include wasd keys for movement (hopefull) however as the EU servers are down for 3 hours 40 minutes I was wondering if anyone else could tell me if this solution would actually work?

All I have done is add the following to the script;

(As reference, are the keys case sensitive? So is 'e' the same as 'E'? Does one work and not the other?)

[code:1]; *******************
; *** WASD ***
; *******************
#IfWinActive, World of Warcraft
~w::
ControlSend,,{w down}{w up}, ahk_id %idMain%
ControlSend,,{= down}{= up}, ahk_id %idClone%
ControlSend,,{w down}{w up}, ahk_id %idClone%
return

#IfWinActive, World of Warcraft
~a::
ControlSend,,{a down}{a up}, ahk_id %idMain%
ControlSend,,{= down}{= up}, ahk_id %idClone%
ControlSend,,{a down}{a up}, ahk_id %idClone%
return

#IfWinActive, World of Warcraft
~s::
ControlSend,,{s down}{s up}, ahk_id %idMain%
ControlSend,,{= down}{= up}, ahk_id %idClone%
ControlSend,,{s down}{s up}, ahk_id %idClone%
return

#IfWinActive, World of Warcraft
~d::
ControlSend,,{d down}{d up}, ahk_id %idMain%
ControlSend,,{= down}{= up}, ahk_id %idClone%
ControlSend,,{d down}{d up}, ahk_id %idClone%
return
[/code:1]

Simplest way:
The disconnect only happens if the character that is followed is not moving. So:

1.) hit the /follow macro
2.) immediately move your main
3.) when you reach your destination hit a button that you assign "move back" to on all characters. Do that as soon as you stop moving with your main and the /follow breaks.

Yeah it sucks, but it's the easiest way and it works for my 5 box team.

Have fun,
Bunny

Are you sure you enabled vsync in-game as well as in the graphics card control panel?

It only happens to me, and don't ask me why... when I get my toons onto a boat. I swear to you, everything else is perfect but on a boat my carebear will disconnect 3 times at least.

Also only happens to me on a boat/zeppelin/lift. What I do is /follow onto the moving object, then immediately press my key to stop following. When I get to the destination, I set the toons to follow again. I have had zero problems doing it this way.

The script I use initiates follow on toons 2&3 on the downstroke of 'w' & on the upstroke sends a full 'w' keypress to 2&3. Therefore as soon as my main starts to move forward the others follow and when he stops follow is broken.

I remeber DAOC used to have similar issue. Before it has to do with the background not getting enough resources and ends up DCing.

When I started multiboxing wow I was disconnecting too. Mind you I have a quad core with 4 gigs of ram and such. What I do to fix my problem is I close as many background process as possible. I load in windows mode. Then I set the pority for my wows one setup higher. I make sure the none forground wows are minimized. That seems to work for me. I can have 3 wows running with no dc and /follow. Anything more and I'll get random dc in mins.

My WASD for movement keys doesnt really work, the clone just ends up 'sliding' at a really slow speed, not the same spedd at all as the main client.

Quote:

---

Originally Posted by MrLonghair

Are you sure you enabled vsync in-game as well as in the graphics card control panel?

---

Sadly yes, still get the disconnects.

Quote:

---

Originally Posted by Bunny

Simplest way:
The disconnect only happens if the character that is followed is not moving. So...

---

Excellent idea, thank you. I'll try this asap and tell you my experiances.

Quote:

---

Originally Posted by Minister

It only happens to me, and don't ask me why... when I get my toons onto a boat. I swear to you, everything else is perfect but on a boat my carebear will disconnect 3 times at least.

---

Quote:

---

Originally Posted by Picticon

Also only happens to me on a boat/zeppelin/lift. What I do is /follow onto the moving object, then immediately press my key to stop following. When I get to the destination, I set the toons to follow again. I have had zero problems doing it this way.

---

Lucky for you it only works on those 'transports' :) Picticon you seem to have the same solution as Bunny and Rhubarb. Thanks for letting me know!

Quote:

---

Originally Posted by Rhubarb

The script I use initiates follow on toons 2&3 on the downstroke of 'w' & on the upstroke sends a full 'w' keypress to 2&3. Therefore as soon as my main starts to move forward the others follow and when he stops follow is broken.

---

Excellent idea, essentialy the same as Bunny's but without the need to remember to press a further button. If I can get this to work in AHK I'll post how I did for anyone that has no clue how to use it.

Quote:

---

Originally Posted by Bervi

I remeber DAOC used to have similar issue. Before it has to do with the background not getting enough resources and ends up DCing.

When I started multiboxing wow I was disconnecting too. Mind you I have a quad core with 4 gigs of ram and such. What I do to fix my problem is I close as many background process as possible. I load in windows mode. Then I set the pority for my wows one setup higher. I make sure the none forground wows are minimized. That seems to work for me. I can have 3 wows running with no dc and /follow. Anything more and I'll get random dc in mins.

---

Yeah that's similar to what I have been doing. I've set all graphics to minimum's, windowed mode, minimizing the clone etc. I haven't tried changing the priority in Windows however.

All of that does have a noticeable effect, however the disconnects still happen at least once every 5 minutes as of now. I'll try making 'stop follow' keys for when I stop moving and let everyone know how I get on.

Quote:

---

Originally Posted by Rhubarb

The script I use initiates follow on toons 2&3 on the downstroke of 'w' & on the upstroke sends a full 'w' keypress to 2&3. Therefore as soon as my main starts to move forward the others follow and when he stops follow is broken.

---

Sorry to spam my thread but, Rhubarb could you please post your script? Or at least the 'W' part? I've tried to do the same thing and due to limited knowledge have had no luck.

Thanks in advance.

Must be something like:

[code:1]w::
ControlSend,, LetterForFollowMacro, ahk_id %wowid%
KeyWait w, D
ControlSend,, w, ahk_id %wowid%
return[/code:1]

Replace LetterForFollowMacro with the key you bound your follow macro.

so that's what that problem is.. one of my 5 accounts always disconnects every time I get on a zepp. just stop following and it won't happen?

The boat/zep/elevator thing happens to everyone on follow no matter what. Sometimes you're lucky and don't get hit by it.

Navigating stairs with clients on /follow is a bigger problem if you ask me. Try those narrow stairs or a test.

IDK

But it seems to be only happening to me on the "Newer" servers
I play fine on my other ones

I've never experienced this follow bug on zeppelins or elevators or anywhere else, and I do not normally break follow unless casting mind flay.

[edit] But if this only affects people who are running multiple instances of WoW on 1 PC, then that makes sense as I'm using a separate PC for each of my 4.

Here is the 'w' script for my dual box, just add more id clones for more. '-' is a macro set to follow my main.

[code:1]#IfWinActive, World of Warcraft
; *** Makes wow2 follow Wow1 Player ***
~w::
ControlSend,,{- down}{- up}, ahk_id %idClone%
return

#IfWinActive, World of Warcraft
; *** Makes wow2 stop following Wow1 Player ***
~w Up::
ControlSend,,{w down}{w up}, ahk_id %idClone%
return[/code:1]

My only concern is that the follow macro is spammed while the button is held down (when you are moving) although this has yet to actually be a problem.

Quote:

---

Originally Posted by Rhubarb

Here is the 'w' script for my dual box, just add more id clones for more. '-' is a macro set to follow my main...

---

My only problem with this is that there is always a gap between the two characters, most likely due to lag, whereby the clone stops following well before it is directly behind the main. Thanks for the script though, I have added it to my script however commented it out until I am able to test without as much lag.



For anyone that's interested, below is my entire script. It works for two clients and is basically Sorn's script with two /follow scripts added and a Suspend script added. Comments and suggestions welcome!

[code:1]
;
; Wow Duel Account Helper Version: .02a
; Language: English
; Platform: AutoHotkey Script
; Author: Sorn
; NOTES: Written for the Duel-Boxing.com forums, Send PM or post in the Autohotkey thread for assistance or suggestion
;
; Script Function:
; Allows you to play two copies of WOW at the same time
;
; Edited by Zaza 16/8/07 to include Suspend and Following, mainly for people with disconnects due to /follow.
; Edited without permission of Sorn, no attempt at plagiarism is intended. All other scripting work by Sorn.

; ************************************************** **************************************
; *** READ BEFORE USE! ***
; *** Uncomment ONE of the FOLLOW scripts to setup follow (line 82 to 90 OR 97 to 105) ***
; *** Bind 'Q' to follow macro on Clone ***
; *** Bind '=' to '/assist party1' on Clone ***
; *** Bind 'Ctrl+Q' to target self macros on both Main and Clone ***
; ************************************************** **************************************

;Tell user what is about to happen
SplashTextOn, 325, , Preparing to find your Main and Clone windows of WoW.
Sleep, 2000
SplasHtextoff

;Grab unique window ID's
WinGet, wowid, List, World of Warcraft

; Minimize All WOW windows
WinMinimize, ahk_id %wowid1%
WinMinimize, ahk_id %wowid2%

;Determine Main and Clone Windows
WinActivate, ahk_id %wowid1%

MsgBox, 4,, Is this your WOW Main window? (press Yes or No)
IfMsgBox Yes
idMain = %wowid1%
else
idMain = %wowid2%

If idMain = %wowid1%
{
idClone = %wowid2%
} else {
idClone = %wowid1%
}

;Activate All WOW windows
WinActivate, ahk_id %idMain%
WinActivate, ahk_id %idClone%


;*** Special Functions ***

#IfWinActive, World of Warcraft
; *** Makes wow2 follow Wow1 Player ***
^-::
ControlSend,,{- down}{- up}, ahk_id %idClone%
return

#IfWinActive, World of Warcraft
; *** Makes wow2 Assist Wow1 Player ***
^=::

return


; ************************************************** *******************
; *** Suspending (Pausing) the Script ***
; *** Used when you need to type etc without duplicating keypresses ***
; ************************************************** *******************
^E::Suspend ; Press Ctrl+E to Suspend this script, press it again to resume.


; ************************************************** ***
; *** FOLLOW TYPE 1 ***
; *** Bind 'Q' to follow macro on clone ***
; *** Bind 'E' to walk forwards on clone (unfollow) ***
; ************************************************** ***
;#IfWinActive, World of Warcraft
; ~Q::
; ControlSend,,{Q down}{Q up}, ahk_id %idClone%
;return
;
;#IfWinActive, World of Warcraft
; ~E::
; ControlSend,,{E down}{E up}, ahk_id %idClone%
;return


; ************************************************** **********
; *** FOLLOW TYPE 2 ***
; *** On W down Clone follows Main until W key is released ***
; ************************************************** **********
;#IfWinActive, World of Warcraft
; ~w::
; ControlSend,,{Q down}{Q up}, ahk_id %idClone% ; Replace Q with follow macro keybinding
;return
;
;#IfWinActive, World of Warcraft
; ~w Up::
; ControlSend,,{w down}{w up}, ahk_id %idClone% ; When W is released, clone takes a step ergo breaks follow
;return

; *******************
; *** Target Self ***
; *******************
#IfWinActive, World of Warcraft
~^Q::
ControlSend,,{Ctrl down}{Q down}{Q up}{Ctrl up}, ahk_id %idMain%
ControlSend,,{Ctrl down}{Q down}{Q up}{Ctrl up}, ahk_id %idClone%
return


; *******************
; *** Hotbars 1-0 ***
; *******************
#IfWinActive, World of Warcraft
~1::
ControlSend,,{1 down}{1 up}, ahk_id %idMain%
ControlSend,,{= down}{= up}, ahk_id %idClone%
ControlSend,,{1 down}{1 up}, ahk_id %idClone%
return

#IfWinActive, World of Warcraft
~2::
ControlSend,,{2 down}{2 up}, ahk_id %idMain%
ControlSend,,{= down}{= up}, ahk_id %idClone%
ControlSend,,{2 down}{2 up}, ahk_id %idClone%
return

#IfWinActive, World of Warcraft
~3::
ControlSend,,{3 down}{3 up}, ahk_id %idMain%
ControlSend,,{= down}{= up}, ahk_id %idClone%
ControlSend,,{3 down}{3 up}, ahk_id %idClone%
return

#IfWinActive, World of Warcraft
~4::
ControlSend,,{4 down}{4 up}, ahk_id %idMain%
ControlSend,,{= down}{= up}, ahk_id %idClone%
ControlSend,,{4 down}{4 up}, ahk_id %idClone%
return

#IfWinActive, World of Warcraft
~5::
ControlSend,,{5 down}{5 up}, ahk_id %idMain%
ControlSend,,{= down}{= up}, ahk_id %idClone%
ControlSend,,{5 down}{5 up}, ahk_id %idClone%
return

#IfWinActive, World of Warcraft
~6::
ControlSend,,{6 down}{6 up}, ahk_id %idMain%
ControlSend,,{= down}{= up}, ahk_id %idClone%
ControlSend,,{6 down}{6 up}, ahk_id %idClone%
return

#IfWinActive, World of Warcraft
~7::
ControlSend,,{7 down}{7 up}, ahk_id %idMain%
ControlSend,,{= down}{= up}, ahk_id %idClone%
ControlSend,,{7 down}{7 up}, ahk_id %idClone%
return

#IfWinActive, World of Warcraft
~8::
ControlSend,,{8 down}{8 up}, ahk_id %idMain%
ControlSend,,{= down}{= up}, ahk_id %idClone%
ControlSend,,{8 down}{8 up}, ahk_id %idClone%
return

#IfWinActive, World of Warcraft
~9::
ControlSend,,{9 down}{9 up}, ahk_id %idMain%
ControlSend,,{= down}{= up}, ahk_id %idClone%
ControlSend,,{9 down}{9 up}, ahk_id %idClone%
return

#IfWinActive, World of Warcraft
~0::
ControlSend,,{0 down}{0 up}, ahk_id %idMain%
ControlSend,,{= down}{= up}, ahk_id %idClone%
ControlSend,,{0 down}{0 up}, ahk_id %idClone%
return


; ***************************
; *** Hotbars Shift ^ 1-0 ***
; ***************************
#IfWinActive, World of Warcraft
~+1::
ControlSend,,{Shift down}{1 down}{1 up}{Shift up}, ahk_id %idMain%
ControlSend,,{= down}{= up}, ahk_id %idClone%
ControlSend,,{Shift down}{1 down}{1 up}{Shift up}, ahk_id %idClone%
return

#IfWinActive, World of Warcraft
~+2::
ControlSend,,{Shift down}{2 down}{2 up}{Shift up}, ahk_id %idMain%
ControlSend,,{= down}{= up}, ahk_id %idClone%
ControlSend,,{Shift down}{2 down}{2 up}{Shift up}, ahk_id %idClone%
return

#IfWinActive, World of Warcraft
~+3::
ControlSend,,{Shift down}{3 down}{3 up}{Shift up}, ahk_id %idMain%
ControlSend,,{= down}{= up}, ahk_id %idClone%
ControlSend,,{Shift down}{3 down}{3 up}{Shift up}, ahk_id %idClone%
return

#IfWinActive, World of Warcraft
~+4::
ControlSend,,{Shift down}{4 down}{4 up}{Shift up}, ahk_id %idMain%
ControlSend,,{= down}{= up}, ahk_id %idClone%
ControlSend,,{Shift down}{4 down}{4 up}{Shift up}, ahk_id %idClone%
return

#IfWinActive, World of Warcraft
~+5::
ControlSend,,{Shift down}{5 down}{5 up}{Shift up}, ahk_id %idMain%
ControlSend,,{= down}{= up}, ahk_id %idClone%
ControlSend,,{Shift down}{5 down}{5 up}{Shift up}, ahk_id %idClone%
return

#IfWinActive, World of Warcraft
~+6::
ControlSend,,{Shift down}{6 down}{6 up}{Shift up}, ahk_id %idMain%
ControlSend,,{= down}{= up}, ahk_id %idClone%
ControlSend,,{Shift down}{6 down}{6 up}{Shift up}, ahk_id %idClone%
return

#IfWinActive, World of Warcraft
~+7::
ControlSend,,{Shift down}{7 down}{7 up}{Shift up}, ahk_id %idMain%
ControlSend,,{= down}{= up}, ahk_id %idClone%
ControlSend,,{Shift down}{7 down}{7 up}{Shift up}, ahk_id %idClone%
return

#IfWinActive, World of Warcraft
~+8::
ControlSend,,{Shift down}{8 down}{8 up}{Shift up}, ahk_id %idMain%
ControlSend,,{= down}{= up}, ahk_id %idClone%
ControlSend,,{Shift down}{8 down}{8 up}{Shift up}, ahk_id %idClone%
return

#IfWinActive, World of Warcraft
~+9::
ControlSend,,{Shift down}{9 down}{9 up}{Shift up}, ahk_id %idMain%
ControlSend,,{= down}{= up}, ahk_id %idClone%
ControlSend,,{Shift down}{9 down}{9 up}{Shift up}, ahk_id %idClone%
return

#IfWinActive, World of Warcraft
~+0::
ControlSend,,{Shift down}{0 down}{0 up}{Shift up}, ahk_id %idMain%
ControlSend,,{= down}{= up}, ahk_id %idClone%
ControlSend,,{Shift down}{0 down}{0 up}{Shift up}, ahk_id %idClone%
return


; **************************
; *** Hotbars Cntl ^ 1-0 ***
; **************************
#IfWinActive, World of Warcraft
~^1::
ControlSend,,{Ctrl down}{1 down}{1 up}{Ctrl up}, ahk_id %idMain%
ControlSend,,{= down}{= up}, ahk_id %idClone%
ControlSend,,{Ctrl down}{1 down}{1 up}{Ctrl up}, ahk_id %idClone%
return

#IfWinActive, World of Warcraft
~^2::
ControlSend,,{Ctrl down}{2 down}{2 up}{Ctrl up}, ahk_id %idMain%
ControlSend,,{= down}{= up}, ahk_id %idClone%
ControlSend,,{Ctrl down}{2 down}{2 up}{Ctrl up}, ahk_id %idClone%
return

#IfWinActive, World of Warcraft
~^3::
ControlSend,,{Ctrl down}{3 down}{3 up}{Ctrl up}, ahk_id %idMain%
ControlSend,,{= down}{= up}, ahk_id %idClone%
ControlSend,,{Ctrl down}{3 down}{3 up}{Ctrl up}, ahk_id %idClone%
return

#IfWinActive, World of Warcraft
~^4::
ControlSend,,{Ctrl down}{4 down}{4 up}{Ctrl up}, ahk_id %idMain%
ControlSend,,{= down}{= up}, ahk_id %idClone%
ControlSend,,{Ctrl down}{4 down}{4 up}{Ctrl up}, ahk_id %idClone%
return

#IfWinActive, World of Warcraft
~^5::
ControlSend,,{Ctrl down}{5 down}{5 up}{Ctrl up}, ahk_id %idMain%
ControlSend,,{= down}{= up}, ahk_id %idClone%
ControlSend,,{Ctrl down}{5 down}{5 up}{Ctrl up}, ahk_id %idClone%
return

#IfWinActive, World of Warcraft
~^6::
ControlSend,,{Ctrl down}{6 down}{6 up}{Ctrl up}, ahk_id %idMain%
ControlSend,,{= down}{= up}, ahk_id %idClone%
ControlSend,,{Ctrl down}{6 down}{6 up}{Ctrl up}, ahk_id %idClone%
return

#IfWinActive, World of Warcraft
~^7::
ControlSend,,{Ctrl down}{7 down}{7 up}{Ctrl up}, ahk_id %idMain%
ControlSend,,{= down}{= up}, ahk_id %idClone%
ControlSend,,{Ctrl down}{7 down}{7 up}{Ctrl up}, ahk_id %idClone%
return

#IfWinActive, World of Warcraft
~^8::
ControlSend,,{Ctrl down}{8 down}{8 up}{Ctrl up}, ahk_id %idMain%
ControlSend,,{= down}{= up}, ahk_id %idClone%
ControlSend,,{Ctrl down}{8 down}{8 up}{Ctrl up}, ahk_id %idClone%
return

#IfWinActive, World of Warcraft
~^9::
ControlSend,,{Ctrl down}{9 down}{9 up}{Ctrl up}, ahk_id %idMain%
ControlSend,,{= down}{= up}, ahk_id %idClone%
ControlSend,,{Ctrl down}{9 down}{9 up}{Ctrl up}, ahk_id %idClone%
return

#IfWinActive, World of Warcraft
~^0::
ControlSend,,{Ctrl down}{0 down}{0 up}{Ctrl up}, ahk_id %idMain%
ControlSend,,{= down}{= up}, ahk_id %idClone%
ControlSend,,{Ctrl down}{0 down}{0 up}{Ctrl up}, ahk_id %idClone%
return


[/code:1]

I've been dual-boxing on one com today, and i had the disconnect problem when i was running wow maximised, so i could only see one at a time.

But when i downsized my windows a little and was able to see one window at about 80% of the screen, and the other window behind it at the same time, i didnt have a single disconnect.

Dunno if its a coincidence, but maybe worth a try for people with the problem.

As I said in my previous posts, unfortunatly even with the clone window minimized I still had the disconnects. Still, it pretty much works now so I'm happy enough. Hopefully Blizzard will release the proper fix for next patch, or sooner!

Just thought you should know, I've experienced it again yesterday. When i had both windows maximised and therefore could see only one of them at a time, I had a DC on my clone window, meaning the one i wasnt playing.

But when i resized them a bit, so I was able to see both my windows at the same time, i didnt have any DC's for a 3 hour session of playing.

It's almost like windows forgets about my second wow window, when i cant see it.

Windows: "If a wow window cant be seen then should it exist? I think NOT!"

Anyway, I cant be the only person where that is the solution, so I hope it helps someone else.

Quote:

---

Originally Posted by loonitoons

Just thought you should know, I've experienced it again yesterday. When i had both windows maximised and therefore could see only one of them at a time, I had a DC on my clone window, meaning the one i wasnt playing.

But when i resized them a bit, so I was able to see both my windows at the same time, i didnt have any DC's for a 3 hour session of playing.

It's almost like windows forgets about my second wow window, when i cant see it.

Windows: "If a wow window cant be seen then should it exist? I think NOT!"

Anyway, I cant be the only person where that is the solution, so I hope it helps someone else.

---

This fixed it for me thanks a ton :wink:

the bug seems to be fixed btw ;)

it seems so. /happy

I haven't seen this bug since the patch. Kept /follow on blimps/UC elevator/needles lifts/boats and haven't been d/c'ed at all since.

/cheer

modify your script to something like
[code:1]
; *******************
; *** WASD ***
; *******************
#IfWinActive, World of Warcraft

w::
ControlSend,,{w down}, ahk_id %idMain%
ControlSend,,{= down}, ahk_id %idClone%
ControlSend,,{w down}, ahk_id %idClone%
return

w up::
ControlSend,,{w up}, ahk_id %idMain%
ControlSend,,{= up}, ahk_id %idClone%
ControlSend,,{w up}, ahk_id %idClone%
return

a::
ControlSend,,{a down}, ahk_id %idMain%
ControlSend,,{= down}, ahk_id %idClone%
ControlSend,,{a down}, ahk_id %idClone%
return

a up::
ControlSend,,{a up}, ahk_id %idMain%
ControlSend,,{= up}, ahk_id %idClone%
ControlSend,,{a up}, ahk_id %idClone%
return

s::
ControlSend,,{s down}, ahk_id %idMain%
ControlSend,,{= down}, ahk_id %idClone%
ControlSend,,{s down}, ahk_id %idClone%
return

s up::
ControlSend,,{s up}, ahk_id %idMain%
ControlSend,,{= up}, ahk_id %idClone%
ControlSend,,{s up}, ahk_id %idClone%
return

d::
ControlSend,,{d down}, ahk_id %idMain%
ControlSend,,{= down}, ahk_id %idClone%
ControlSend,,{d down}, ahk_id %idClone%
return

d up::
ControlSend,,{d up}, ahk_id %idMain%
ControlSend,,{= up}, ahk_id %idClone%
ControlSend,,{d up}, ahk_id %idClone%
return [/code:1]

you don't want the ~ if you are explicitly sending the control to your main... ~ tells AHK to not block the key press to the current focus so you would end up with 2x w

btw what is the = being sent for? is this a straight copy of Sorn's script?

if so do you want a slightly improved version of the instance identification code? (not all my work)

@zaza

looks like a mod of Sorn's script ;) that is how I started too ;)

1. quick tip... #IfWinActive affects all subsequent lines of code in the script... you don't need it before every hotkey. I find getting rid of it all over the place makes the script much easier to read.

2. ~ is used to tell ahk not to block the keypress from the system... so if you have ~w:: which is also sending w to your main, then you will end up with 2x w... not too much impact while playing but a real pain when typing.

Indeed it is a mod of Sorn's script! :wink:

I would really like to see the improved version for sure, would be much appreciated.

As for the '=' it is sent because in Sorn's script you're told to bind '=' to a '/assist #main#' macro, which makes sure that thing's are always being cast on the correct targets.

Ah yes I remember now... the first thing I got rid of :)

I have ` (top left key) bound to assist on my clones... I just spam that and as I use pitbull I can see if they are targeted correctly or not.

Will try to post my script tonight... want to mod it slightly first though.