What's new
  • Visit Rebornbuddy
  • Visit Panda Profiles
  • Visit LLamamMagic
  • Visit Resources
  • Visit Downloads
  • Visit Portal

[Suggestion] Adding path element to profile

awww

New Member
Joined
Oct 4, 2012
Messages
33
Reaction score
0
Hi all,
I'm new to DB. After setting up and running my bot for a while, I got some suggestion for the pathing in profile.
Some MoveTo elements in the profiles are simply to make sure we cleared everything in the map; they are not the main path. When my bot dies, it will go back using the same path, going in that corner, then back out again. So is it too much trouble if we can set some path to be "mandatory" (the main path) and others just need to go once?
So instead of
Code:
			<MoveTo questId="1" x="1140.686" y="732.1945" z="0.1000002" pathPrecision="10" />
			<MoveTo questId="1" x="1081.564" y="715.2292" z="0.09999999" pathPrecision="10" />
			<MoveTo questId="1" x="991.7961" y="728.0093" z="0.1000001" pathPrecision="10" />
			<MoveTo questId="1" x="885.3837" y="717.8165" z="0.1000153" pathPrecision="10" />
			<MoveTo questId="1" x="775.1333" y="627.4221" z="0.1000157" pathPrecision="10" />
			<MoveTo questId="1" x="737.8298" y="549.946" z="0.1000217" pathPrecision="10" />
			<MoveTo questId="1" x="591.9153" y="550.4387" z="0.1000032" pathPrecision="10" />
			<MoveTo questId="1" x="548.8901" y="651.1499" z="0.1000153" pathPrecision="10" />
			<MoveTo questId="1" x="544.4486" y="707.1024" z="0.529933" pathPrecision="10" />
			<MoveTo questId="1" x="336.1475" y="724.474" z="0.1" pathPrecision="10" />
			<MoveTo questId="1" x="156.8677" y="719.1554" z="-51.6376" pathPrecision="10" />
we have
Code:
<Path mandatory="True">
			<MoveTo questId="1" x="1140.686" y="732.1945" z="0.1000002" pathPrecision="10" />
			<MoveTo questId="1" x="1081.564" y="715.2292" z="0.09999999" pathPrecision="10" />
			<MoveTo questId="1" x="991.7961" y="728.0093" z="0.1000001" pathPrecision="10" />
			<MoveTo questId="1" x="885.3837" y="717.8165" z="0.1000153" pathPrecision="10" />
</Path>
<Path mandatory="False" backtrack="True">
			<MoveTo questId="1" x="775.1333" y="627.4221" z="0.1000157" pathPrecision="10" />
			<MoveTo questId="1" x="737.8298" y="549.946" z="0.1000217" pathPrecision="10" />
			<MoveTo questId="1" x="591.9153" y="550.4387" z="0.1000032" pathPrecision="10" />
			<MoveTo questId="1" x="548.8901" y="651.1499" z="0.1000153" pathPrecision="10" />
</Path>
<Path mandatory="False">
			<MoveTo questId="1" x="544.4486" y="707.1024" z="0.529933" pathPrecision="10" />
			<MoveTo questId="1" x="336.1475" y="724.474" z="0.1" pathPrecision="10" />
			<MoveTo questId="1" x="156.8677" y="719.1554" z="-51.6376" pathPrecision="10" />
</Path>

So if a path is not mandatory, once it is done, it can be removed during that run. If the bot dies, it only need to run the main paths.

The "backtrack" is just for the profile maker's convenience: If a path is "backtrack", once the bot runs it, it will run that path again backward. So the profile maker only needs to specify "go in", and the bot can still know the way out (back to main path).

Any path will default to mandatory="True" backtrack="False" if not specify.

What do you guys think?
 
Last edited:
Hi all,
I'm new to DB. After setting up and running my bot for a while, I got some suggestion for the pathing in profile.
Some MoveTo elements in the profiles are simply to make sure we cleared everything in the map; they are not the main path. When my bot dies, it will go back using the same path, going in that corner, then back out again. So is it too much trouble if we can set some path to be "mandatory" (the main path) and others just need to go once?
So instead of
Code:
            <MoveTo questId="1" x="1140.686" y="732.1945" z="0.1000002" pathPrecision="10" />
            <MoveTo questId="1" x="1081.564" y="715.2292" z="0.09999999" pathPrecision="10" />
            <MoveTo questId="1" x="991.7961" y="728.0093" z="0.1000001" pathPrecision="10" />
            <MoveTo questId="1" x="885.3837" y="717.8165" z="0.1000153" pathPrecision="10" />
            <MoveTo questId="1" x="775.1333" y="627.4221" z="0.1000157" pathPrecision="10" />
            <MoveTo questId="1" x="737.8298" y="549.946" z="0.1000217" pathPrecision="10" />
            <MoveTo questId="1" x="591.9153" y="550.4387" z="0.1000032" pathPrecision="10" />
            <MoveTo questId="1" x="548.8901" y="651.1499" z="0.1000153" pathPrecision="10" />
            <MoveTo questId="1" x="544.4486" y="707.1024" z="0.529933" pathPrecision="10" />
            <MoveTo questId="1" x="336.1475" y="724.474" z="0.1" pathPrecision="10" />
            <MoveTo questId="1" x="156.8677" y="719.1554" z="-51.6376" pathPrecision="10" />
