-
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! 👋
Plugin - MQ2AdvPath Warp Detection
- Thread starter faiding
- Start date
i believe the intent was to ensure we didn't trigger the server side warp detection.
but ive spoken with some DBG staff about their server side detection and it is full of false positives anyhow. (my guess is between bard speed, and the teleport-ahead-AAs we all get now a days)
I prefer to use nav for zones with large hills and nonsense like GD - advpath triggers warp detection all the time there - I'll just run my tank ahead, and then do a nav id me.id "come to me" since i leave dynamic updates on, they will keep coming to me until they get there even as i move away
but ive spoken with some DBG staff about their server side detection and it is full of false positives anyhow. (my guess is between bard speed, and the teleport-ahead-AAs we all get now a days)
I prefer to use nav for zones with large hills and nonsense like GD - advpath triggers warp detection all the time there - I'll just run my tank ahead, and then do a nav id me.id "come to me" since i leave dynamic updates on, they will keep coming to me until they get there even as i move away
I don't think that's the case. I'm confident if the line was removed the plugin would work fine.
In my case, I'm boxing 19 accounts on 1 computer with the background characters set to 10 FPS. Moving that many characters through zones with bumpy terrain is an absolute nightmare. I'll probably recompile a personal copy of AdvPath at some point but I don't want to distribute/modify someone else's work.
For the sake of everyone's/my own sanity, I wrote a quick script that circumvents the issue.
To use (Needs EQBC):
/bcaa //mac following or /mac follow on characters
Use /followme command to follow
Use /stopfollow command to stop