Concern about moveto.iss

godfetish

Active Member
In the obstacle function is being called from within moveto with the premise that the integer fed in indicates the number of failed attempts thus far in reaching your destination, but when you look at the function the integer received is used as the delay for timing issues which should probably be a constant the user needs to edit if they have lag or something absurd.

This is causing infinite loops when the character is stuck while harvesting and probably other situations.

ie the pathing routine in eq2harvest has a do while the node exists, it expects to either harvest the node or declare the node bad. I contend that it is never deeming it bad because of some coding error between versions. I know it used to set bad nodes after a few attempts...now it is just bouncing against a wall forever...

Yes, I made a video...4 minutes straight of bang, strafe, bang, strafe, bang...it tries so much that it actually gets stuck and I think the LavNAV portion finally quits the harvesting and logs the character out.

I would fix it myself, but I don't know what else relies on this single little script!

Anyway, would the powers that be tend to this please?

gf
 

godfetish

Active Member
Looking at it again, I see failedattempts is getting incremented after the call to obstacle in main...and the bot actually comes up and says Stuck in the info panel on the main tab. Maybe the fault is in the harvest bot and it is not recognizing the return STUCK compared to return "STUCK"...anyway, something is buggered up. Even setting the moveto lines in harvest to only 1 attempt is having the bot bounce against walls when something is on the other side.

gf
 

Valerian

ISX Specialist
nice. feel free to fix it. eq2harvest is currently unsupported by anyone, nobody works on it, but if you'd like to volunteer, more power to you.

as far as moveto.iss, I think eq2harvest and goharvest are the only two scripts still using it.

EDIT: I see eq2bot still includes it, not sure why. Also used by (deprecated) getrecipes and recipedata, and (of course) eq2harvestpath and eq2patherlegacy. I'll look into eq2bot to see just why we're still using it.

EDIT2: EQ2Bot no longer uses anything moveto provides. I am removing the include.
 
Last edited:

Valerian

ISX Specialist
Make sure you update from svn before submitting anything, I added some comments near the top that I'd like to keep there
 

Valerian

ISX Specialist
eq2bot doesn't use those definitions anymore, and there's a new system in place for "optional" movement key definitions which won't get patched over.
 
Top Bottom