Hotkeynet stopped working

[Relic]

Hello everyone,

EDIT: didn't work again this morning so this wasn't the fix. Ignore my resolution. It was only temporary

*******RESOLVED********
I deleted both copies of HKN on both machines and then deleted the old script. I downloaded and installed HKN and then ran the generic sample script from the website. Changed the IP Address in the script and reload it. All my machines are running WOW again with no issues.
********RESOLVED********



I'm in need of some help. I have hotkeynet installed by using the sample script. I use this for dual-boxing in WOW. I had it working for a couple of years now and haven't had any issues. For some reason today it doesn't work.

I use 3 machines-3 accounts.
Hotkeynet works as I can see each machine talking to each other with no errors. However when i open WOW now on both machines it doesn't work even though when I alt tab out both machines are successfully chatting with no error within Hotkeynet I have made no changes to the script other than IP address's in the past. It was working fine this morning till i came back from running some choirs. Scroll Lock is my toggle by default.

I'm not sure where to look to troubleshoot here. I don't think this is a Hotkeynet issue. I don't think its a WOW issue. My Firewall allows full access to WOW and Hotkey and I run Hotkeynet on both machines running them as administrator. I have wiped my WTF folder in WOW (longshot).

Any Thoughts on where to look?

[Wubsie]

I hardly think it's a coincidence that we get 2 threads posted so close to each other with similar issues with scripts that were functioning fine previously.

It would appear that something in Windows has changed that makes Hotkeynet no longer function, or that is my best guess anyways. Using my 1PC script that was functioning perfectly before I can not get any keys sent to windows anymore either. This is not specific to WoW either, as the same issue is present when I try to send keys through HKN to Notepad. I've gone through all the SendWin modes and none of them appear to work anymore.

Not quite sure where to even start with this, so any input from HKN users (current or previous) would be appreciated. It might just be that some Windows update has broken the functionality needed and HKN has just come to the end of it's life...

[Rafipi]

I found the solution that was posted confusing. This is all I had to do to get HotkeyNet working:

