New dual-boxer

[Alq]

Hey, I'm 90% sure I'm going to start dual-boxing another account with mine for a short while(under RAF) to get me two new 60s(maybe 4 if I feel like paying to transfer two chars).

The first problem I am having is:
I can't download octopus. None of the download links appear to work. Either the page won't load or the download has been removed. Yes, I googled.

Secondly, the less important question:
For my first two chars, I'm thinking shaman and hunter.
What I would do is have 8 and 9 on my shaman set to /follow and /cast [target=targetoffocus] chain lightning(or lightning bolt) and then have my G15 spam buttons 8 and 9 and not have them do anything on my hunter. Then I just play the hunter(except for looting basically).
Does this sound like a good idea? Would their be something significantly better without requiring me to actually have experience at dualboxing?


Thanks,
Alq.

[Chranny]

[...]then have my G15 spam buttons 8 and 9 and not have them do anything on my hunter. [...]

If you are talking about automation here then I would say no.

[Castamon]

http://ftp.heanet.ie/disk1/sourceforge/o/oc/octo/
Thats the octopus download link

Download the last link for latest version.
Took a while for me to find. But here ya go!

[Svpernova09]

I don't think Octopus is even supported anymore. You should check out a software package that is still supported Keyclone / HKN / IS

[Otlecs]

have my G15 spam buttons 8 and 9 and not have them do anything on my hunter. Then I just play the hunter(except for looting basically).

It might just be your choice of words, but if you really mean to use the G-15 delay feature to automatically feed keystrokes to your WoW client then you'll fall foul of the ToS and run a very high risk of getting your accounts banned.

As Chranny said, automation is a very big no-no.

Would their be something significantly better without requiring me to actually have experience at dualboxing?

Although there's a small cost associated with it, Keyclone remains the simplest turnkey solution.

[Castamon]

Personally I use HKN, but i also have a license to Keyclone, and i must say its a very good program, however i perferr HKN.
HKN takes some time to learn, but if you want a simple, yet Powerful dualboxing software solution, then Keyclone is the for you.
Plus the maximizer feature is remarkable.
8)

However, Even Unsupported, Octopus is still a verryyy good tool. Quite similar to keyclone. Give it a shot.
I posted the link.
But as nova said, unsuported. But if you dont want to cough up 20 bucks for keyclone, and fine HKN confusing, i think Octopus is a great option too. 8)

[Ughmahedhurtz]

I don't think Octopus is even supported anymore. You should check out a software package that is still supported Keyclone / HKN / IS

I'll grant you the general point but follow up with a question: if Octopus isn't buggy, why would it need support?

/ducks

[Alq]

Hm. I've never used the G-keys before but I figured it was a good reason to start. Glad to know it's against the TOS, I could see people getting off easymode with them ^_^

Octopus is giving me an error. "Octopus has encountered a problem blah blah" nonsense when I open it.

I need a new job before I start paying to dualbox, but when I start I will tell you how I do!

Thanks for the help!

EDIT:
I downloaded HKN, And it doesn't seem too complicated(I've done minimal programming before so I understand the concepts)

I basically want it to send numbers(1-9, not numberpad), q,w,a,s,d,e, space, and (MODIFIER = LCtrl) RButton, LButton
My text file looks like

