Hugo Locurcio
2a962929f3
Update demo files for Godot 4.2.1 (#1013)
|
9 ماه پیش | |
|---|---|---|
| .. | ||
| debug | 1 سال پیش | |
| fonts | 1 سال پیش | |
| player | 1 سال پیش | |
| screenshots | 4 سال پیش | |
| state_machine | 1 سال پیش | |
| Demo.tscn | 1 سال پیش | |
| README.md | 1 سال پیش | |
| icon.webp | 1 سال پیش | |
| icon.webp.import | 1 سال پیش | |
| project.godot | 9 ماه پیش | |
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/516
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.
Screenshots
