MultiBox (software)

I haven't had a chance to try this (at work atm), will this broadcast to multiple wow instances running on a secondary computer?

nemesis
No, WoW will need to be in the foreground of every computer. While it is possible to inject input into a background process it gets ever closer to automation and crosses a line that I am not willing to cross. Playing a game that isn't the active application looks way too much like a bot for my taste.

Rowan
One option for stopping movement is to bind a key to stop on each of the client computers that you can press when you are ready for them to stop. Unfortunately you can't put it into a macro that I know of. :(

Quote:

---

Originally Posted by Ellay

Their opinion on banning for 3rd party software involves anything that is automated or does actions on its own. Broadcasting keystrokes is perfectly legal.
Although it is up to Blizzards discretion on what they run through their system. They have made it known that hardware devices that broadcast keystrokes are fine, and I've sent messages to GM's inquiring if using software to broadcast keystrokes was legal. It was sent to a supervisor who approved it and said as long as it does not automate or think on its own your fine.

So overall I think the risk chance is extremely low, but this is just my opinion.

---

Still, if there is a risk of losing characters with 60days game time is dangerous to say the least. I was bored a bit, so I asked a gm (eu realms).

http://www.dutchpeanutforce.nl/WoWSc...07_165446x.jpg

I got a bit annoyed of the automated answering gm's are doing these days so i stopped herassing him/her. Guess I will write an email to that address and see what i get in return.

Also i read once that blizzard installes software that detects, or trys to detect software interfering with their processes? (btw excuse my english, not my native language, and am a bit tired ;))

Hi :).

So i've been tinkering with this and i cant seem to get my clients to see the server. Any ideas what would cause that? or how to get it to work. the software sounds amazing like old xilophone.

Amazing program, and it is working flawless for me for about 5 minutes at a time, just curious if anyone has a similar problem.

I'm using a desktop & laptop on my home network, both connected to each other. They are both rather high end, and I'm playing WoW on both.

I can setup the server & clients and dual box perfectly for about 5 minutes. then while on my main display, I move the mouse over to the laptop, but it just stops at the edge of my main display. Then when I move it around, it lags badly, jerking all over the screen. After a few seconds it is fine, but I'm unable to switch over to the laptop.

The only way I've found to fix it is to restart the server, reconnect both clients, then I get another 5 min or so of good use. Any suggestions I could try?

Hopefully Micah knows a possible fix, for the time being I'll do some testing and see what I come up with.

Also to add, try out Synergy with broadcasting and see if that works for the time being.

I tried Synergy, however the service would have some kind of critical error on the laptop when it tried to connect. I'll give it another go later.

Basically the functionality of Multibox is exactly what I'm looking for (when it works for me). Being able to just mouse between monitors, no alt+tabbing, and without broadcasting.

Has anyone had experience using something like a firewire cable to connect 2 pc's and having Multibox communicate that way? Is it any faster/more reliable?

Thanks in advance for the help.

I fixed a crash bug caused by having too much data in the clipboard. I have updated the link without source in the original post, the link with source is still outdated. Try this version and let me know if it fixes the problem for you, I had a similar problem and this did the trick.

Thanks so much, I'll give it a try as soon as I get home. I thought I'd unchecked the clipboard option, but I may not have.

This may be completely wrong, but the impression I got when the problem occurred was that it only happened when I didn't move the mouse from one PC to another for a few minutes. For example, I never noticed the problem while going back and forth - only after I'd been on my primary for a few minutes, then tried to move the mouse back to the laptop. Is it possible that there is some kind of inactivity timeout going on?

Thanks again!

It is possible that it has to do with Windows caching, though I'm not sure why that would have an effect. Let me know if the updated version fixes the problem or not either way.