Ok, to start, I get EQ2Bot to work fine when I set it to home point or when I set up a camp and pullpoint that are the same. Both seem to work similarly and other than awaiting respawns within a small range it works. I do have to limit scan range to within pull distance of 35 for my spell because the bot will target something out of pull range (say 40-50) away an try as he may attempt to pull, getting target out of ranges over and over occasionally. It will give up after a couple tries sometimes if something else appears nearby. Seems something is wrong in the move to pull range...wherever that is.
The real problem is when I setup a camp and multiple pull points or a single camp with a long path to a pull point. The character will pull everything within range of the nearest camp and sometimes follow a ways toward a pull point but will eventually run dry of spawns. Once this happens it will just stop and await spawns. Sometimes this will trigger it to wander to a pull point, but usually not. It gets in that spawn loop and stays. I've never had it successfully run from waypoint to waypoint like one would assume and pulling everything within range then moving to the next waypoint.
The third issue is that sometimes the bot will think it has something targeted and attempt to pull, but there is nothing there resulting in No Eligible Target errors, how hard is it to impliment a rescan for targets if that error is seen? I see can't see target and out of range coded into the pull routines(not that it ever strafes or anything to attempt a repull, but I digress)...is chat analysis broken too?
Last night I setup the bot and it gained 20% experience, the rest of the night it sat there attempting to cast on an imaginary target...for 4 or 5 hours.
The real problem is when I setup a camp and multiple pull points or a single camp with a long path to a pull point. The character will pull everything within range of the nearest camp and sometimes follow a ways toward a pull point but will eventually run dry of spawns. Once this happens it will just stop and await spawns. Sometimes this will trigger it to wander to a pull point, but usually not. It gets in that spawn loop and stays. I've never had it successfully run from waypoint to waypoint like one would assume and pulling everything within range then moving to the next waypoint.
The third issue is that sometimes the bot will think it has something targeted and attempt to pull, but there is nothing there resulting in No Eligible Target errors, how hard is it to impliment a rescan for targets if that error is seen? I see can't see target and out of range coded into the pull routines(not that it ever strafes or anything to attempt a repull, but I digress)...is chat analysis broken too?
Last night I setup the bot and it gained 20% experience, the rest of the night it sat there attempting to cast on an imaginary target...for 4 or 5 hours.
Last edited:
