Agreed, I didn't see it mentioned but one way to compensate for class differences is to have certain keybinds actionless on some clients. For example, the "1" key on your DPS could be mapped to a DoT, whereas on your HPS it is blank. As mentioned, common-overlap can be had. Where both toons offer DD spells which have a similar cast-time, and sometimes "differing" cast times for non-interruptable spells can be put to use. For example casting a Shadow Bolt on a lock while also casting an instant on the Priest, then hitting another key that ends up being ignored by the lock (because it's busy) but respected by the priest (because GCD has already reset.) I may have explained that poorly, but the idea is you can put cooldowns and cast-times to efficient use so that in your "rotation" you get a non-symmetric yet efficient set of spells from both classes. Where symmetry cannot be had and you clearly need "DPS only" or "HPS only" behavior without a lot of complexit, put your cast bars to good use (e.g. SHIFT+1 through SHIFT+6) so that SHIFT+2 is DPS-only and SHIFT+3 is HPS only, SHIFT+1 would be your "common overlap w/blank actions" action bar. It should work quite well for you. Finally, you can rebind all of your keys as many people do. I run 5 locks and 1 priest for heals while boosting, my priest has keybinds for "R" through "P" on the keyboard. These are actionless on the locks, which lets me indepedently activate my healer. The downside is you can quickly run out of keys for unique keybinds. If you run two mages and two priests, as an example, this latter option is probably the most efficient in terms of cast-time overlap, targeting and mana-use.
When I began multiboxing I ran a destro lock and holy priest up to L72. I didn't use a multiplexer and basically alt-tabbed between the two instances. Ultimately I wrote my own tool to do exactly what I needed. I have to admit that using a multiplexer significantly reduces the potential for carpal tunnel syndrome, and thus using a keyboard multicaster/braodcaster/multiplexer such as keyclone, HKN, etc is worth it, and works well.
Key translation isn't much different from re-mapping your action bars and keybinds. So, if you can, try and remap your actions first. Secondly look into utilizing a good spread of Macros, such as cast sequence macros, to acheive differential cast rotations between multiple classes.
Lastly, a good mouse cloner would help for those "one off" actions that simply don't map well or you lack the keybinds to handle, but have plenty of extra action bar buttons to compensate.
Hope that helps![]()
Connect With Us