Pathing questions

[zipyzen]

Hello. this is my first post. I have been experimenting with the harvest bot for a while and have gotten it to work sufficiently, but i been having trouble making correct paths to use with eq2bot.
I use eq2pather combat and the dungeon crawl seems to stop when it hits the end. So i cant leave in on long unless its a long path. Not sure if theres a way to loop the path like in the harvest. So i been trying to make a good path for the small camp/pull setting. Im not sure exactly how this setting works. Can you have multiple camps with thier own pull spots, or just ONE camp? and would it pull to the nearest camp, or run all the way back to the first?

I play a necromancer. and was also wondering if anyone knew exactly why eq2bot doesnt load the settings properly for my character when i have cirtain things checked. It will not let me hit start on the eq2bot when this happens. I sometimes have to delete the xml and start a new one when things like auto loot are checked. It seems to happen on multiple class scripts for me.

sorry for the long post, but any help would be nice. TY

 

[abbadon]

pather/eq2bot

I have had the exact same problems in the past. I would check harvest playing around and then I was stuck until I deleted my xml file. I also had issues where things didn't seem to work the way they should and whole tabs would no appear in eq2bot. I don't know what it was on my end but I made a backup copy of my current scripts directory, blew it away and reloaded the package put together by ama and all of my problems went away. I would go so far to say as scripts I thought had been broken since inception now work flawlessly. Any remnant (paths etc) that I needed I just copied over one at a time to make sure they didn't cause the problems in the first place.

That is what I would do. Worst case scenario is you blow it away and restore your backup script directory.

Abbadon

 

[Pygar]

There is a bug running in continuous loop where the bot reaches the end point then tries to run to the start point directly without following the stream of points back.

In general the bot runs around bouncing into walls for 45 seconds, realizes its stuck, calls its stuck routine and moves to the nearest point in the path and resumes its trek through waypoints back to start.

Some agree with me this bug exists, others don't, but I've tried every variant possible, and I get the same result everytime.

It does sound to me though that you have it set to run start to end, and not continuous loop. Setting start to end is the desired results you are experiencing.

Good luck