godot-navmesh-pathing-4-6

Godot 4.6 enemies stand still when spawned because the editor-baked navmesh is empty or the navigation map has not synced. You must explicitly bake the level-root navmesh at runtime and force the navigation map to update so agents can path immediately.

To bake a navigation mesh at runtime in Godot 4.6, call the navmesh baking function inside the level's `_ready()` method using the level root as the source geometry. This avoids the empty editor-bake trap and ensures the mesh is available for NavigationAgent3D.

NavigationAgent3D reports path finished on frame one due to spawn-frame pathing races. Fix this by forcing the navigation map to update after baking, or by deferring the first destination assignment so the agent queries the mesh after it is fully committed.

To preserve navigation velocity when a base entity owns `_physics_process`, apply FSM-before-move update ordering. This ensures the entity's state machine updates the agent's target before movement is applied, preventing knockback or shove logic from overwriting nav velocity.

The best way to handle off-mesh destinations in Godot enemy pathing is destination snapping. You snap the target position to the closest point on the navigation mesh, ensuring the agent has a valid reachable path instead of freezing when the target misses the mesh.