mirror of
https://github.com/godotengine/godot-demo-projects.git
synced 2026-01-04 15:00:09 +01:00
faae60ac2f
Opened them, saved all scenes, ran the project. Did necessary fixes here and there, fixed some warnings (but some remain in bigger demos). Did not port JRPG demo yet (#306) nor the two platformer demos.
43 lines
2.0 KiB
Plaintext
43 lines
2.0 KiB
Plaintext
[gd_scene load_steps=4 format=2]
|
|
|
|
[ext_resource path="res://fonts/source_code_pro_explanations_bold.tres" type="DynamicFont" id=1]
|
|
[ext_resource path="res://fonts/source_code_pro_explanations.tres" type="DynamicFont" id=2]
|
|
[ext_resource path="res://debug/top_level_ui.gd" type="Script" id=3]
|
|
|
|
[node name="Explanations" type="RichTextLabel"]
|
|
anchor_right = 1.0
|
|
anchor_bottom = 1.0
|
|
margin_left = 10.0
|
|
margin_top = -370.0
|
|
margin_right = -10.0
|
|
margin_bottom = -730.0
|
|
rect_clip_content = false
|
|
mouse_filter = 2
|
|
size_flags_vertical = 4
|
|
custom_fonts/bold_font = ExtResource( 1 )
|
|
custom_fonts/normal_font = ExtResource( 2 )
|
|
bbcode_enabled = true
|
|
bbcode_text = "This example shows how to apply the State programming pattern in GDscript, including Hierarchical States, and a pushdown automaton.
|
|
|
|
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 [b]one[/b] 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 [url=http://gameprogrammingpatterns.com/state.html]Game Programming Patterns ebook[/url]."
|
|
text = "This example shows how to apply the State programming pattern in GDscript, including Hierarchical States, and a pushdown automaton.
|
|
|
|
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."
|
|
script = ExtResource( 3 )
|
|
__meta__ = {
|
|
"_edit_lock_": true
|
|
}
|
|
|