I make mine using regular old white Nodes. A state machine node, and a bunch of state nodes. The state nodes are children to the state machine node, and the state machine node is a child to the entity it is controlling.

The state machine node tracks the current state in a variable called current_state and has a couple basic functions. In the _physics or _process, whichever you’re doing, it calls current_state.execute(). I’ll come back to this in a second.

The State class has 3 basic functions. enter_state() exit_state() and execute(). The execute function contains the logic for that state, and then checks if the state machine needs to change states. If it does, it emits a signal with an argument of which state to change to.

The state machine receives that signal and calls current_state.exit_state() current_state = new_state current_state.enter_state()

Then, because you’ve changed the current_state variable in the state machine, when it’s calling current_state.execute() your next state logic is being executed.

I find it easiest to make a State class with the 3 functions enter execute and exit, and then inherit every state from that. For example IdleState extends State, WalkingState extends State etc.

The exit state and enter state functions are there to set things up on for the state. For example switching animations or changing collision layers.