<Hotkey 1>
<If ActiveWinIs wow1>
<SendWin wow1>
<Key 1>
<SendWin wow2>
<Key 1>
<EndIf>
<Hotkey 2>
<If ActiveWinIs wow1>
<SendWin wow1>
<Key 2>
<SendWin wow2>
<Key 2>
<EndIf>
<Hotkey 3>
<If ActiveWinIs wow1>
<SendWin wow1>
<Key 3>
<SendWin wow2>
<Key 3>
<EndIf>
<Hotkey 4>
<If ActiveWinIs wow1>
<SendWin wow1>
<Key 4>
<SendWin wow2>
<Key 4>
<EndIf>
<Hotkey W>
<If ActiveWinIs wow1>
<SendWin wow1>
<Key W>
<SendWin wow2>
<Key W>
<EndIf>
<Hotkey A>
<If ActiveWinIs wow1>
<SendWin wow1>
<Key A>
<SendWin wow2>
<Key A>
<EndIf>
<Hotkey S>
<If ActiveWinIs wow1>
<SendWin wow1>
<Key S>
<SendWin wow2>
<Key S>
<EndIf>
<Hotkey D>
<If ActiveWinIs wow1>
<SendWin wow1>
<Key D>
<SendWin wow2>
<Key D>
<EndIf>
<Hotkey Q>
<If ActiveWinIs wow1>
<SendWin wow1>
<Key Q>
<SendWin wow2>
<Key Q>
<EndIf>
<Hotkey E>
<If ActiveWinIs wow1>
<SendWin wow1>
<Key E>
<SendWin wow2>
<Key E>
<EndIf>
<Hotkey Space>
<If ActiveWinIs wow1>
<SendWin wow1>
<Key Space>
<SendWin wow2>
<Key Space>
<EndIf>
<UseKeyAsModifier LCtrl>
<Hotkey LButton>
<If ActiveWinIs wow1>
<SendWin wow1>
<Key LButton>
<SendWin wow2>
<Key LButton>
<EndIf>
<Hotkey RButton>
<If ActiveWinIs wow1>
<SendWin wow1>
<Key RButton>
<SendWin wow2>
<Key RButton>
<EndIf>

It keeps telling me LCtrl is already a modifier, and when I load HKN(without renaming the textfile) I can't click on ANYTHING on my screen. To close the window I have to alt+f4 out.

ALSO: Can I have it permenantly name my two wow windows instead of doing it individually each time(1 Wow.exe from the same folder loaded twice)?
Edit again!: I think I fixed this with

<hotkey ctrl R>
<RenameWin "World of Warcraft" "wow1">
<RenameWin "World of Warcraft" "wow2">

Thanks a ton(Again!)

[falsfire3401]

As to your broadcasting mouse clicks, don't do it via a button, use the ClickMouse command (but do not specify coordinates, that's skirting the TOS dangerously, let it just scale the position). Also, since Ctrl is already a modifier you don't have to code in UseKeyAsModifier for it.

I use HKN and I've found no need to ever LClick anything on the slave window, so I just have it set to send a right-click when I Ctrl-RightClick.

My code looks something like this (going from memory cuz I'm at work)

<Hotkey Ctrl RButton>
    <SendWinM wow2>
        <ClickMouse RButton>

That way when you need to interact with something other than an NPC/corpse on the 2nd wow (ie the translocation orb from UC->Silvermoon, any "gear" activated objects on the ground), you Ctrl-Rightclick on approximately the right part of the screen (based on the alt's point of view), glance at your 2nd wow client to see where the 'gauntlet' actually appears briefly to tell if it's out of position or not.



To interact with NPC's/Flight Masters/Innkeepers/Loot Corpses, you should use the new 'InteractWithTarget' UI feature:
1. Setup a macro on your slave that says "/target party1target". Put it on an action bar and keybind a key to it, I use backslash. Setup HKN to broadcast that key to your 2nd wow.
2. Go into keybindings on your slave and find wow's "Interact with Target" keybind. Bind another key to it (I use Shift-backslash). Setup HKN to broadcast that key to your 2nd wow.

Now whenever you want to loot something or interact with any NPC, be it a questgiver, flightmaster, innkeeper, vendor, etc...you target it (or the corpse) with your main, and then press Backslash Shift-Backslash and your slave will target & interact with it / loot it.



Also, you should always use SendWinM instead of SendWin. SendWin will bring the other window to the foreground, causing your main wow to lose focus and most likely mess up your play. SendWinM sends the keystrokes to a window in the background and leaves it in the background.

[Alq]

My keys are set up like

<Hotkey W>
	<SendWinM wow2>
		<Key W>
	<SendWinM wow1>
		<Key W>

It says they are sending to the clients, but they don't appear to be working.
Not only that, my keypresses are very delayed, I don't know if it is my computer failing or the program slowing them.
I can type in chat, so I know it's at least getting sent to the wow1 window. But when I do it ends up looking like
Hye gu syi ened hel pwit hthis(Hey guys i need help with this)
Forcing me to type slow and backspace like 5 times per message.
It may not be as extremely delayed as I put it, but you get the idea.

Any help would be appreciated.
My characters both jump fine...
But when I try to move nothing happens
when I jump and hit W at the same time, they move slightly forwards.
Sometimes they will turn like 2 degrees when I am spamming all the buttons as fast as I can.
It really is confusing me.