Bevy AI navigation

When to use

Load this when an actor must chase, patrol, or wait, and you need to see which Bevy skill owns the next step. Path data and any future nav crate stay on bevy-navigation. Transform integration stays on bevy-character-movement. Line-of-sight sensors stay on bevy-spatial-queries until a solver exists.

ECS shape

• Components: a mode flag can be an enum Component (see bevy-state-machines for the pattern). Goal position can be your own component. No agent, radius, or layer type was opened.
• Resources: a shared patrol table can be a Resource you define. No navigation resource was opened.
• Systems: read the mode and write a desired velocity or waypoint on Update or Fixed. Use .chain() so policy runs before movement. Do not name a Godot-style agent callback.
• Schedule: Fixed / FixedMain when the result feeds the movement step.

Coming from Godot