Latency can be a real factor. If you are quickly changing targets and then hitting assist, the server might be sending your slaves the previous target instead of your new target. I guess it all depends on when you selected versus when they requested from the server who you were targeting. There seems to be some latency with this.

I have conditionals that choose targets optimally. First it tries to assist the character I'm driving from. Then it tries to assist one of the melee (if it is range) or finds the nearest enemy (if melee) or simply follows the driving character if there is still no available target.

It looks like this. Modify and append to any of your dps macros.


/stopmacro [@target, nodead, exists, harm]
/assist {FTL}

/stopmacro [@target, nodead, exists, harm]
/targetnearestenemy
/targetenemyplayer

/stopmacro [@target, nodead, exists. harm]
/assist <MELEE NAME HERE>

/stopmacro [@target, nodead, exists, harm]
/follow {FTL}

There is a danger when using this if you fat finger the key ( I have done this ) in a PvP flagged area your characters WILL target other players and attack them. So be ready for that. Usually that is what I want but I've killed myself doing it, too.


Note: This won't fix the issue of having them on separate targets. This still happens with me from time to time but it happens far less because melee will engage first and the range will assist the melee. If I have a target, they will of course try to assist me first.