map-navigator-guide

Use a MapNavigateAction custom action with a NAVMESH path entry containing the target coordinate. The runtime plans an executable route over the triangle navmesh automatically, so no pre-recorded path is needed when the destination is reachable without interactions or map transitions.

Prefer NAVMESH whenever the target is reachable without interactions, map transitions, or special mechanisms. Fall back to a recorded path only when the route contains semantics the navigator cannot infer, such as INTERACT points, PORTAL transitions, or jump pads.

target_tier disambiguates coordinates that come from a tier-specific base map, declared as an object like { "action": "RUN", "target": [x, y], "target_tier": "Wuling_L4_328" }. It only declares the coordinate's source layer and never implies a zone switch, which remains the job of ZONE and PORTAL nodes.

The game is 3D but the base map is 2D, so corridors, bridges, and rooftops can share one target coordinate. Declare target_deck_y with the surface's world height, read from the overlapping-surface list in the MapNavigator tool, so pathfinding stops on the intended layer.

An INTERACT point with interact_text becomes asynchronous: navigation stops when the prompt appears, confirms it via OCR, then presses the key. Adding interact_rec delegates which option row to press back to the outer Pipeline, useful for multi-option interactions like accept or abandon.

The camera cannot rotate while the character is stopped, so no new minimap observations are produced and localization stalls. Any stop-turn-restart change causes deadlock; heading adjustments must be performed during movement.