Danil Alexeev c492e5fd73 Update some GDScript files for Godot 4.3 (#1129) 3 months ago
..
debug bac1e69164 Use static typing in all demos (#1063) 8 months ago
fonts 5553ecfd88 Fix font code for Godot 4 in Finite State Machine (#1027) 10 months ago
player c492e5fd73 Update some GDScript files for Godot 4.3 (#1129) 3 months ago
screenshots fcc7d5c723 Optimize PNG images using oxipng 4 years ago
state_machine c492e5fd73 Update some GDScript files for Godot 4.3 (#1129) 3 months ago
Demo.tscn 5553ecfd88 Fix font code for Godot 4 in Finite State Machine (#1027) 10 months ago
README.md b4c73f4888 Fix README links to asset library (#1078) 7 months ago
icon.webp 63d1cd9a60 Use 128×128 WebP icons for all demos (#885) 1 year ago
icon.webp.import 63d1cd9a60 Use 128×128 WebP icons for all demos (#885) 1 year ago
project.godot bac1e69164 Use static typing in all demos (#1063) 8 months ago

README.md

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

Check out this demo on the asset library: https://godotengine.org/asset-library/asset/2714

Why use a state machine

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

  1. Separate each behavior and transitions between behaviors, thus make scripts shorter and easier to manage.

  2. Respect the Single Responsibility Principle. Each State object represents one action.

  3. 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.

Screenshots

Screenshot