Botting at multiple places / different waypoint files ???

[d003232]

I want to discuss the idee and points about botting with multi waypoint files. As discussed in different posts, there is the possibility to connect waypoint files together and so change the places where the bot works.

It goes like:

We run from the start point to area 1:

Code: Select all

<waypoints type="TRAVEL" >
	<!-- # 3 --><waypoint x="-3779" z="-8480"></waypoint>
	<!-- # 4 --><waypoint x="-3654" z="-8639"></waypoint>
	    __WPL:load(getExecutionPath() .. "/waypoints/l2-3_woelfe.xml");
	    __WPL:setWaypointIndex(__WPL:getNearestWaypoint(player.X, player.Z));
	</waypoint>
</waypoints>

then we start there botting:

Code: Select all

<waypoints type="NORMAL" >
	<!-- # 1 --><waypoint x="-2206" z="-9648"></waypoint>
	<!-- #14 --><waypoint x="-1931" z="-9750">
		if( player.Level > 4 ) then
			__WPL:load(getExecutionPath() .. "/waypoints/l5_goto_5_kaefer.xml");
	    		__WPL:setWaypointIndex(__WPL:getNearestWaypoint(player.X, player.Z));
	  	end	
	</waypoint>
</waypoints>

if we reach LvL 4 we load the next waypoint file and change place again. By doing it that way, you can level a character from LvL 1 to 10 and run to Varanas without big break.

And so on. By doint that, there are some issues:

• if you stop the bot or lost connection, you have to change the profile or call the bot with the profile of that place, where you are standing now. Thats complicated
• If you die, you need also different returnpath files
• You have to open ingame the gift bags to get enough hp and mana poitions
• you have to learn ingame the next level of you main damage skills

I could imaging, to start botting with a list of waypoint files. And the bot will look, what's the closest waypoint file and start with that file ... or with that return path file. But I don't see solutions for the other, for the ingame points.

Does anyone have issues or ideas about that? Any more 'problems'?

[Administrator]

The problem here is that many people will want many different things. Some will want it to be based on what is the closest location, others depending on what level they are, some want a random selection, and others what class they are, etc. With so many possibilities, it isn't an easy fix.

I guess one thing that could be done is to add a script tag to the profile that is used when the profile is loaded. This would not take care of changes that happen during runtime, only when loading. Simply enough, it would just run a snippet of Lua code.

Code: Select all

<script>
  if( player.Level > 15 ) then
    __WPL:load(getExecutionPath() .. "/waypoints/level15wp.xml");
    __RPL:load(getExecutionPath() .. "/waypoints/level15ret.xml");
  elseif( player.Level > 10 ) then
    __WPL:load(getExecutionPath() .. "/waypoints/level10wp.xml");
    __RPL:load(getExecutionPath() .. "/waypoints/level10ret.xml");
  else
    __WPL:load(getExecutionPath() .. "/waypoints/level1wp.xml");
    __RPL:load(getExecutionPath() .. "/waypoints/level1ret.xml");
  end
</script>

Another thing that could be done would be an extension of the waypoints option.

Code: Select all

<option name="WAYPOINTS" value="10_to_15.xml" conditionType="level" conditionMin="10" conditionMax="15" />
<option name="WAYPOINTS" value="1_to_9.xml" conditionType="level" conditionMin="1" conditionMax="9" />
<option name="WAYPOINTS" value="myPriest.xml" conditionType="class" conditionValue="priest" />

The problem with this is that you cannot mix and match conditions (as shown above). You can only have a waypoint list selected by level or class; not both. Plus, this means constantly updating the code based on what every person would like to use.