Choppy FPS w/ EQ2Bot in full group (not boxing)

[superslam]

I've noticed this a few times, but I think I was able to pinpoint it last night. I typically just group with one or two characters, and I usually box them on the same computer with no problems.

Last night though, I was not running multiple accounts, but I was in a full group (me + 5 others). During combat everything was fine, but after the mob would die my FPS would drop to 2 - 5 fps and it would be almost impossible to move or do anything. If I clicked "Pause EQ2Bot" then the choppy framerate / lag would go away and I would be back up to 35+ FPS.

To work around this, I would have to pause EQ2bot just before a mob would die, then resume EQ2bot after we got aggro again. This made for some interesting situations, but I was wondering if anyone knows what would be causing this - is there just more overhead for the bot checking each player in the group? Is there an option that I could click uncheck on the bot configuration window? EDIT: Forgot to add, the character in question was a level 80 Female Dwarf Guardian. I also did not have anyone on AutoFollow; I was set as the main assist and the main tank on the EQ2Bot Config.

If this has been addressed 50k times, I apologize for re-asking (I promise I did search, but couldn't find an answer).

Thanks,
SS

 

[Pygar]

The guardian was MT?

Basically, adjust your scanrange first.

The bot is scanning every actor in that range persistently to see if any of them are targeting any ally. If it is targeting an ally it is one of the conditions used to determine hostile threats.

Lower the scan range and your FPS should come back up.

 

[superslam]

Yes the guardian was MT. I lowered the scan range to 5; it was at 50. Does it matter what it's set to if you're not using AutoHunt (I have movement set to manual)? I'll let you know what happens tonight.

Also, is there any way to keep it from casting Bind Wound every time it's up?

SS

Edit: OK, I re-read your post - gotcha. I'll leave it at 5 for now, if that fixes the problem then I may raise it up a bit. Thanks again.