Printable View
Anyone noticed that even if you choose SendWin, SendWinM or SendWinMF, you have to click 2-3 times for the 4 slaves to target the main chars mobs? or is it omething only i suffer from?
Im gonna break my finger soon i think after mass-clicking assist to have some sort of Micro going on in instance.
(tried search)
I focus my main. I use HKN to broadcast keys. So my targeting is in my macros. I use
/cast [target=focus-target] UltimageDamage (for DPS)
and
/cast [target=focus-target-target] SuperHeal (for healing).
So I don't really have to wait for targetting.
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
When this happens with SendWin, it's usually because HKN types too fast. What happens is, the computer takes maybe 100 ms each time it activates the next WoW. By the time that finishes, HKN has already typed the command but WoW didn't receive it because it wasn't activated yet. The solution is to slow down HKN's typing. Unfortunately the only way to do this is to insert a delay in the hotkey, which frightens some people because they think all delays are against the rules. I don't think this type of delay is against the rules because even with the delay, you are typing commands into WoW as fast as the computer is capable of doing it. But I don't work for Blizzard.Quote:
Originally Posted by 'legg1',index.php?page=Thread&postID=70651#post706 51
When this happens with SendWinMF, it's usually because the second Background Focus Delay number on the settings panel needs to be longer.
I've never seen this happen with SendWinM and WoW together, so I don't know what's up with that. :(
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 ?
Aren't you guys saying that you have macros used for targeting and a hotkey to activate the macro? If that is the case then there is no typing involved. I think it's latency. Sometimes my /target focustarget macro connects on first click, sometimes it takes two.
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:Quote:
Originally Posted by 'legg1',index.php?page=Thread&postID=70665#post706 65
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 F1>
<SendWinM "World of Warcraft">
<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.Code:<hotkey F2>
<sendwinm World>
<text /><wait 100><text say hey there bud wassup>
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.
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.Quote:
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 ?
However, you could type the "/" to open chat and THEN activate the hotkey <text say hey there's Bud> , yes? I haven't tried this.Quote:
you have to avoid chat line commands
That would work. But if you do it the way you and Electron are recommending, does the chat line get used?
Nope, I haven't started building chat commands in HKN yet. I probably will...one day.
Wow way to forum.... Can we get this moved out of the movie forums.
i'd be very careful with HKN... this kind of thing is completely bannable by blizzardCode:<hotkey F2>
<sendwinm World>
<text />
<wait 100>
<text say hey there bud wassup>
Hey Legg.....can we clarify, are you sending single keys that are mapped to Macros, or are you sending the command (ie /asssist) as part of the hotkey definition?. are you running multiple clients per PC?
Perhaps show your Hotkey config file.
I multibox across PCs and multiptle clients within a PC and don't experience this.
You could also come post on the HKN forum if you want.
www.hotkeynet.com
[quote='keyclone',index.php?page=Thread&postID=7070 9#post70709][code]<hotkey F2>
<sendwinm World>
<text />
<wait 100>
<text say hey there bud wassup>[/code]
i'd be very careful with HKN... this kind of thing is completely bannable by blizzard[/quote]
Is that because it types on the chat line? Or because of the delay? If it's the delay, the only reason it's there is to slow down the typing so it can be read. Suppose the typing was slowed down by something that paused for a few milliseconds after every keystroke, like AuthoHotKey's [url=http://www.autohotkey.com/docs/commands/SetKeyDelay.htm']SetKeyDelay[/url] command. Would that be legal?
any delays are where the question gets raised.
the other would be the single keypress spawning multiple keys input to the client
ie:
F2 --> /say hey there bud wassup
in this case, 1 key press turned into 25 plus enter. definitely ban-able as per blizzards policy (1 key pressed == 1 key entered into the destination window)
and yes, AHK gets into these kind of grey areas.
the G15 keyboard is iffy.. and blizzard tolerates it due to logitech being the company they are.
if this weren't the case, keyclone would have had out-of-game macros a long time ago
Okay, in that case, the whole question of slowing down the typing is moot because chat commands themselves are illegal. Thanks for educating me.Quote:
Originally Posted by 'keyclone',index.php?page=Thread&postID=70746#post 70746