Stage 2 · Lesson 3 of 7
Signals
are 's built-in events. A node sends out (emits) a signal when something happens. Examples are body_entered on an Area2D, or a custom health_changed signal you declare yourself.
Any function connected to that signal then runs. You can connect in the editor, or in code with signal_name.connect(callable). The rule of thumb is "call down, signal up".
Parents call methods on their children, and children emit signals that parents or siblings listen to. This keeps scenes reusable: a scene that only emits signals does not care who is listening. The next stage uses signals for pickups, damage zones, timers and UI buttons.
Common trapa child reaching up the tree to call its parent directly.
A question to check yourself, an AI practice session and 1 cheat sheet entry come with the full roadmap. Unlock
Resources for this stage
Start with· follow one of these
- CourseFreeLearn GDScript From Zero
GDQuest · Beginner
A free browser app that teaches GDScript from zero with checked exercises
- CourseFreeGodot Docs: Your First 2D Game
Godot Engine · Beginner
The official complete first game: scenes, signals, input, spawning and a HUD
Practise
Keep handy
Also worth your time
The official guide to connecting, declaring and emitting signals
- Game Programming PatternsGo deeper
Free book on the state, observer, component and other patterns games rely on