Key Send Delay?

[nobodyz]

This question might be addressed before, if so, please refer me to the correct location.

Recently i juz switch to windows 7 with i7 processor and mb, 6g of ram..

tri-boxing on wow is fun but i realized that when ever i press a certain key, one of the other 2 windows seems to have abit of delay in receiving the key press. is that normal?

e.g. WoW1, WoW2, WoW3

i press 1 on WoW1, WoW2 will get it almost immediately, while WoW3 might get it after a second or half second delay.. it does not always happen to WoW3, sometimes the reverse, WoW3 gets it, then WoW2.

though the delay is not really a big bother to me, but just wondering if it is normal...

[Freddie]

when ever i press a certain key, one of the other 2 windows seems to have abit of delay in receiving the key press.

Which key? What is this certain key bound to in the game? Could you please post the script so I can see how this hotkey is defined? I can't begin to answer your question without that info.

In the meantime, make sure you set affinity as shown here. If you don't set affinity your three WoW's are restricted to only two physical cores on your CPU. This can cause thread-scheduling problems that sometimes introduce delays.

<SetAffinity all>

[nobodyz]

this script in particular:

<Hotkey F1>
<Toggle>
<SendLabel w2, w3>
<Key S>
<wait 500>
<Key 1>

i understand that there is a wait 500 tag, the delay that i mention, is in addition to the 500 ms that has been introduced to the hotkey.

also, i have set the affinity for my wow clients:

wow1 to cpu 0,1,6,7
wow2 to cpu 2,3
wow3 to cpu 4,5

[Owltoid]

I'm pretty sure that type of script is against the TOS/EULA and should not be used. You should not be introducing delays between sending of keys as it is considered automation. Casting my treants would be easier if I hit the button for the spell, had it delay 500 ms, and then sent a mouse click to position them, but the end result is I pushed one button and got two distinct actions.

HotKeyNet is an absolutely wonderful program and I implore you to only use it within the rules. The program could be turned into a botting utility which would be a huge shame to those of us who use it properly.

[Otlecs]

I'm pretty sure that type of script is against the TOS/EULA and should not be used.

Owltoid is absolutely right.

[Freddie]

The hotkey is written wrong. That's the cause of the problem.

With or without the error, like Owltoid and Otlecs said, the hotkey violates Blizzard's rules.

Game Specific Forum Rules

[Freddie]

The program could be turned into a botting utility which would be a huge shame to those of us who use it properly.

As we've seen in this thread, it's possible to break certain rules with HotkeyNet but I don't think the program can be turned into a bot utility because it cannot detect or react automatically to in-game events.

Since HotkeyNet's beta began, I've seen a few hundred scripts that were sent to me by users asking for help, and only a handful violated Blizzard's rules. It's been my experience that the vast majority of people do not want to risk losing their accounts and are not interested in breaking rules. Most people are pretty fanatical about not taking the slightest risk.

[Owltoid]

I'm sure it was an honest mistake by the OP. That's good to know that HKN can't be used for botting!

[nobodyz]

Thanks all for pointing that out. I have since changed not to use that script. No more problems at the moment