Hugo Locurcio 2a962929f3 Update demo files for Godot 4.2.1 (#1013)		9 kuukautta sitten
..
debug	3706e3e998 Map attack to gamepad X, revise text in Finite State Machine demo (#937)	1 vuosi sitten
fonts	e03d6abbc8 Update finite state machine demo for 4.0.rc4 (#850)	1 vuosi sitten
player	e03d6abbc8 Update finite state machine demo for 4.0.rc4 (#850)	1 vuosi sitten
screenshots	fcc7d5c723 Optimize PNG images using oxipng	4 vuotta sitten
state_machine	e03d6abbc8 Update finite state machine demo for 4.0.rc4 (#850)	1 vuosi sitten
Demo.tscn	3706e3e998 Map attack to gamepad X, revise text in Finite State Machine demo (#937)	1 vuosi sitten
README.md	e03d6abbc8 Update finite state machine demo for 4.0.rc4 (#850)	1 vuosi sitten
icon.webp	63d1cd9a60 Use 128×128 WebP icons for all demos (#885)	1 vuosi sitten
icon.webp.import	63d1cd9a60 Use 128×128 WebP icons for all demos (#885)	1 vuosi sitten
project.godot	2a962929f3 Update demo files for Godot 4.2.1 (#1013)	9 kuukautta sitten

Hierarchical Finite State Machine

This example shows how to apply the State machine programming pattern in GDscript, including Hierarchical States, and a pushdown automaton.

Language: GDScript

Renderer: Compatibility

Why use a state machine

States are common in games. You can use the pattern to:

Separate each behavior and transitions between behaviors, thus make scripts shorter and easier to manage.
Respect the Single Responsibility Principle. Each State object represents one action.
Improve your code's structure. Look at the scene tree and FileSystem tab: without looking at the code, you'll know what the Player can or cannot do.

You can read more about States in the excellent Game Programming Patterns ebook.