Race Issues with 5x multiboxing casters

[Nandus]

Hey Guys,

anyone of you does multiboxing with more different races? I start a new team with 4xMage/1xDisc - 1x dwarf, 2x gnomes, 2x human.
I thought it’s a cool idea to have different races especially because of 5%int Bonus of gnome mages and fear ward of dwarf priest (but overall I more like human females because of casting animations and better fitting equipment ) - but already from lvl 1-10 the gnomes got stuck multiple times, or the two human mages are attacking the target and the gnomes are standing there and are out of sight (because of smallness)

What are your experience ? You go with 5x the same race?

[nodoze]

I drive from a Human Warrior and have following 2 human Warriors and 2 Dwarven Paladins and occasionally my 2 dwarfs would get stuck (I think due to size issues going up big steps/walls/hills). Less frequently one of my human would also get stuck.

This could be problematic for me in that the Dwarfs would just be stuck there running against the step/wall and not heal me (even if in range) unless I make them stop following or have them catch up. The one time it was a real problem was in the SM Graveyard.

The fix for me in most cases would be to issue a jump command to my whole party and the ones trying to catch up would clear whatever obstacle was in the way and catch up.

Now that I am aware it doesn't really bother me and EMA helps me know ASAP if there is an issue.

I think I will keep my class/race combos BiS and I don't think I will be trying to match races.

[Madsage]

I made a 4 Gnome 1 Dwarf team and gnomes are an absolute multiboxing nightmare, they get stuck so easily and can't swim, the infamous Darkshore water collection quest wiped out my gnomes

[Ughmahedhurtz]

How do you track things like your followers no longer following? I did gnomes for a bit back in the day. Yeah, they're easily stuck on things but EMA/Jamba have warnings that let you know when that happens (as long as you pay attention to it lol). There are ways around it. Not a lot different than learning to run up circle stairs in e.g. one of those horde blimp towers.

[nodoze]

How do you track things like your followers no longer following? I did gnomes for a bit back in the day. Yeah, they're easily stuck on things but EMA/Jamba have warnings that let you know when that happens (as long as you pay attention to it lol). There are ways around it. Not a lot different than learning to run up circle stairs in e.g. one of those horde blimp towers.Besides getting used to the stuck/follow-break issues and maneuvering to avoid them I keep EMA in a prominent position and easily see the warnings if anyone breaks follow. EMA is actually part of my scan now in that I know when it should/shouldn't be lit up.

When running around I also practice making my whole party jump just so that if/when I need to do it during a stressful time it isn't something I have to think about. 95% of the time it happens making the group follow(if not already) and having everyone jump clears the issues (unless you are on steep cliffs for some reason).

[Apatheist]

I found it was easier to just train myself to keep an eye on my alt windows to see when they stop moving. The problem with EMA/Jamba is that they spam you with so many alerts that I ended up tuning them out. Every time I stop my casters to cast or drink I get an alert that they're no longer following, etc.

It would be nice if EMA could interact with ISBoxer in some way to help distinguish between characters breaking follow because a movement key or IWT was activated versus when they stop following for some unknown reason.

[Madsage]

I made a habit of spamming follow button when navigating tricky terrain, I use WASD for movement and Q for follow, mouse scroll is also good for spamming.

[Mercbeast]

I use esdf, and shift-f has been impulsively spammed by me when multiboxing since 2004 :)

Also bind something like shift or alt or ctrl-space to jump on your other clients, so you can easily hit space, shift-space to make your main jump over an obstacle, and then your minions jump immediately after.

For an all caster group, you could also use EMA strobing. It works "ok" for melee, but if you use it with melee you need to be driving with a melee and dragging mobs away from your group so they always face the mobs, or you need to spam an IWT hotkey so the minions will keep turning to face the target when they can auto attack. With casters it's not as big of an issue, and when I was playing with my 60 priest + 4 low level mages, I was running strobing on like .5s pulse, and it worked great for aoeing. I'd run around body pull with the priest, get agro, and then AE everything down with the mages, and never ever had to worry about characters breaking follow.

[moosejaw]

I found it was easier to just train myself to keep an eye on my alt windows to see when they stop moving. The problem with EMA/Jamba is that they spam you with so many alerts that I ended up tuning them out. Every time I stop my casters to cast or drink I get an alert that they're no longer following, etc.

It would be nice if EMA could interact with ISBoxer in some way to help distinguish between characters breaking follow because a movement key or IWT was activated versus when they stop following for some unknown reason.

EMA has a setting to not warn when drinking/eating while strobe is active. When they finish the drink/eat they stand back up when follow is on strobe again.


On this topic I have an all undead team and they keep getting stuck on the small steps at the doorways in SM. Jumping won't get them over the steps. I have to run a little bit ahead and strafe them back and forth till they finally get past it. Even the lead toon gets stuck on those damn steps. SM Armory entry to Herod's room is the main offender.

I have noticed some other weird behavior with slaves randomly dismounting without any interaction or mob attacks. It's like the GM's are screwing with me. :)

[Orkus]

I have an Undead team and can confirm that they get stuck in the Scarlet Monastery steps especially the female models.