Printable View
If I am 5 boxing on 1 computer, can I have it so I just have my main guy up then minimize all the other wow's instead of having a screen for each so I can just play on 1 big screen instead of looking at 5 small ones?
And then if I can get that done is it possible to loot on another character if my main's bags get full? Would i just switch to another guy and make that my "main" for say?
yes - that's what I do.
Minimizing is BAD BAD BAD BAD, mmkay? You absolutely MUST be able to see whispers on all clients. Think about this. You have CloneX, CloneY, CloneZ, and Clone0. Well, you play CloneX as your main, but the GM gets the typical "lame botter" complaint and goes "meh, probably just multiboxing, I'll ask him". So then he whispers CloneZ and goes "Hey, I got a complaint about you....you a bot?"
Then, you spend 10 straight minutes grinding in an instance. Now what's that gonna look like from their perspective? Bans I tell you, bans!!
Never minimize if you don't have to -- keep chat windows nearby.
Ehh, /dnd talk to Xzin
I never monitored chat boxes on the Zins.
^^^^Quote:
Originally Posted by Xzin
sometimes I dont even bother to reply on my main screen... :D
The Chat is not the the problem.
I still like to see what my little minions are doing *g*
The dualboxing kit addon will relay the messages to your main, making it so you never miss anything :)
Whenever I minimise my alts never keep up, but I haven't really tried on my new Vista installation. To minimize latency on my main window, though, I use keyclone to keep all my alts at 5 fps, with my main not capped. Hehe, its like they are not even there!
(Heaven forbid if the main dies, though >.>)
I find this way too useful to warrant minimizing screens (which I dont need to)Quote:
Originally Posted by Ilion Sturmlied
And twoboxtoolkit is great for things like that. However the most recent version seems to be messed up. I get constant errors on all characters upon entering org. The error points to a line in the lua file talking about the stickyfollow but I have it disabled so I just went back to 1.55 and it works fine again.