Quote Originally Posted by 'legg1',index.php?page=Thread&postID=70665#post706 65
I've got:

/target [target=party1target] for assist
/follow party1 for follow.

tried both seperate, and in 1 macro.

Still takes 2-3 clicks before they react
I've never played WoW so I don't know how those commands execute, but if they get entered on the chat line, I can tell you a reason why this isn't working. In WoW (like many games) the client takes a huge amount of time (by computer standards) to move the cursor to the chat line. You can see this by making a simple hotkey like this:

Code:
<hotkey F1>
<SendWinM "World of Warcraft">
<text /say hey there bud wassup>
I deliberately omitted the final "Enter" so you can read what gets typed on the chat line. If you press this hotkey when the cursor is not yet on the chat line, you'll see that nothing gets typed on the chat line except the initial slash. Why? Because HKN finishes typing before the cursor reaches the chat line. If you want the hotkey to work, you have to insert a delay like this:

Code:
<hotkey F2>
<sendwinm World>
<text /><wait 100><text say hey there bud wassup>
You probably don't need a full 100 ms there, but it's a good idea to start with more than you need and whittle it down till you find the shortest delay that works on your machine.

Like I said earlier, I don't think this type of delay violates the rules because it's simply there to make HKN's typing speed match the client. It's not separating one command from another. in fact there's only one command. But if you disagree or you're worried that Blizzard disagrees, you have to avoid chat line commands. There's just no way to type them with HKN without using an explicit delay. HKN types too fast and the typing has to be slowed down.

wouldnt that be the same as setting delay in the "Settings" page of HKN, to make it use 100ms between the windows ?
Or do you mean directly into the hotkeys.txt file ?
Background Focus Delays on the settings panel isn't a delay between windows. It's an extremely short delay used internally by HKN with SendWinMF (and only SendWinMF) when it tries to fool the target window into thinking it's in the foreground even though it's not.