1. Delete all the HotkeyNet files (don't need to touch the script)
2. Extract the files from the zip file to a new folder, NOT in Program Files
3. Right click hotkeynet.exe, click Properties, go to the Compatibility tab and check "Run this program as an administrator"

[Wubsie]

Huh... Interesting... I did try Right click --> Run as administrator, but that didn't seem to change anything. Perhaps I was using an incorrect SendWin mode at that time. Well, good that it's been resolved.

[Mamut]

Hi All

Long time HKN user, usually able to resolve any problems on my own but this one has me stumped.

When i launch my wow's they launch but a large grey box appears with no text and an "OK" button. The grey box is named "wow0", which is what the world of warcraft app was supposed to be renamed after launch.

It only started after i updated my wow today. The wow installs that i had forgot to update had launched normally but started doing the same behavior after i updated them.

If i remove from my script part of the Command LaunchAndRename "<RemoveWinFrame>" then the wows will launch but none of them are renamed and will receive no key broadcasts or resize and position correctly.

Windows did update 2 days ago, but i had no issues yesterday.

I have tried different admin settings, compatibility settings, used a fresh HKN install in a new directory, tried to launch wow manually then rename it with <RenameFromPath> (like you diablo users are familiar with). Nothing has worked.

Any insights would be greatly appreciated, I just started some new toons and was very excited to play some horde on bleeding hollow this coming weekend. I'm not sure i have it in me to redo all my scripts/settings in new software.

Thanks in advance
M

[Relic]

I found the solution that was posted confusing. This is all I had to do to get HotkeyNet working:

1. Delete all the HotkeyNet files (don't need to touch the script)
2. Extract the files from the zip file to a new folder, NOT in Program Files
3. Right click hotkeynet.exe, click Properties, go to the Compatibility tab and check "Run this program as an administrator"
My fix was only a temp fix. I got it working again last night and post resolved. Played a bit on WOW multi-boxing and then logged for off. This morning I fired up both machines and bam back to sqaure one. HKN is working again on both machines but not in the game. I tried un/reinstalling HKN and running it as an admin still nothing. reloaded my script, created another script. Nothing. This is frustrating as it shows nothing in the logs and I don't know where else to look to see what is causing this

[muldorante]

If you are multiboxing 4 wows, use a code for 5 wows...

I dont know why thix fixed for me, but now im boxing again :D

[rapstar]

I had a similar problem with 7.2. I believe it's the patcher. You might see some hidden files in your main wow directory (.build.info, .patch.result, .product.db). Copying those into each folder got me past the issue, but I'm on OSX so it might not be relevant.

Hmm... nevermind. I misread the topic. Doubt this is relevant.

[Armslave]

Hi there!

I got the same Problem... I tryed the same stuff noting works for me...

LG Arms

[r3tardbatman]

My money is on Blizzard having done something, I'd bet there was some kind of patch this morning in combination with the maintenance.
Using hotkeynet I can control both Half-Life 2 & The Stanley Parable, as well as enter text in chrome. With WoW however I can't do more than rename the windows. Thus it's not something that's changed in Windows that's broken it.
I'm running Windows 7 Ultimate, last update received March 16'th. Tried disabling my antivirus which did nothing and I'm about to fire up my other computer in safe mode to see what happens there.

EDIT: CKS does work however, unfortunately it's not exactly a substitute.

[Rafipi]

It was a temp fix for me as well I'm afraid. Worked once but can't get it to work again.

[fdelduque]

I first I tought was Wow related, but today I tried using on notepad to be sure and didn't work too. So probally the problem is with windows and HKN, I hope they fixed this cause I like HKN. I'm using autohotkey while HKN isnt working

[MiRai]

There's no reason to have multiple threads about the same topic, so they've been merged.

[Rathik]

I am still having issues, all I can do is rename the windows.
None of the other keys work in any wow windows.
I re downloaded hkn and use default script but nothing works still.

Anyone has any more tips on how to make this work again?

[Spacecowboy]

Came here to see if anyone else was having a similar issue and if there was a fix for it. I can open wow fine manually but when I use my script I get the same blank grey error box as everyone else. I did manage a work around for this problem but hope someone can come up with a better solution. Anyway, here is what I did:

Open each instance of wow manually
Then use HKN program menu to manually rename each instance. The rename option is under the Actions menu. Right click the title bar of the window you want to rename when the Rename option is open. Then type the windows new name.
Then I just use the hotkey I have set up that Configures the position of the windows.

Note: Depending on how your config file is set you may want to add a <RemoveWinFrame> to your ResizeAndPosition command.

Hope this helps and that we can come up with a better solution soon.

Here is the relevant code for reference:

//----------------------------------------------------------------
// Alternate Window CONFIG WITH HOTKEYS Alt Shift F1-F5
//----------------------------------------------------------------
<Hotkey ScrollLockOn Alt Shift F1>
<ResizeAndPosition 1 2 3 4 5>
<SetActiveWindowTracking On>
<SendWin WoW1>
<Key Oem6> // Key to send to focus win to tell slaves to follow.

<Hotkey ScrollLockOn Alt Shift F2>
<ResizeAndPosition 2 1 3 4 5>
<SetActiveWindowTracking On>
<SendWin WoW2>
<Key Oem6>

<Hotkey ScrollLockOn Alt Shift F3>
<ResizeAndPosition 3 1 2 4 5>
<SetActiveWindowTracking On>
<SendWin WoW3>
<Key Oem6>

<Hotkey ScrollLockOn Alt Shift F4>
<ResizeAndPosition 4 1 2 3 5>
<SetActiveWindowTracking On>
<SendWin WoW4>
<Key Oem6>

<Hotkey ScrollLockOn Alt Shift F5>
<ResizeAndPosition 5 1 2 3 4>
<SetActiveWindowTracking On>
<SendWin WoW5>
<Key Oem6>

//-----------------------------------------------------------
// SUBROUTINE TO Position Windows for 5 boxing.
//-----------------------------------------------------------
<Command ResizeAndPosition>
<SendWinM WoW%1%>
<RemoveWinFrame>
<SetWinRect 0 0 1920 1050>
<SendWinM WoW%2%>
<RemoveWinFrame>
<SetWinRect 1920 0 840 525>
<SendWinM WoW%3%>
<RemoveWinFrame>
<SetWinRect 2760 0 840 525>
<SendWinM WoW%4%>
<RemoveWinFrame>
<SetWinRect 1920 525 840 525>
<SendWinM WoW%5%>
<RemoveWinFrame>
<SetWinRect 2760 525 840 525>

[Glayde]

I thought I was going crazy the other day when it stopped working.
I run two wow's on two machines, and normally I send to "World of Warcraft" on the second machine so I don't need to bother renaming windows.

What seems to happen is that the actual "World of Warcraft" window isn't being recognized. If you put up another window with the "World of Warcraft" title, such as a website, your keystrokes will be sent there. However if the game window is the only titled window matching "World of Warcraft" the keypresses go into the void.

What I found to work was to manually rename my "World of Warcraft" default window to something else and direct the script on my master hotkey client to send to the new name, and not "World of Warcraft."

Hotkeynet simply can't recognize the default "World of Warcraft" window.

[Rafipi]

Yes the problem is to do with how the windows are renamed. I have some code in my script that renames my 2 World of Warcraft instances as WoW1 and WoW2. I have also made my own code to rename them back to World of Warcraft. Just keep playing with renaming the windows until you get it to work. If the windows don't seem to be renamed the first time you press the key, don't worry and try the game anyway. That might be what gets it to work.

[Mamut]

Manually renaming does work, thanks for the tip.

I cannot get any of the usual commands to rename them from a script. It makes me wonder if its some kind of change to hurt botters? Once renamed everything else works just fine.

[Wildflower]

Hello,
I was just going to post this too, I cannot get it to work anymore.
Yesterday I got it to work, but I dont really know why, today nothing works anymore.
Yesterday renaming manually worked, today not.

-------

Seems to be depending on luck? I just started it again, now it seems to work, but I did really nothing else than I did before, when it did not work. Puzzled.

[Armslave]

Wildflower you got an Ingame Invite from BlueShadow.
So kann man sich direkt austauschen^^

[fdelduque]

Looks like we don't have a permanet fix yet. I don't know if it is related, but since 7.2 when I launch wow from the battle net before the wow windows opens, there a small windows on top left corner that remains from some seconds than vanished and wow open. Maybe this new windows capture broadcast keys to prevent dualboxing. AHK still working

[muldorante]

Hello guys, im here again, with some investigation why HotKeyNet stopped working and some solution(kind of) I did a little test, i oppened 4 wows and instead of running my usual script for 4 wows, i loaded one script for 8 wows

http://imgur.com/mjB3rnp

And when i press my key to rename the wows something strange happens, look:

http://imgur.com/pavOtEj

My HKN says Completed: Windows found for 8 wows, but i only oppened 4 wows.. what is happening? I'm suspecting that this has to do with the World of Warcraft performing initial setup window that appear before wow is launched.

http://imgur.com/UE6TCWH

Somehow this window its not closed but hidden when the game is launched, and its causing the renaming/commands to not work using HKN

Using the HKN > Actions > Identify window handle, i searched the hex code to see what class they're using:

http://imgur.com/Oprqysu

As you can see in the image above, the class input text appear #32770 for the WoW1 hex code...
When we search this class on the internet, we can found this:

http://imgur.com/xqKJSJ5
Font: https://msdn.microsoft.com/en-us/library/windows/desktop/ms633574(v=vs.85).aspx

"The class for a dialog box", so the HKN is renaming World of Warcraft initial setup window like was the game client...

So i did another test, again with HKN > Identify window handle, i searched the hex code for the WoW5 to see what class they're using:

http://imgur.com/9D83nmo

And here its the normal class GxWindowsClass for a wow game.
Wich its the one who will received the commands from KNH for the multiboxing.

Conclusion
The World of Warcraft initial setup its causing the problem, after the setup this windows is hidden and not closed

Solution:
For each client of wow you're oppening for multibox, add 2 rename line, like a i did in the first image
And I apologize for my english and my simplified post, but i hope i could clarify or help someone.

[Mamut]

Muldorante, Thank you for sharing what you found. No need to apologize, your English is excellent.

I modified my script using your findings and can now launch and rename properly.

The first command to rename seems to always hit the "initial setup" window, so i can still target specific installs for renaming if i keep that in mind.

Thanks again

M

[xerxos0815]

could you please post your script? I have tried myself with the images, but still the same problem

[Rafipi]

My solution that works every time is:

Define a key that renames your windows back to their original name.

Press the key to rename your windows twice. Then press the key to rename back to their original name once.

Here is the code I use for 2 WoWs:


<Hotkey ScrollLockOn Ctrl R>
<SendPC local>
<RenameWin "World of Warcraft" WoW1>
<RenameWin "World of Warcraft" WoW2>


<Hotkey ScrollLockOn Ctrl T>
<SendPC local>
<RenameWin WoW1 "World of Warcraft">
<RenameWin WoW2 "World of Warcraft">

[xerxos0815]

My solution that works every time is:

Define a key that renames your windows back to their original name.

Press the key to rename your windows twice. Then press the key to rename back to their original name once.

Here is the code I use for 2 WoWs:


<Hotkey ScrollLockOn Ctrl R>
<SendPC local>
<RenameWin "World of Warcraft" WoW1>
<RenameWin "World of Warcraft" WoW2>


<Hotkey ScrollLockOn Ctrl T>
<SendPC local>
<RenameWin WoW1 "World of Warcraft">
<RenameWin WoW2 "World of Warcraft">


Yes, this works, thanx a lot!!

[fdelduque]

Hello guys, im here again, with some investigation why HotKeyNet stopped working and some solution(kind of) I did a little test, i oppened 4 wows and instead of running my usual script for 4 wows, i loaded one script for 8 wows

http://imgur.com/mjB3rnp

And when i press my key to rename the wows something strange happens, look:

http://imgur.com/pavOtEj

My HKN says Completed: Windows found for 8 wows, but i only oppened 4 wows.. what is happening? I'm suspecting that this has to do with the World of Warcraft performing initial setup window that appear before wow is launched.

http://imgur.com/UE6TCWH

Somehow this window its not closed but hidden when the game is launched, and its causing the renaming/commands to not work using HKN

Using the HKN > Actions > Identify window handle, i searched the hex code to see what class they're using:

http://imgur.com/Oprqysu

As you can see in the image above, the class input text appear #32770 for the WoW1 hex code...
When we search this class on the internet, we can found this:

http://imgur.com/xqKJSJ5
Font: https://msdn.microsoft.com/en-us/library/windows/desktop/ms633574(v=vs.85).aspx

"The class for a dialog box", so the HKN is renaming World of Warcraft initial setup window like was the game client...

So i did another test, again with HKN > Identify window handle, i searched the hex code for the WoW5 to see what class they're using:

http://imgur.com/9D83nmo

And here its the normal class GxWindowsClass for a wow game.
Wich its the one who will received the commands from KNH for the multiboxing.

Conclusion
The World of Warcraft initial setup its causing the problem, after the setup this windows is hidden and not closed

Solution:
For each client of wow you're oppening for multibox, add 2 rename line, like a i did in the first image
And I apologize for my english and my simplified post, but i hope i could clarify or help someone.

WOW! That was very clever of you, nice finding. Now I'm really curious, if this was something blizzard did against dual boxers or was for something else and messing with HKN was a coincidence. I do hope they did not do a BAN against dual boxers, all they do is change the EULA and TOS(Yeah, we all read this) and BAN. I dream when blizzard become nicer and maybe give a 6 mounth warning so the info is well spread instead of just change terms.
Thanks for sharing this solution. Regards

[Lax]

Now I'm really curious, if this was something blizzard did against dual boxers or was for something else and messing with HKN was a coincidence. I do hope they did not do a BAN against dual boxers, all they do is change the EULA and TOS(Yeah, we all read this) and BAN.
Ummm... no. They have publicly defended multiboxers and multiboxing in general.

Chances are they changed something trivial, and it just happened to affect the way you guys use HotkeyNet. Do note that it's just HKN users having trouble -- not any other software. If they wanted to take action against multiboxers, this would be one of the last -- and least effective -- changes they would consider :)

[Armslave]

Hi i need some Help... I got a diverent way to Rename the WIndows and so on. I tryed to integrate the fix but i got not enough knowlege...
I am using 5 Toons on 2 screens. Could you please help me?


// Scrolllock is the toggle for hotkeys
//-----------------------------------------------------------
// SUBROUTINE TO LAUNCH AND RENAME A COPY OF WOW.
//-----------------------------------------------------------
<Command LaunchAndRename>
<SendPC %1%>
<Run "C:\Program Files (x86)\World of Warcraft\Wow-64.exe">
<RenameTargetWin %2%>

//-----------------------------------------------------------
// Initial window positions
//-----------------------------------------------------------
<Command SetF1Pos>
<TargetWin WoW1>
<SetWinPos 0 0>
<SetWinSize 1920 1080>
<SetForegroundWin>
<UpdateWin>
<TargetWin WoW2>
<SetWinPos -1920 0>
<SetWinSize 960 540>
<TargetWin WoW3>
<SetWinPos -960 0>
<SetWinSize 960 540>
<TargetWin WoW4>
<SetWinPos -1920 540>
<SetWinSize 960 540>
<TargetWin WoW5>
<SetWinPos -960 540>
<SetWinSize 960 540>


//-----------------------------------------------------------
// Shift-alt-L launches all 5 instances and logs in
//-----------------------------------------------------------
<Hotkey Alt Ctrl L>
<LaunchAndRename Local WoW1>
<RemoveWinFrame>
<sendpc local>
<SendWin "WoW1">
<wait 1000>
<text email>
<Key Tab>
<wait 100>
<text Password>
<wait 300>
<Key Enter>
<wait 3000>
<Key Down>
<Key Down>
<Key Down>
<Key Down>
<Key Enter>

<LaunchAndRename Local WoW2>
<RemoveWinFrame>
<sendpc local>
<SendWin "WoW2">
<wait 1000>
<text email>
<Key Tab>
<wait 100>
<text Password>
<wait 300>
<Key Enter>
<wait 3000>
<Key Down>
<Key Down>
<Key Down>
<Key Enter>

<LaunchAndRename Local WoW3>
<RemoveWinFrame>
<sendpc local>
<SendWin "WoW3">
<wait 1000>
<text email>
<Key Tab>
<wait 100>
<text Password>
<wait 300>
<Key Enter>
<wait 3000>
<Key Down>
<Key Down>
<Key Enter>

<LaunchAndRename Local WoW4>
<RemoveWinFrame>
<sendpc local>
<SendWin "WoW4">
<wait 1000>
<text email>
<Key Tab>
<wait 100>
<text Password>
<Key Enter>
<wait 3000>
<Key Down>
<Key Enter>

<LaunchAndRename Local WoW5>
<RemoveWinFrame>
<sendpc local>
<SendWin "WoW5">
<wait 1000>
<text email>
<Key Tab>
<wait 100>
<text Password>
<Key Enter>
<wait 3000>
<Key Enter>


//-----------------------------------------------------------
// DEFINE MAIL LABELS FOR SENDING KEY STROKES.
//-----------------------------------------------------------
<Label w1 Local SendWinM WoW1>
<Label w2 Local SendWinM WoW2>
<Label w3 Local SendWinM WoW3>
<Label w4 Local SendWinM WoW4>
<Label w5 Local SendWinM WoW5>


//-----------------------------------------------------------
// DEFINE HOTKEYS FOR ALL KEY COMBINATIONS THAT WILL GET
// SENT TO ALL WOWS. ADD MORE KEY COMBO'S IF YOU WANT.
//-----------------------------------------------------------
<KeyList MyList A-Z, 0-9, Plus, Minus, Period, Oem7, Oem4, Oem6, Oem3, Tab, Comma, Oem1, F1-F12, Backspace, Ctrl, Enter, Esc, Divide, Capslock, Oem2, Numpad0-Numpad9, except W, A, S, D, Q, E>
<Hotkey ScrollLockOn MyList; ScrollLockOn Shift MyList, except F1-F12>
<SendLabel w1, w2, w3, w4, w5>
<Key %Trigger%>

//-----------------------------------------------------------
// DEFINE MOVEMENT KEYS THAT WILL GET SENT TO BOTH WOW'S.
// ADD MORE KEYS IF YOU WANT.
//-----------------------------------------------------------
<MovementHotkey ScrollLockOn W, S, A, D, Q, E, Up, Down, Left, Right, Space>
<SendLabel w1, w2, w3, w4, w5>
<Key %Trigger%>

//-----------------------------------------------------------
// BROADCAST MOUSE CLICKS. HOLD DOWN OEM5 (ON U.S. KEYBOARDS,
// THAT'S THE SQUIGGLE KEY IN UPPPER LEFT CORNER) WHEN YOU
// WANT TO BROADCAST.
//-----------------------------------------------------------
<UseKeyAsModifier Oem5>
<Hotkey ScrollLockOn Oem5 LButton, MButton, RButton, Button4, Button5>
<SendLabel w1, w2, w3, w4, w5>
<ClickMouse %TriggerMainKey%>


//------------------------------------------------------------------------
//Window Shifting
//------------------------------------------------------------------------



<Hotkey ScrollLockOn Shift F1>
<If ActiveWinIs WoW1>
<Else>
<SetF1Pos>
<Hotkey ScrollLockOn Shift F2>
<If ActiveWinIs WoW2>
<Else>
<TargetWin WoW1>
<SetWinPos -1920 0>
<SetWinSize 960 540>
<TargetWin WoW3>
<SetWinPos -960 0>
<SetWinSize 960 540>
<TargetWin WoW4>
<SetWinPos -1920 540>
<SetWinSize 960 540>
<TargetWin WoW5>
<SetWinPos -960 540>
<SetWinSize 960 540>
<TargetWin WoW2>
<SetWinPos 0 0>
<SetWinSize 1920 1080>
<SetForegroundWin>
<UpdateWin>
<Hotkey ScrollLockOn Shift F3>
<If ActiveWinIs WoW3>
<Else>
<TargetWin WoW1>
<SetWinPos -960 540>
<SetWinSize 960 540>
<TargetWin WoW2>
<SetWinPos -1920 0>
<SetWinSize 960 540>
<TargetWin WoW4>
<SetWinPos -960 0>
<SetWinSize 960 540>
<TargetWin WoW5>
<SetWinPos -1920 540>
<SetWinSize 960 540>
<TargetWin WoW3>
<SetWinPos 0 0>
<SetWinSize 1920 1080>
<SetForegroundWin>
<UpdateWin>
<Hotkey ScrollLockOn Shift F4>
<If ActiveWinIs WoW4>
<Else>
<TargetWin WoW1>
<SetWinPos -1920 540>
<SetWinSize 960 540>
<TargetWin WoW2>
<SetWinPos -960 540>
<SetWinSize 960 540>
<TargetWin WoW3>
<SetWinPos -1920 0>
<SetWinSize 960 540>
<TargetWin WoW5>
<SetWinPos -960 0>
<SetWinSize 960 540>
<TargetWin WoW4>
<SetWinPos 0 0>
<SetWinSize 1920 1080>
<SetForegroundWin>
<UpdateWin>
<Hotkey ScrollLockOn Shift F5>
<If ActiveWinIs WoW5>
<Else>
<TargetWin WoW1>
<SetWinPos -960 0>
<SetWinSize 960 540>
<TargetWin WoW2>
<SetWinPos -1920 540>
<SetWinSize 960 540>
<TargetWin WoW3>
<SetWinPos -960 540>
<SetWinSize 960 540>
<TargetWin WoW4>
<SetWinPos -1920 0>
<SetWinSize 960 540>
<TargetWin WoW5>
<SetWinPos 0 0>
<SetWinSize 1920 1080>
<SetForegroundWin>
<UpdateWin>

[fdelduque]

I'm no HKN experT buT looks like you launch and rename aT The same Time, Try using a key To rename all wows one more Time afTer lauch.
PS: T is capiTal cause is my roundrobin for inTerrupT, The only way TO Type while i play is using capiTal, even wih scrolllock off

[zenga]

Ummm... no. They have publicly defended multiboxers and multiboxing in general.

Chances are they changed something trivial, and it just happened to affect the way you guys use HotkeyNet. Do note that it's just HKN users having trouble -- not any other software. If they wanted to take action against multiboxers, this would be one of the last -- and least effective -- changes they would consider :)

The vultures are in :D
http://www.animatedimages.org/data/media/504/animated-vulture-image-0009.gif

[Mamut]

Armslave i made only changes to the launchand rename command, give it a try. It fired up on my machine.



// Scrolllock is the toggle for hotkeys
//-----------------------------------------------------------
// SUBROUTINE TO LAUNCH AND RENAME A COPY OF WOW.
//-----------------------------------------------------------
<Command LaunchAndRename>
<SendPC %1%>
<Run "C:\Program Files (x86)\World of Warcraft\Wow-64.exe">
<wait 1500>
<RenameWin "World of Warcraft" PreDummyBox>
<RenameWin "World of Warcraft" %2%>




//-----------------------------------------------------------
// Initial window positions
//-----------------------------------------------------------
<Command SetF1Pos>
<TargetWin WoW1>
<SetWinPos 0 0>
<SetWinSize 1920 1080>
<SetForegroundWin>
<UpdateWin>
<TargetWin WoW2>
<SetWinPos -1920 0>
<SetWinSize 960 540>
<TargetWin WoW3>
<SetWinPos -960 0>
<SetWinSize 960 540>
<TargetWin WoW4>
<SetWinPos -1920 540>
<SetWinSize 960 540>
<TargetWin WoW5>
<SetWinPos -960 540>
<SetWinSize 960 540>




//-----------------------------------------------------------
// Shift-alt-L launches all 5 instances and logs in
//-----------------------------------------------------------
<Hotkey Alt Ctrl L>
<LaunchAndRename Local WoW1>
<RemoveWinFrame>
<sendpc local>
<SendWin "WoW1">
<wait 1000>
<text email>
<Key Tab>
<wait 100>
<text Password>
<wait 300>
<Key Enter>
<wait 3000>
<Key Down>
<Key Down>
<Key Down>
<Key Down>
<Key Enter>

<LaunchAndRename Local WoW2>
<RemoveWinFrame>
<sendpc local>
<SendWin "WoW2">
<wait 1000>
<text email>
<Key Tab>
<wait 100>
<text Password>
<wait 300>
<Key Enter>
<wait 3000>
<Key Down>
<Key Down>
<Key Down>
<Key Enter>


<LaunchAndRename Local WoW3>
<RemoveWinFrame>
<sendpc local>
<SendWin "WoW3">
<wait 1000>
<text email>
<Key Tab>
<wait 100>
<text Password>
<wait 300>
<Key Enter>
<wait 3000>
<Key Down>
<Key Down>
<Key Enter>


<LaunchAndRename Local WoW4>
<RemoveWinFrame>
<sendpc local>
<SendWin "WoW4">
<wait 1000>
<text email>
<Key Tab>
<wait 100>
<text Password>
<Key Enter>
<wait 3000>
<Key Down>
<Key Enter>


<LaunchAndRename Local WoW5>
<RemoveWinFrame>
<sendpc local>
<SendWin "WoW5">
<wait 1000>
<text email>
<Key Tab>
<wait 100>
<text Password>
<Key Enter>
<wait 3000>
<Key Enter>




//-----------------------------------------------------------
// DEFINE MAIL LABELS FOR SENDING KEY STROKES.
//-----------------------------------------------------------
<Label w1 Local SendWinM WoW1>
<Label w2 Local SendWinM WoW2>
<Label w3 Local SendWinM WoW3>
<Label w4 Local SendWinM WoW4>
<Label w5 Local SendWinM WoW5>




//-----------------------------------------------------------
// DEFINE HOTKEYS FOR ALL KEY COMBINATIONS THAT WILL GET
// SENT TO ALL WOWS. ADD MORE KEY COMBO'S IF YOU WANT.
//-----------------------------------------------------------
<KeyList MyList A-Z, 0-9, Plus, Minus, Period, Oem7, Oem4, Oem6, Oem3, Tab, Comma, Oem1, F1-F12, Backspace, Ctrl, Enter, Esc, Divide, Capslock, Oem2, Numpad0-Numpad9, except W, A, S, D, Q, E>
<Hotkey ScrollLockOn MyList; ScrollLockOn Shift MyList, except F1-F12>
<SendLabel w1, w2, w3, w4, w5>
<Key %Trigger%>

//-----------------------------------------------------------
// DEFINE MOVEMENT KEYS THAT WILL GET SENT TO BOTH WOW'S.
// ADD MORE KEYS IF YOU WANT.
//-----------------------------------------------------------
<MovementHotkey ScrollLockOn W, S, A, D, Q, E, Up, Down, Left, Right, Space>
<SendLabel w1, w2, w3, w4, w5>
<Key %Trigger%>

//-----------------------------------------------------------
// BROADCAST MOUSE CLICKS. HOLD DOWN OEM5 (ON U.S. KEYBOARDS,
// THAT'S THE SQUIGGLE KEY IN UPPPER LEFT CORNER) WHEN YOU
// WANT TO BROADCAST.
//-----------------------------------------------------------
<UseKeyAsModifier Oem5>
<Hotkey ScrollLockOn Oem5 LButton, MButton, RButton, Button4, Button5>
<SendLabel w1, w2, w3, w4, w5>
<ClickMouse %TriggerMainKey%>




//------------------------------------------------------------------------
//Window Shifting
//------------------------------------------------------------------------






<Hotkey ScrollLockOn Shift F1>
<If ActiveWinIs WoW1>
<Else>
<SetF1Pos>
<Hotkey ScrollLockOn Shift F2>
<If ActiveWinIs WoW2>
<Else>
<TargetWin WoW1>
<SetWinPos -1920 0>
<SetWinSize 960 540>
<TargetWin WoW3>
<SetWinPos -960 0>
<SetWinSize 960 540>
<TargetWin WoW4>
<SetWinPos -1920 540>
<SetWinSize 960 540>
<TargetWin WoW5>
<SetWinPos -960 540>
<SetWinSize 960 540>
<TargetWin WoW2>
<SetWinPos 0 0>
<SetWinSize 1920 1080>
<SetForegroundWin>
<UpdateWin>
<Hotkey ScrollLockOn Shift F3>
<If ActiveWinIs WoW3>
<Else>
<TargetWin WoW1>
<SetWinPos -960 540>
<SetWinSize 960 540>
<TargetWin WoW2>
<SetWinPos -1920 0>
<SetWinSize 960 540>
<TargetWin WoW4>
<SetWinPos -960 0>
<SetWinSize 960 540>
<TargetWin WoW5>
<SetWinPos -1920 540>
<SetWinSize 960 540>
<TargetWin WoW3>
<SetWinPos 0 0>
<SetWinSize 1920 1080>
<SetForegroundWin>
<UpdateWin>
<Hotkey ScrollLockOn Shift F4>
<If ActiveWinIs WoW4>
<Else>
<TargetWin WoW1>
<SetWinPos -1920 540>
<SetWinSize 960 540>
<TargetWin WoW2>
<SetWinPos -960 540>
<SetWinSize 960 540>
<TargetWin WoW3>
<SetWinPos -1920 0>
<SetWinSize 960 540>
<TargetWin WoW5>
<SetWinPos -960 0>
<SetWinSize 960 540>
<TargetWin WoW4>
<SetWinPos 0 0>
<SetWinSize 1920 1080>
<SetForegroundWin>
<UpdateWin>
<Hotkey ScrollLockOn Shift F5>
<If ActiveWinIs WoW5>
<Else>
<TargetWin WoW1>
<SetWinPos -960 0>
<SetWinSize 960 540>
<TargetWin WoW2>
<SetWinPos -1920 540>
<SetWinSize 960 540>
<TargetWin WoW3>
<SetWinPos -960 540>
<SetWinSize 960 540>
<TargetWin WoW4>
<SetWinPos -1920 0>
<SetWinSize 960 540>
<TargetWin WoW5>
<SetWinPos 0 0>
<SetWinSize 1920 1080>
<SetForegroundWin>
<UpdateWin>

[fdelduque]

My solution that works every time is:

Define a key that renames your windows back to their original name.

Press the key to rename your windows twice. Then press the key to rename back to their original name once.

Here is the code I use for 2 WoWs:


<Hotkey ScrollLockOn Ctrl R>
<SendPC local>
<RenameWin "World of Warcraft" WoW1>
<RenameWin "World of Warcraft" WoW2>


<Hotkey ScrollLockOn Ctrl T>
<SendPC local>
<RenameWin WoW1 "World of Warcraft">
<RenameWin WoW2 "World of Warcraft">


Nice fix. Most of the times works, only failed once here with 2 wows too. But doing this makes wow really slow to shut down. Dunno why.

[TheDesertWind]

Hello guys, im here again, with some investigation why HotKeyNet stopped working and some solution(kind of) I did a little test, i oppened 4 wows and instead of running my usual script for 4 wows, i loaded one script for 8 wows

http://imgur.com/mjB3rnp

And when i press my key to rename the wows something strange happens, look:

http://imgur.com/pavOtEj

My HKN says Completed: Windows found for 8 wows, but i only oppened 4 wows.. what is happening? I'm suspecting that this has to do with the World of Warcraft performing initial setup window that appear before wow is launched.

http://imgur.com/UE6TCWH

Somehow this window its not closed but hidden when the game is launched, and its causing the renaming/commands to not work using HKN

Using the HKN > Actions > Identify window handle, i searched the hex code to see what class they're using:

http://imgur.com/Oprqysu

As you can see in the image above, the class input text appear #32770 for the WoW1 hex code...
When we search this class on the internet, we can found this:

http://imgur.com/xqKJSJ5
Font: https://msdn.microsoft.com/en-us/library/windows/desktop/ms633574(v=vs.85).aspx

"The class for a dialog box", so the HKN is renaming World of Warcraft initial setup window like was the game client...

So i did another test, again with HKN > Identify window handle, i searched the hex code for the WoW5 to see what class they're using:

http://imgur.com/9D83nmo

And here its the normal class GxWindowsClass for a wow game.
Wich its the one who will received the commands from KNH for the multiboxing.

Conclusion
The World of Warcraft initial setup its causing the problem, after the setup this windows is hidden and not closed

Solution:
For each client of wow you're oppening for multibox, add 2 rename line, like a i did in the first image
And I apologize for my english and my simplified post, but i hope i could clarify or help someone.

Nice work, Muldorante!

Indeed, upon listing all windows I found two for each visible WoW window with a title of "World of Warcraft". One with window class "GxWindowClass" and the other with window class "#32770" (documented by Microsoft as a system dialog box window class).

So I put in a ticket asking that a request be forwarded to the development team to rename the title of the extra window. Not sure what'll come of it; quite possibly nothing. But it seemed worthwhile to ask.

TDW

[fdelduque]

Nice work, Muldorante!

Indeed, upon listing all windows I found two for each visible WoW window with a title of "World of Warcraft". One with window class "GxWindowClass" and the other with window class "#32770" (documented by Microsoft as a system dialog box window class).

So I put in a ticket asking that a request be forwarded to the development team to rename the title of the extra window. Not sure what'll come of it; quite possibly nothing. But it seemed worthwhile to ask.

TDW

Nice. I hope They rename This windows To some dummy name. Keep us updaTed.

[samljer]

its not a script issue, i can tell you exactly whats happening..

if you manually name each window, it works 100% fine
theres a hidden window somewhere.
its also not a dummy window, or it would be in the process list.
i tested this with C++

further more, you dont see 2 windows of the game in the system processes.
for some reason, wow is creating a hidden window to throw off HKN
but if you look in the HKN log window, it will show "found #"
where # is total number of games running +1.

Launch a SINGLE copy of the game. and then do the auto rename.
it finds two.

close your game, it finds none.

launch again (1 copy of the game)
it finds two

launch 5, it finds 6, and so on.

thats why it sometimes works and sometimes does not.

but if you manually rename each window, you can still use HKN.
thats fine i guess if you play, 2, 3, or maybe 5 at once... as thats what i do
but if you had to rename 15. id probably stop.

edit: i want to point out youll have this issue if you manually launch each game and auto-name
or if you let HKN launch-rename, its going to happen. just manually name each window.

edit 2: oh yea 1 more thing, this issue occured on all 3 of my computers, and each one has a different OS
windows10, windows8 and windows7.

[Rafipi]

This code renames the windows using one keypress and works fine for me. Haven't tested the 5 WoW version as I only have 2 accounts but it should work.

2 WoWs:


<Hotkey ScrollLockOn Ctrl R>
<SendPC local>
<RenameWin "World of Warcraft" HiddenDialog>
<RenameWin "World of Warcraft" HiddenDialog>
<RenameWin "World of Warcraft" WoW1>
<RenameWin "World of Warcraft" WoW2>

5 WoWs:


<Hotkey ScrollLockOn Ctrl R>
<SendPC local>
<RenameWin "World of Warcraft" HiddenDialog>
<RenameWin "World of Warcraft" HiddenDialog>
<RenameWin "World of Warcraft" HiddenDialog>
<RenameWin "World of Warcraft" HiddenDialog>
<RenameWin "World of Warcraft" HiddenDialog>

<RenameWin "World of Warcraft" WoW1>
<RenameWin "World of Warcraft" WoW2>
<RenameWin "World of Warcraft" WoW3>
<RenameWin "World of Warcraft" WoW4>
<RenameWin "World of Warcraft" WoW5>


It may be beneficial to split it into separate keypresses as well in case you need to open a new WoW after a crash or something.

[fdelduque]

This code renames the windows using one keypress and works fine for me. Haven't tested the 5 WoW version as I only have 2 accounts but it should work.

2 WoWs:


<Hotkey ScrollLockOn Ctrl R>
<SendPC local>
<RenameWin "World of Warcraft" HiddenDialog>
<RenameWin "World of Warcraft" HiddenDialog>
<RenameWin "World of Warcraft" WoW1>
<RenameWin "World of Warcraft" WoW2>

5 WoWs:


<Hotkey ScrollLockOn Ctrl R>
<SendPC local>
<RenameWin "World of Warcraft" HiddenDialog>
<RenameWin "World of Warcraft" HiddenDialog>
<RenameWin "World of Warcraft" HiddenDialog>
<RenameWin "World of Warcraft" HiddenDialog>
<RenameWin "World of Warcraft" HiddenDialog>

<RenameWin "World of Warcraft" WoW1>
<RenameWin "World of Warcraft" WoW2>
<RenameWin "World of Warcraft" WoW3>
<RenameWin "World of Warcraft" WoW4>
<RenameWin "World of Warcraft" WoW5>


It may be beneficial to split it into separate keypresses as well in case you need to open a new WoW after a crash or something.
I'm using AHK for rename, AHK can rename by he windows chosen.


~1::
IfWinActive, World of Warcraft
{
if not GetKeyState("Scrolllock", "T")
Return
WinSetTitle, WoW1
Return
}

[Spacecowboy]

I managed to get my HKN script setup again that will Launch and setup all my wow's again with a single key press. Below is the relevant code for reference.

I added in the Rename for the Hidden Dialog box and I added in 2 Renames for "World of Warcraft". Not sure why I had to add it twice but I noticed that when I tried without it would launch and rename an instance to WoW# then rename back to World of Warcraft. I had to add the 3rd Rename to make sure the instance had the correct label. Hope this helps.



<Template LaunchAndRename>
<If WinDoesNotExist WoW%1%>
<Run %2%>

<RenameWin "World of Warcraft" HiddenDialog>
<wait 1000>
<RenameWin "World of Warcraft" WoW%1%>
<wait 1000>
<RenameWin "World of Warcraft" WoW%1%>

<RemoveWinFrame>
<SetAffinity %4%>

<SendWin WoW%1%>
<wait 1000>
<Text %3%>
<Key Enter>

<ResizeAndPosition 1 2 3 4 5>

<EndIf>
<EndTemplate>

<Command ResizeAndPosition>
<SendWinM WoW%1%>
<SetWinRect 0 0 1920 1050>
<SendWinM WoW%2%>
<SetWinRect 1920 0 840 525>
<SendWinM WoW%3%>
<SetWinRect 2760 0 840 525>
<SendWinM WoW%4%>
<SetWinRect 1920 525 840 525>
<SendWinM WoW%5%>
<SetWinRect 2760 525 840 525>

<Hotkey ScrollLockOn Alt Ctrl L>
<ApplyTemplate LaunchAndRename 1 D:\Games\WorldofWarcraft\Wow-64.exe password 0>
<ApplyTemplate LaunchAndRename 2 D:\Games\WorldofWarcraft2\Wow-64.exe password 1>
<ApplyTemplate LaunchAndRename 3 D:\Games\WorldofWarcraft3\Wow-64.exe password 2>
<ApplyTemplate LaunchAndRename 4 D:\Games\WorldofWarcraft4\Wow-64.exe password 3>
<ApplyTemplate LaunchAndRename 5 D:\Games\WorldofWarcraft5\Wow-64.exe password 3>

[Rathik]

...

[jeffleigh]

Solved the problem of Hotkeynet not working
I two box characters in wow, with a heals class in lead and pet class on follow- been doing it since cata with hotkeynet and its been great
I use two PCs running windows 10 and had a problem with Hotkeynet not working when Legion came out
I found I had to have the WOW windows on Fullscreen NOT (Windowed fullscreen) - no problems then
WOW reset the windows to Windowed fullscreen after patch 7.3 and then hotkeynet did not work again - so I had to set the windows back to Fullscreen

[muldorante]

old


//----------------------------------------------------------------
// PRESS CTRL R TO RENAME WOW'S
//----------------------------------------------------------------

<Hotkey ScrollLockOn Ctrl R>
<If WinSizeIs "World of Warcraft" 470 265>
<RenameWin "World of Warcraft" HiddenDialogBox>
<RenameWin "World of Warcraft" HiddenDialogBox>
<RenameWin "World of Warcraft" HiddenDialogBox>
<RenameWin "World of Warcraft" HiddenDialogBox>
<Else>
<RenameWin "World of Warcraft" WoW1>
<RenameWin "World of Warcraft" WoW2>
<RenameWin "World of Warcraft" WoW3>
<RenameWin "World of Warcraft" WoW4>


new


//----------------------------------------------------------------
// HOTKEY TO RENAME WOW'S
//----------------------------------------------------------------


<Hotkey ScrollLockOn Ctrl R>
<If WinSizeIs "World of Warcraft" 470 265>
<SendWinM "World of Warcraft">
<RenameWin "World of Warcraft" HiddenDialogBox>
<Else>
<RenameWin "World of Warcraft" WoW1>
<RenameWin "World of Warcraft" WoW2>
<RenameWin "World of Warcraft" WoW3>
<RenameWin "World of Warcraft" WoW4>


*Update: the last code was bugging sometimes because there are too many renames inside one if and this was causing to rename one hidden box and three game clients to HiddenDialogBox, the new code check for the hidden box every time you press the hotkey, when all hidden box are renamed the next time you press it will rename the game clients correctly.
I will leave the old code for comparison If you wanna try.


Hello again guys ;)
If found a new way to rename wows and the hidden dialogs box separately

With the function WinSizeIs i can focus and rename the hidden box using his dimensions (and as far i know this is standard for everyone, 470x265), leaving only the game clients with the World of Warcraft title.

I was doing the rename manually with the hotkeynet action>rename a window, but now i can do the same action pressing two times :cool:

Its a simple thing, but i hope that it can help someone :o

Happy painting multiboxing, peace!

[Scorchant]

old


new


*Update: the last code was bugging sometimes because there are too many renames inside one if and this was causing to rename one hidden box and three game clients to HiddenDialogBox, the new code check for the hidden box every time you press the hotkey, when all hidden box are renamed the next time you press it will rename the game clients correctly.
I will leave the old code for comparison If you wanna try.


Hello again guys ;)
If found a new way to rename wows and the hidden dialogs box separately