we have
Code:
<Path mandatory="True">
            <MoveTo questId="1" x="1140.686" y="732.1945" z="0.1000002" pathPrecision="10" />
            <MoveTo questId="1" x="1081.564" y="715.2292" z="0.09999999" pathPrecision="10" />
            <MoveTo questId="1" x="991.7961" y="728.0093" z="0.1000001" pathPrecision="10" />
            <MoveTo questId="1" x="885.3837" y="717.8165" z="0.1000153" pathPrecision="10" />
</Path>
<Path mandatory="False" backtrack="True">
            <MoveTo questId="1" x="775.1333" y="627.4221" z="0.1000157" pathPrecision="10" />
            <MoveTo questId="1" x="737.8298" y="549.946" z="0.1000217" pathPrecision="10" />
            <MoveTo questId="1" x="591.9153" y="550.4387" z="0.1000032" pathPrecision="10" />
            <MoveTo questId="1" x="548.8901" y="651.1499" z="0.1000153" pathPrecision="10" />
</Path>
<Path mandatory="False">
            <MoveTo questId="1" x="544.4486" y="707.1024" z="0.529933" pathPrecision="10" />
            <MoveTo questId="1" x="336.1475" y="724.474" z="0.1" pathPrecision="10" />
            <MoveTo questId="1" x="156.8677" y="719.1554" z="-51.6376" pathPrecision="10" />
</Path>

So if a path is not mandatory, once it is done, it can be removed during that run. If the bot dies, it only need to run the main paths.

The "backtrack" is just for the profile maker's convenience: If a path is "backtrack", once the bot runs it, it will run that path again backward. So the profile maker only needs to specify "go in", and the bot can still know the way out (back to main path).

Any path will default to mandatory="True" backtrack="False" if not specify.

What do you guys think?

If this was implemented it'll cut the time for bot to run back after dying.. then again most people here do have 24% MSped so it wont matter, though i for one would like to see this as well so it can carry on with botting efficiency
 
Hi all,
I'm new to DB. After setting up and running my bot for a while, I got some suggestion for the pathing in profile.
Some MoveTo elements in the profiles are simply to make sure we cleared everything in the map; they are not the main path. When my bot dies, it will go back using the same path, going in that corner, then back out again. So is it too much trouble if we can set some path to be "mandatory" (the main path) and others just need to go once?
So instead of
Code:
			<MoveTo questId="1" x="1140.686" y="732.1945" z="0.1000002" pathPrecision="10" />
			<MoveTo questId="1" x="1081.564" y="715.2292" z="0.09999999" pathPrecision="10" />
			<MoveTo questId="1" x="991.7961" y="728.0093" z="0.1000001" pathPrecision="10" />
			<MoveTo questId="1" x="885.3837" y="717.8165" z="0.1000153" pathPrecision="10" />
			<MoveTo questId="1" x="775.1333" y="627.4221" z="0.1000157" pathPrecision="10" />
			<MoveTo questId="1" x="737.8298" y="549.946" z="0.1000217" pathPrecision="10" />
			<MoveTo questId="1" x="591.9153" y="550.4387" z="0.1000032" pathPrecision="10" />
			<MoveTo questId="1" x="548.8901" y="651.1499" z="0.1000153" pathPrecision="10" />
			<MoveTo questId="1" x="544.4486" y="707.1024" z="0.529933" pathPrecision="10" />
			<MoveTo questId="1" x="336.1475" y="724.474" z="0.1" pathPrecision="10" />
			<MoveTo questId="1" x="156.8677" y="719.1554" z="-51.6376" pathPrecision="10" />
we have
Code:
<Path mandatory="True">
			<MoveTo questId="1" x="1140.686" y="732.1945" z="0.1000002" pathPrecision="10" />
			<MoveTo questId="1" x="1081.564" y="715.2292" z="0.09999999" pathPrecision="10" />
			<MoveTo questId="1" x="991.7961" y="728.0093" z="0.1000001" pathPrecision="10" />
			<MoveTo questId="1" x="885.3837" y="717.8165" z="0.1000153" pathPrecision="10" />
</Path>
<Path mandatory="False" backtrack="True">
			<MoveTo questId="1" x="775.1333" y="627.4221" z="0.1000157" pathPrecision="10" />
			<MoveTo questId="1" x="737.8298" y="549.946" z="0.1000217" pathPrecision="10" />
			<MoveTo questId="1" x="591.9153" y="550.4387" z="0.1000032" pathPrecision="10" />
			<MoveTo questId="1" x="548.8901" y="651.1499" z="0.1000153" pathPrecision="10" />
</Path>
<Path mandatory="False">
			<MoveTo questId="1" x="544.4486" y="707.1024" z="0.529933" pathPrecision="10" />
			<MoveTo questId="1" x="336.1475" y="724.474" z="0.1" pathPrecision="10" />
			<MoveTo questId="1" x="156.8677" y="719.1554" z="-51.6376" pathPrecision="10" />
</Path>

So if a path is not mandatory, once it is done, it can be removed during that run. If the bot dies, it only need to run the main paths.

The "backtrack" is just for the profile maker's convenience: If a path is "backtrack", once the bot runs it, it will run that path again backward. So the profile maker only needs to specify "go in", and the bot can still know the way out (back to main path).

Any path will default to mandatory="True" backtrack="False" if not specify.

What do you guys think?

I think you make it more complicated and not ease for script. Just make a new profiles tag <CheckPoint> whenever bot died and start from the last check point. It's not hard for the logic to achieve as i expect.
 
Back
Top