boxSize and boxTolerance

[Thric3]

Can someone please explain these. I've looked around and I see that .35-.5 for boxSize and 10-20 for boxTolerance seem to be the norm.

However if I had a better understanding my profiles for Keeps 1-3 may be better served.

Also is there a way for the bot to detect walls? E.G. if the bot is within 10 yards of a wall I'd like to have him move away, because this is where 80% of the stucks come from. Thanks.

 

[Polyester]

ExploreArea
boxSize - Lets you adjust the exploration box size. See the "Map Viewer" for better details.
boxTolerance - Lets you adjust the amount of navigable area in each box for it to be considered as a visit area for the exploration.
exitNameHash - The name hash of the "exit" to take (or find) for the dungeon. Get this from the "Dump Map Markers" button.
leaveWhenFinished - True/False - Tells the bot to leave the area when it has finished exploring. Requires exitNameHash to be set.
actorId - the SNO ID of the actor to search for. Once the bot finds this actor, it will end this behavior.
until - A multi-purpose attribute to define when this behavior should stop exploring. Valid values are as follows:
"FullyExplored" - this is the default. This will end the behavior (or cause it to leave if leaveWhenFinished is defined as True) when it has fully explored the dungeon.
"ExitFound" - This will end the behavior when the exit defined by exitNameHash is found. (Optionally leave the game as well if leaveWhenFinished is defined as True)
"ObjectFound" - This will end the behavior when the specified actorId is found. The same goes for leaveWhenFinished here.

playing around with the mapviewer will give you a better understanding, also give up on your keep depths profiles. they will. not. work.

 

[rrrix]

playing around with the mapviewer will give you a better understanding, also give up on your keep depths profiles. they will. not. work.

My keep depths profiles work great. In fact all my random dungeon profiles work great.


To OP:
boxSize is the number of cells/units that will make up a navigable section of the map. boxTolerance is the percentage of boxSize that needs to be navigable in order to be considered in ExploreArea navigation.

For "inside" places like arreat crater, dungeons, sewers, spider dens and whatnot, try a boxSize of 18 and boxTolerance of 0.18, or 15/0.15 - I have found these are ideal for tight spaces.

For large open spaces like dahlgur oasis, try a boxSize of 45 and boxTolerance of 0.20, or 40/0.

Keep in mind, the smaller the box size, the slower the bot will go and the more backtracking it will have to perform. The larger the box size and higher box tolerance, the more chance of the bot not navigating to an important area (with potential elites, or dungeon exits within).

 

[Polyester]

My keep depths profiles work great. In fact all my random dungeon profiles work great.


To OP:
boxSize is the number of cells/units that will make up a navigable section of the map. boxTolerance is the percentage of boxSize that needs to be navigable in order to be considered in ExploreArea navigation.

For "inside" places like arreat crater, dungeons, sewers, spider dens and whatnot, try a boxSize of 18 and boxTolerance of 0.18, or 15/0.15 - I have found these are ideal for tight spaces.

For large open spaces like dahlgur oasis, try a boxSize of 45 and boxTolerance of 0.20, or 40/0.

Keep in mind, the smaller the box size, the slower the bot will go and the more backtracking it will have to perform. The larger the box size and higher box tolerance, the more chance of the bot not navigating to an important area (with potential elites, or dungeon exits within).

do they find the exits every time or do they explore then tp out?

 

[Thric3]

Changed my profiles to .15/15, they work perfectly now. Thanks very much.

My next projects>
- Act key prioritization. (Go to the act that you need the most keys out of first).
- Rakkis Crossing full length runs (I have it check for the door instead of just go in 100% of the time already)
- Act 2 Key run with fast elite find route.

 

[rrrix]

do they find the exits every time or do they explore then tp out?

Sometimes they don't find the exit. It's a known issue but it's easily handled within the profile to keep moving. Sucks if you're trying to do questing, but for champ hunting it's a non issue IMO.

 

[Polyester]

Sometimes they don't find the exit. It's a known issue but it's easily handled within the profile to keep moving. Sucks if you're trying to do questing, but for champ hunting it's a non issue IMO.

well we obviously have different ideas about what "working" means :|

 

[Flyingtoo]

My keep depths profiles work great. In fact all my random dungeon profiles work great.


To OP:
boxSize is the number of cells/units that will make up a navigable section of the map. boxTolerance is the percentage of boxSize that needs to be navigable in order to be considered in ExploreArea navigation.

For "inside" places like arreat crater, dungeons, sewers, spider dens and whatnot, try a boxSize of 18 and boxTolerance of 0.18, or 15/0.15 - I have found these are ideal for tight spaces.

For large open spaces like dahlgur oasis, try a boxSize of 45 and boxTolerance of 0.20, or 40/0.

Keep in mind, the smaller the box size, the slower the bot will go and the more backtracking it will have to perform. The larger the box size and higher box tolerance, the more chance of the bot not navigating to an important area (with potential elites, or dungeon exits within).

Thank you so much. This helped me with my profile immensely.