Evergreen · Researched November 9, 2026 (UTC) · AI-assisted writing. Sources: Pathfinding and Path reference.
Quick answer
When a route stops working, distinguish failed computation from a later blockage. Path.Blocked can also report obstacles behind the character: it does not always mean the character should stop.
Studio review
You need project access and access to its movement code.
- Enable Navigation mesh in Visualization Options to inspect traversable areas.
- After
ComputeAsync(), checkPath.Statusbefore retrieving points withGetWaypoints().NoPathis not a valid route. - In the
Blockedhandler, compareblockedWaypointIndex >= nextWaypointIndex. Recompute for a blockage on the remaining route, not the completed section.
Mistakes and checks
Creating a Path does not automatically run ComputeAsync(). If computation fails, check that the start and destination are not inside solid objects.
Checklist: valid status, ordered points and a response to an obstacle placed ahead, without restarting for one behind. This is a recommended check, not a test performed in your project.
Related reading: CreatePath parameters.


