Hotkeynet stopped 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/lib...(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.

[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/lib...(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

[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/lib...(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.