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

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