Can't get the HotkeyNet Sample script to work

[Khatovar]

That error is irrelevant. It's simply HKN looking for anything that it should do without you using hotkeys, such as autolaunching WoW or creating buttons.

1. Are your paths set properly? <Run "c:\Program Files\World of Warcraft\WoW.exe">
2. Is your Scroll Lock on? <Hotkey ScrollLockOn A-Z....>
3. Are your WoWs renamed? <Hotkey ScrollLockOn Alt Ctrl L> or <Hotkey ScrollLockOn Ctrl R> if you launched instances manually
4. Are you activating mousing properly? You must hold down oem3 {the tilde key ` } while pressing the mouse buttton.
5. Are you running both windows as active or are you minimizing the secondary window? I don't see a resize code in that script. The below code will add a large window for your main WoW and a small window for your slave WoW on the same screen. You may need to adjust based on your screen size.

//----------------------------------------------------------
// 	SUBROUTINE TO Position Windows for 2 boxing.
//----------------------------------------------------------
<Command ResizeAndPosition>
	<SendPC Local>
		<SendWinM %1%>
			<SetWinRect 0 0 1288 1020>              
		<SendWinM %2%>
			<SetWinRect 1290 0 390 356>

Then add <ResizeAndPosition WoW1 WoW2> in the Launch and Rename section so it reads like this

//-----------------------------------------------------------
// HOTKEY TO LAUNCH AND RENAME BOTH WOW'S.
//-----------------------------------------------------------
<Hotkey ScrollLockOn Alt Ctrl L>
    <LaunchAndRename Local WoW1>
    <LaunchAndRename Local WoW2>
<ResizeAndPosition WoW1 WoW2>

You may need to adjust based on your screen size. One way to do this is to take a screenshot of your desktop {PrtScn in Windows} and pasting it {ctrl+v} into a paint program like Paint.NET, then use a draw rectangle tool to visualize how you want it set up.





The pink rectangle would be your main window, the blue would be the slave.

The first set of numbers you need for SetWinRect are the x,y coordinates for the upper left corner of the windows {0 0 for the main and 1290 0 for the slave using my example}. Paint.NET shows this in the lower right corner of the program. Alternately, you can get these coordinates by opening HotKeyNet and clicking your mouse anywhere on your screen where you want the window to be placed. In the Last Key Press Window you will see "scrn position: x = 0 y = 0"

The second set of numbers for SetWinRect are the dimensions of the windows {1288 1020 for the master and 390 356 for the slave in my example}. This is shown in the bottom left corner in Paint.NET and states how many pixels wide {1288, 390} by how many pixels high {1020, 356} the specific window should be.

Here's what I'm trying to do:

Have spells, click-to-move, accept quest, turn in quest, and interact with NPC basically mimicked on my inactive window?
...
I'm trying to get the game to run on one machine/monitor and have hotkeynet just mimic my mouseclicks, targeting, and key pressing on my inactive window.

It sounds kinda like you're trying to do everything with your mouse. That's really not going to work well for multiboxing. It's almost all keybinds and macros and that script you are using only allows for manually triggered mousepassing {ie. mouse will only be passed to the slave screen if you are holding down the ` key} .

Spells - Should be all keybound macros/spells triggered with keypresses. You will need a spell/macro on the master and one on the slave. We'll take shamans for example, since everyone loves them. This is just down and dirty examples to get you going. You'll have time for elegant and complex later.

The main is easy enough, you can simply drag Lightning Bolt from your spell book and drop it on 1.

However, the slave needs a macro or other means of knowing what your master is targeting. You can do this with a manual assist, a built in assist or by using focus.


Manual Assist - This is a button that you press before you start attacking, but after your main has a target to tell your slave to pick up the target.

• On your slave make a macro that says simply /assist toon/party#/focus using either the name of your main toon, the party number of your master {if your main is always the party leader, this will be party1} or your focus target {see below}.
  
• Place that macro on a keybind. I use [
  
• Target a mob on your main and then press [ Your slave will now pick up the same target.
  
• Place Lightning Bolt on the same keybind that the master uses {1}.

Built-in Assist - Rather than assisting prior to combat or having to use a keybind to assist, you can macro it directly to your spells.

• On your slave, make a macro for Lightning Bolt, adding /assist toon/party#/focus to the top of the macro.
  
  

  /assist Kina
  /cast Lightning Bolt

• Place that macro on the same keybind your master uses {1}. Your slave will now target and cast in the same keybind.

Focus Assist - Rather than acquiring a target, your slave simply casts on what their focus casts on without actually targeting anything. This, like manual assist, requires initial setup, but does not require constant interaction with another button.

• On your slave, create a macro to set your focus. /focus toon/party#/target {if you use target, you'll need your slave to target someone first, which you can do manually or you can do /target toon /focus target which is rather roundabout}.
  
• Place that macro on a keybind. I use Home. As long as you don't do anything to clear your focus {logging out, setting a new focus, changing the main toon in the party, ui reloading} you will only need to use this key once per gaming session.
  
• On your slave create a macro for Lightning Bolt adding a targetting conditional to the line
  
  

  /cast [@focustarget] Lightning Bolt

• Place that macro on the same keybind your master uses {1}. Your slave will now cast on whatever your master has targeted without actually having a target of their own.

Click-to-move

Your slave should only actually Click-to-move on their own in combination with interact with target. It should not be used for normal movement. For travel and such, your slave should always simply follow your main. Because of things like latency, resoultion, camera angles and even slight degrees in variance of facing, your slave will never perfectly mirror the master for movement. This is why we all use follow commands instead of sending movement keys to slaves.

For quests and such, review my FAQ on Jamba Jamba - Getting Started, particularly the sections Now what? -> What do you mean "push"? in post 1 and Quest -> Quest Completion in post 3.