DPB2Class · Navigation

ExilePather

Query routes and path distances in the current area. Route calculation and issuing movement commands are separate operations.

Namespace: DreamPoeBot.Loki.Bot.Pathfinding

public static class ExilePather
Reference: DPB2 0.4.5.103Compare the DPB1 reference → Check signatures and usage notes separately; a matching type is not a compatibility guarantee.

Members and overloads

1 declared here
Show all members

BlockTriggerableBlockages

MethodLink ↗
public static void ExilePather.BlockTriggerableBlockages(ref byte[] data, int bytesPerRow, Func<NetworkObject, bool> shouldBlock, List<NetworkObject> obj)

Applies a blockage's observed closed clearance (predicate true) or restores its open clearance (predicate false). Does not open or close the object in the game or turn surrounding walls into walkable cells. Empty bounds contain no cells and are ignored without interrupting the remaining objects.

Return type: voidNo return value.

Parameters

data
Parameter type: byte[]No current DPB page is linked for this built-in, external, generic or compatibility-only type.

Walkability data buffer to modify.

bytesPerRow
Parameter type: intNo current DPB page is linked for this built-in, external, generic or compatibility-only type.

Row stride in bytes for data.

shouldBlock
Parameter type: Func<NetworkObject, bool>

Predicate indicating whether a blockage should be applied for a given object.

obj
Parameter type: List<NetworkObject>

Objects whose triggerable blockage components supply the overlay.

No dedicated example has been reviewed for this member. Browse the class reference; its examples may demonstrate other operations.

Guides using this class

These guides refer to ExilePather as a whole and may use other members. They are not dedicated examples of the selected member.

See how these APIs fit together. Labs include complete source; the FollowBot walkthrough teaches you to build your own bot from selected fragments and checkpoints.

DPB2 0.4.5.103 · Reference reviewed 2026-10-30. Descriptions use source summaries where available, otherwise concise signature-based descriptions. Examples illustrate usage; they are not a live-game test.