Page 1 of 1

Is language[15] still usefull?

Posted: Sun Nov 23, 2014 1:20 pm
by Bill D Cat

Code: Select all

	[15] = "Waypoint #%d is closer then #1. Hence we start with waypoint #%d.\n",
Referenced in functions.lua around line 650.

I was playing around with some of my older waypoint scripts and noticed that this was still in the bot. With the implementation of the resume feature, I was curious if this was still a useful feature to have in the bot. Most of my waypoint files now start with this code in the <onload> section.

Code: Select all

	<onload>
		if not __WPL.ResumePoint then
			__WPL:setWaypointIndex(1)
		end
	</onload>
If this code wasn't present, the bot would be trying to start a waypoint file somewhere in the middle even if the resume option wasn't selected from the menu. Most noticeable to me are my Elven Island and Yrvandis Hollows waypoint series. Is there any other reason to start a waypoint file somewhere in the middle of it without explicitly using the resume feature?

Re: Is language[15] still usefull?

Posted: Sun Nov 23, 2014 2:19 pm
by BlubBlab
I'm not sure I don't know much about the resume function but in theory it allow you to start the script somewhere else along the road which can go crazy when you have a (one)script with multiply zones.

Because of this I want to add in my DP bot not only xyz but also the zone.

Re: Is language[15] still usefull?

Posted: Sun Nov 23, 2014 9:11 pm
by rock5
Using the resume option is optional. By default the bot finds the nearest waypoint to start from. So it can be resumed if stopped in the middle of a script. This is by design.

The purpose of the resume feature is for waypoints that crisscross over itself that might resume from the wrong waypoint when you need it to resume from the right one. Probably most waypoint files either don't crisscross or it doesn't matter which waypoint it resumes from, so the old feature is still very useful. It's mainly for chained complex waypoint files, such as your Elven Island and Yrvandis Hollow series, that the resume feature is needed.