For some reason after this past update when I attack all my guys are bouncing and moving around a lot. I use all CWTN plug ins for war, zerker, rog, Shm, Cleric and KA for Bard. The bard isn't acting this way. Not sure what's going on checked settings and don't see anything I can tell that's off.
-
You've discovered RedGuides, an EverQuest multi-boxing and scripting community 🧙♀️⚙️. We want you to play several EQ characters at once, come join us and say hello! 👋
Question - Toons bouncing around attacking
- Thread starter Thebone
- Start date
you probably have "follow me" stuck on.
you shouldn't use afollow while trying to fight
/bcga //afollow off and/or un-click your "Follow Me" buttonall of your toons should be NOT be at "min" for max background fps. this 100% can and will cause you automation issues with toons in the background, especially with things like navigation, movement, damage, spellbook, etc. you should be at least 30, with a strong encouragement to be at 60.
It is an everquest setting in your alt-o window
>>> Alt-O -> Display -> Advanced - > Max Background FPS <<<
if you have having pc performance issues, you should consider trying mq "Next" and running the frame limiter. the background "frame cycles" still occur so your automation can continue to "do work" but it makes it not get drawn and not take pc power
you can see what a low impact eq is on my cpu here
then you shouldn't have any reason to have your background fps set to min.
since i'm having this conversation with two folks at the same time :
it doesn't matter if you are using a nasa computer, if you tell your toons to "not do anything in the background" you can run into issues with "not doing stuff in the background" that is why it is in the FAQ specifically for the spell book.
as i mentioned, the frames cycle is where "work is done" so if you tell it "do as little work as possible" it is going to "do as little work as possible". which can end up resulting in less than ideal movement like navigation or afollow, or spellbook issues, or just slugging response to things.
this is a common problem people have which results in issues with all sorts of things happening in the background regardless of which macro/plugin/automation you're using for your characters.
no, frame limiter is the built-in frame limiter for mq "next"
Here are several other threads over time where folks had similar things