With the function WinSizeIs i can focus and rename the hidden box using his dimensions (and as far i know this is standard for everyone, 470x265), leaving only the game clients with the World of Warcraft title.

I was doing the rename manually with the hotkeynet action>rename a window, but now i can do the same action pressing two times :cool:

Its a simple thing, but i hope that it can help someone :o

Happy painting multiboxing, peace!

Any chance you could post your full script? I cant get mine to work after april and just got back to the game. Tried alot of different "rename" versions of my old script but cant get it to work. Would be very greatful. Playing 2 wow on 1 PC.

[CityKitty]

Ok I must be completely dumb. I have tried all the suggestions and scripts here but nothing is working for me. Perhaps part of the problem, at least, is that I am trying to adapt these commands for two wows on one pc to mine, which is two wows on two pcs. Nothing I've tried has worked at all, not even manual rename. The second pc doesn't see any key presses or commands and I know the addresses are correct and the HKNs are communicating just fine. It's just that nothing happens now and this script worked just fine when I used to run it.

Any thoughts on what I should do and what would the command be for two pcs running one wow each?

Thanks in advance for any help!

EDIT: I have overcome the problem by running the following on the second comp but can't figure out how to send it from the script on the main one. The second computer's keyboard doesn't have Scroll Lock.

//-----------------------------------------------------------
// PRESS CTRL R TO RENAME WOW'S IF YOU LAUNCH THEM MANUALLY
//-----------------------------------------------------------


<Hotkey Ctrl R>
<SendPC local>
<RenameWin "World of Warcraft" WoW2>


<Hotkey Ctrl T>
<SendPC local>
<RenameWin WoW2 "World of Warcraft">