EQ2Bot and my swash

[cybs]

This has been bugging me for a while and I've pretty much had it at this point. I don't know if there is something going on with my setup or if I am doing something wrong. So here is the problem: Everytime I pull with my tank, my swash goes in immediately. Which makes it a real pain in the ass to body pull. If I taunt, bow bow pull, hit and move back... swash goes in.

So here are my settings:

Main tab:

MT unselected with tank on drop down.
MA unselected with tank on drop down and assist at 90% health.
EQ2 AF on tank
Retain EQ2 AF in combat

Manual Movement

No other options selected/checked

EQ2Bot options-> Basic Options:

Only thing checked/selected is engage in melee combat.

EQ2Bot Options-> Ignore:

Only ignore epic encounters selected

Navigation:

Camp Pathing selected (Although shouldn't matter because he's AF on my tank?)

Class: No options selected

Extras: BG routine was seleted, is that the culprit?

 

[cybs]

So an update, on a group wipe, I revive the swash then he goes tearing off on his own to start attacking mobs.

I also tried it without the BG option selected and it did the same thing.

 

[wolfppo]

If you want him to just sit by till the mob is in then check the boxes on the main page the no combat movement at all you can make it work even with the % at 99 you pull the mob in and spin it around so your swashy can hit its back as he will af you the whole fight.

 

[Pygar]

If you haven't figured it out yet, one of the 2 sliders on the options panel sets the scan range.

Set this range lower so that the bot wont react to things that are too far away. For a melee follow bot, I generally use 10m. How you play/move your tank you might set that higher or lower.

Your revive issue is an unfortunate result of the bots AI design. What happens is, if the known/designated tank dies, the bot then searches for whoever has the highest HP and is still alive and designates them as MT. In your case, this was itself.

When you revived, the bot was still in the combat routine for some reason (maybe there are too many abilities in each loop of the swash routine, Id have to check) and it tore off after the mob cause it thought it should behave like a MT.

Sometimes its best to wait a moment before reviving, or doing a relay all endscript eq2bot; relay all run eq2bot; to reset it all.

Classes with excessively long/convoluted combat routines are more likely to have the charge behavior you mentioned. For me, I see it on bards/rogues generally.

If/when I revamp these class files they'll use a better method where it never stays in the combat routine for more than 2 spell casts, before exiting to check other feedback.