WoW: slave always disconnects while following

Not only is this repeatable, it is absolutely guaranteed 100%. Slave will disconnect, for example, if I try to lead him onto a boat. Or if I use my arrow keys to move him onto it without switching active clients. Crossing zone boundaries and sometimes trying to get through tight spaces (like an inn with lots of tables) will do it too.
Anyone know what's going on or how I can fix it? I can workaround it by switching the active client, but that's not too convenient.
If it matters, I run both master and slave with ultra graphics. I've tried lowering the graphics on the slave client, with no affect.

This just started occurring or you just started boxing or using a different multiplexer?

This occurs with five accounts as well as just two?

I would blame a multiplexer (or multiple of them running concurrently) if it occurs with two wows.

I would also think that you have some odd directory layouts where your meta data is being shared between clients and they don't cope well with that.

Just started boxing. I'm using one installation of WoW and just using wow.exe instead of the launcher. Autohotkey is what I use to send keys to both windows.

Quote:

---

Originally Posted by jwideman

Just started boxing. I'm using one installation of WoW and just using wow.exe instead of the launcher. Autohotkey is what I use to send keys to both windows.

---

Like I asked, is this happening when you play with just two wow toons versus five? Are all the accounts logged out?

You use ... AutoHotKey or HotKeyNet ? I didn't know people were allowed to use AutoHotKey, cool power on. Is there a copy that doesn't have screen scanning ability or something?

I have never run wow sharing the same \wtf\config.wtf and \Cache\* contents. It seems using the same \Cache\ is the new vogue with isboxer. But those are exactly the files that are written to and read from when you are being logged out.