Bill D Cat wrote: I was thinking of adding an optional third arg to the loadPaths() function that would contain either the waypoint number or a waypoint tag to resume at.
Even though it might be easy to implement, I'm not sure I like the idea. It seems to me you are saying, normally the "second file" will start from the closest waypoint but when coming from the "first file" you want it to start from the DailyDone tag. But the thing I don't like its it returns to the "First file" regardless. So to me that doesn't really make sense. If the "second file" is only meant to be used with the "first file" then you can add code in the onload to make it start from the correct waypoint as usual. Maybe I'm missing something. I haven't read the split posts yet.
lisa wrote:Something along these lines.
pathingtable = {cot ="at",at="gotoheff",gotoheff="heffdaily",heffdaily="cot"}
in another profile you might have
pathingtable = {cot ="gotoheff",gotoheff="heffdaily",heffdaily="cot"}
That's a great idea. It's sort of like a more compact version of the idea I posted about controling the order of waypoint files.
lisa wrote:As for when you crash and want to continue on from where you left off, Rock did a lot of work on that stuff, he would be best to comment about what bot currently does and ways to use that or improve it.
I suspect something was asked about this in one of the split posts. I'll answer it when I see it.
lisa wrote:not sure if there is an easy function to find the tag, there probably is but it would look in current wp file as opposed to the loaded wp file.
I'm not sure but you might be able to set the waypoint number after loading the file, eg.
Code: Select all
loadPaths("FirstWaypointNamel")
__WPL:setWaypointIndex(__WPL:findWaypointTag("TagName"))