Rust Bevy State Flow

Use this skill to make Bevy states explicit and reusable. State flow should describe when systems run, what is created on entry, and what is cleaned up on exit.

Core Workflow

1. Name the user-visible game phases before adding systems.
2. Represent phases with an AppState or feature-specific state enum.
3. Put setup in OnEnter, cleanup in OnExit, and gameplay in state-filtered update schedules.
4. Mark state-owned entities with cleanup components.
5. Keep transitions event-driven or command-driven, not hidden in rendering systems.
6. Test repeated transitions to catch duplicate entities and stale resources.

Read Next