Danil Alexeev
c492e5fd73
Update some GDScript files for Godot 4.3 (#1129)
|
3 mesi fa | |
|---|---|---|
| .. | ||
| debug | 8 mesi fa | |
| fonts | 10 mesi fa | |
| player | 3 mesi fa | |
| screenshots | 4 anni fa | |
| state_machine | 3 mesi fa | |
| Demo.tscn | 10 mesi fa | |
| README.md | 7 mesi fa | |
| icon.webp | 1 anno fa | |
| icon.webp.import | 1 anno fa | |
| project.godot | 8 mesi fa | |
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:
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
