HKN help needed

Its my first time using HotKeyNet and first attempt at multiboxing so im starting simple. Ive read a decent amount on how the <hotkey " "> thing works so I have some very basic knowledge on it.

im using 1pc for 2 WoW accounts and using HKN and my HKN is already targeting a script I wrote.
Im starting supper basic and already bumping into problems.

i have the following written down in my script.


<hotkey 1>
<sendpc local>
<sendwin WoW2>
<key 1>



Now, when I press the 1 key on my main window 'the one im trying to use to control the other' it jumps to the other window and then presses the 1 key which is my crusader strike key.

Why does it jump to the other window and then do the command?

any help would be much appreciated :)

It jumps to the other window because that's the only place you told it to go with <sendwin WoW2>. That's not how you structure hotkeys.

First, this hotkey {1} should already be defined in the standard script under the keylist. You shouldn't need to redefine it as an individual hotkey.

If you're using the sample script from here, 1 is already defined as a hotkey in these lines {highlighted in red} :

Code:

---

//-----------------------------------------------------------
 // DEFINE HOTKEYS FOR ALL KEY COMBINATIONS THAT WILL GET
 // SENT TO BOTH WOWS. ADD MORE KEY COMBO'S IF YOU WANT.
 //-----------------------------------------------------------
 <Hotkey ScrollLockOn A-Z, 0-9, Plus, Minus, F1-F12 except W, A, S, D, Q, E>
 <SendLabel w1, w2>
 <Key %Trigger%>

---

As far as the command you've written for Hotkey 1, you have a couple problems.

The sample script uses SendWinM, you should avoid using differing sendmodes in your script.

You shouldn't define sendmodes in hotkeys. Hotkeys should use the Label that is defined at the start of the script, in the "Mail Labels" section -

Code:

---

//-----------------------------------------------------------
 // DEFINE MAIL LABELS FOR SENDING KEY STROKES
 //-----------------------------------------------------------
 <Label w1 Local SendWinM WoW1>
 <Label w2 Local SendWinM WoW2>

---

These mail labels also already define that the PC is Local, there's no need to define it again in the hotkey itself.


Finally, under normal circumstances, your script should be throwing errors about 1 already being defined, but the sample script is set up with a modifier for the keylist

Code:

---

// Toggle the scroll lock key to turn hotkeys off and on. (You
 // can change this if you want, just like you can change
 // everything else with HotkeyNet.)

---

Code:

---

//-----------------------------------------------------------
 // DEFINE HOTKEYS FOR ALL KEY COMBINATIONS THAT WILL GET
 // SENT TO BOTH WOWS. ADD MORE KEY COMBO'S IF YOU WANT.
 //-----------------------------------------------------------
 <Hotkey ScrollLockOn A-Z, 0-9, Plus, Minus, F1-F12 except W, A, S, D, Q, E>
 <SendLabel w1, w2>
 <Key %Trigger%>

---

HotKeyNet's sample script is set up so that if you do not have scroll lock ON, you are not broadcasting keys. This way when Scroll Lock is off, you can run your active window without sending anything to your slave window. Adding the additional hotkey without the Scroll Lock On modifier means that 1 will be sent all the time.

A properly constructed hotkey, assuming it wasn't defined in the keylist, should look like this

Code:

---

<Hotkey ScrollLockOn 1>
              <SendLabel w1, w2>
                <Key 1>

---

The link in my sig for HotKeyNet breaks down every line of the starter script and explains how to use and modify it.

The laptop im using dosent have a scroll lock and I like to experiment and challenge my self so I tried to write some of my own.

In the end after reading what you have posted I gave in busted out a keyboard with scolllock plugged it in and copy pasted that code. Everything works flawlessly but I can see that there is a ton of things that I would like to work on and improve, SPECIALLY facing targets, that gets annoying fast.

thanks for taking time to post and help me Khatovar seems like you know youre stuff

You don't have to use ScrollLock. I don't use it. It just means you need to take the ScrollLock out of the Keylist. I believe the original intention of having the keylist using ScrollLock is that the ScrollLock has a lighted indicator on many keyboards that people can use as a visual indicator to whether or not they are broadcasting. You can change it to use any toggled state {CapsLock On/Off, ScrollLock On/Off, NumLock On/Off tend to have lighted indicators on keyboards} or no state at all. I simply use the Pause command to turn off my hotkey broadcasting.

Code:

---

<hotkey Pause>
        <sendpc local>
                <ToggleHotkeys>

---

For facing, you will want to look at Interact With Target and follow. I talk about movement issues, including facing, in this part of the Newbie's Guide Vol. 2. I also have a bit on IWT at the bottom f the post here and the Quest section of the Jamba guide here.

Ill look into that, facing is a tad challenging. Ill look into jamba , will definitely download it today if it makes multi boxing easier