SolarStrike Software

rock5 wrote:1. You could just use createpath and then extract the coordinates. The table the function expects would look something like this.

• table = {
  • {X=1,Z=1},
    {X=2,Z=2},
    {X=1,Z=2},
  }

2. Well, to be REALLY thorough you could do areas for every room and even the corridors if you want but most likely you would just do the difficult rooms and reduce the MAX_COMBAT_DIST a little for easier parts. This method would never be as easy as changing profile options but would yeild better results. So it's up to the user to decide if a certain problem would be best solved by using this method.

3. Not sure. The bot already fights back when aggroing a mob that doesn't pass the default eval function so this should be no exception. It should fight back without any extra work. I'm pretty sure that the bot executes code from passed waypoints so that shouldn't be an issue. The only check I can think of that really needs to be done is to check if the target area is very far away, such as when the user forgets to clear it before moving away or teleporting. Then it should ignore it I think. Or maybe that will intoduce too much needless processing, I'm not sure.

It should be easy to implement. Just have a function to modify the "killzone" table and a check in the eval function

Code: Select all

if killzone then
    if not pnpoly(killzone,target.X,target.Z) then
        return false
    end
end

It could be as simple as that.

rock5 wrote:Ok I'll look into adding it. I have a few decisions to be made.

I'm looking to add 2 functions for this, the pnpoly function and one to set the killzone table.

1. Should the name of pnpoly remain "pnpoly", maybe as a nod to the original author, or should we rename it to something clearer? What should it be named? Maybe "PointInPoly"?
2. Should it be a global function or local? I'm thinking there could be future uses for it so it should be global.

I like the word "killzone" so I thought I'd use it in the "set" function, maybe "SetKillZone(_table)"?

I just had another idea. Maybe we could have SetKillZone accept waypoint files as well. So instead of using createpath to create a temporary waypoint file to extract the coordinates to use with SetKillZone, you could name it KSroom1.xml and then do

Code: Select all

SetKillZone("KSroom1")

So it could accept a table or a waypoint file. How does that sound?

BillDoorNZ wrote:would also act as an extension point later on in case anything else needed to be done at the same time.

rock5 wrote:Ok that's all good but I'm not sure what you mean by this

BillDoorNZ wrote:would also act as an extension point later on in case anything else needed to be done at the same time.

I'm adding a "GetKillZone" function too.

BillDoorNZ wrote:What I meant by this is that if later you find there is a need to do other stuff when clearing out the killzone poly, then you will already have a function in place (that should be the only way that people clear our the killzone) that you can 'extend'/'modify' to add to.

	if _zone == nil or _zone == "" or (type(_zone) == "table" and #_zone == 0) then
		self.KillZone = {}
		return
	end

rock5 wrote:

BillDoorNZ wrote:What I meant by this is that if later you find there is a need to do other stuff when clearing out the killzone poly, then you will already have a function in place (that should be the only way that people clear our the killzone) that you can 'extend'/'modify' to add to.

I think I see what you mean but I don't think ClearKillZone should ever have anything but SetKillZone(nil) in it. Any code you want to do when clearing the killzone table should be placed in SetKillZone. After all, people might still use SetKillZone(nil) or whatever and you don't want them to miss out on any necessary code. At the moment there is a section in SetKillZone that looks like this

Code: Select all

	if _zone == nil or _zone == "" or (type(_zone) == "table" and #_zone == 0) then
		self.KillZone = {}
		return
	end

We could always add extra code in there if we wanted.

<?xml version="1.0" encoding="utf-8"?><waypoints>
<onLoad>
	quest_Id=422580;
	quest = __QL:getQuestById(quest_Id); --__QL is a QuestList class that loads the quests from a database
	quest:update(); --asks ROM for updated info on quest

	quest_oldTargets = settings.profile.mobs;
	quest_oldFriends = settings.profile.friends;
	settings.profile.mobs = {};
	settings.profile.friends = {};
	Friends_Add(GetIdName(102253)); --skippers
	Mobs_Add(GetIdName(102257)); --bear
	
	printf("Starting waypoint for Quest: "..quest.Name.." ("..tostring(quest.Id)..")\n");
	redirectToWaypointTag("start");
</onLoad>
<onUnload>
	settings.profile.mobs = quest_oldTargets;
	settings.profile.friends = quest_oldFriends;
</onUnload>
	<!-- #   0 --><waypoint x="6268" z="21125" y="173" tag="start">
		PickupQuestIfIDontHaveIt(quest); -- if I don't have hte quest, then target the npc, talk to them and get the quest.
		
		TurnInQuestIfComplete(quest); -- if quest is complete (same turn in npc as starter npc) then hand it in
		if (quest.Completed) then
			redirectToWaypointTag("finish"); -- I have to have a finish tag to skip the looping and revert back to my wander waypoint - my code assumes that at last waypoint = finished
		end;
</waypoint>
	<!-- #   1 --><waypoint x="6430" z="21088" y="181"></waypoint>
	<!-- #   2 --><waypoint x="6435" z="20977" y="194"></waypoint>
	<!-- #   3 --><waypoint x="6494" z="20987" y="197"></waypoint>
	<!-- #   4 --><waypoint x="6549" z="21133" y="182"></waypoint>
	<!-- #   5 --><waypoint x="6536" z="21195" y="181"></waypoint>
	<!-- #   6 --><waypoint x="6621" z="21220" y="183"></waypoint>
	<!-- #   7 --><waypoint x="6730" z="21331" y="218"></waypoint>
	<!-- #   8 --><waypoint x="6794" z="21496" y="219"></waypoint>
	<!-- #   9 --><waypoint x="6792" z="21608" y="222"></waypoint>
	<!-- #  10 --><waypoint x="6735" z="21580" y="218"></waypoint>
	<!-- #  11 --><waypoint x="6688" z="21463" y="221"></waypoint>
	<!-- #  12 --><waypoint x="6609" z="21386" y="215"></waypoint>
	<!-- #  13 --><waypoint x="6350" z="21345" y="165"></waypoint>
	<!-- #  14 --><waypoint x="6223" z="21263" y="159"></waypoint>
	<!-- #  15 --><waypoint x="6140" z="21169" y="169">redirectToWaypointTag("start");</waypoint>
	<!-- #  16 --><waypoint x="6256" z="21098" y="175" tag="finish"></waypoint>
</waypoints>

BillDoorNZ wrote:Was thinking about it more last night, might be worth adding a second option to turn the killzone into a exclude_killzone so that the bot will run around and kill anything NOT in the killzone

savvoulis_21 wrote:i have a problem with the waypoint!! when it finishes the run and go to sell the items, it doesnt sell them instead it buys items! plz help me!

		<!-- Auto selling options when used with player:merchant -->
		<option name="INV_AUTOSELL_ENABLE"	value="true" />		<!-- true | false -->
		<option name="INV_AUTOSELL_FROMSLOT" value="15" /> 			<!-- 1 = bag 1 slot 1 -->
		<option name="INV_AUTOSELL_TOSLOT"	value="180" /> 			<!-- 30 = last slot bag 1 -->
		<option name="INV_AUTOSELL_QUALITY"	value="white,green,blue" /> 	<!-- white,green,blue,purple  -->