Bevy 0.19 — input actions

When to use this skill

• Gameplay needs device-neutral, persisted, rebindable actions and prompts.
• Controllers can hot-plug/reorder or multiple players/devices share input.
• Mouse capture, focus loss, Steam Deck, or adaptive hardware needs one policy.
• Frame-scoped edges/motion must drive deterministic FixedUpdate simulation.

Gameplay consumes logical actions, never raw keys or a hard-coded controller entity. Translate Bevy's frame input into an action state once, then feed presentation and fixed simulation from that state.

Canonical pattern

Bevy updates raw input in PreUpdate inside InputSystems. Run the translator after that set so ButtonInput, Gamepad, input messages, and accumulated mouse motion represent the current frame: