Modularity. Splitting the player into its “moves” and move them out as separate scenes

[wchc]

There are multiple ways how you can approach designing your State Machine, there is no “one solution fits all”. Just to name a few most popular ones:

1. You can have states as enums within the same script.
2. You can have states as Resources with the state logic delegated to each Resource script separately.
3. You can have states as Nodes and rip the additional benefits of being able to see them easily in the scene tree.

Here’s an interesting discussion about Resource vs Node based State Machines.

Resource based state machine example

Godot Version v4.5.1.stable.mono.official [state machine example] Introduction Hello! In my current project, I reached the point where I needed to make the state machine. I began doing some researches on how to make one and all the tutorials were awful but in the end I kind of understood how it works. I thought of re-designing the usual way that it’s made in most projects (i think it’s called “node based state machine”) which i thought was very bad the way they did it, or rather t…

Here’s another discussion about a completely different approach that does not use states at all, although this idea is less refined than a traditional State Machine yet.

Modular Character Controller (v4.4-4.6)

Hi everyone, I’d like to share with you my Modular Character Controller. It’s a project I have been working on and is a set of scripts for making characters in your Godot games do the things they should. This applies to player characters, any NPCs, and even vehicles. I just released a major update for it that includes ways for much better control over the actions a character can make. Its available in a few places and can be used as a plugin or a project if you want to see the demo characters. …

I’ll let you draw your own conclusions.

EDIT:
I forgot, there are also State Charts, worth considering:

GitHub - derkork/godot-statecharts: A state charts extension for Godot 4