uw-state-machine

Asynchronous state machines for Unity game flow are structured using an IState or IUpdatableState interface alongside a StateMachine orchestrator. This ensures a single active state and supports clean transitions from menu to gameplay to game over.

To set up a Unity state machine for character behaviors and UI screen flows, define states using IState, wire them into a reusable StateMachine, and apply practical patterns for transitions like Idle/Run/Jump or menu navigation.

You do not strictly need dependency injection to use state machines in your Unity project. The Skill provides clear guidance for both DI-first integration via uw-dependency-injection and ScriptableObject-first integration defined in ProjectConfig.yaml.

Handling cleanup and cancellation tokens during Unity game state transitions is managed through built-in best practices for asynchronous operations. The StateMachine orchestrator ensures previous states are properly cleaned up before activating new ones.

Errors when rapidly switching Unity UI screens are prevented by the StateMachine's enforcement of a single active state and its asynchronous transition handling. Proper use of cancellation tokens ensures safe state lifecycle management during overlapping requests.

Yes, you can use this state machine approach for AI behaviors in Unity. The interface-driven IState and IUpdatableState definitions support complex AI state transitions alongside standard game flow and UI screen management.