Stage 2 of 8 · 7 lessons · ~2 months
Programming for games
Learn GDScript in Godot: nodes, scenes and the scene tree, the _ready and _process callbacks, signals, exported variables, state machines and debugging.
Start: GDScript with static typesLessons· one lesson for each topic, in this order
Do this
- Finish the first units of your engine's official beginner course.
- Rebuild the player from your clone with a state machine instead of booleans.
- Split one large script into at least three small components or child nodes.
- Add a health component that raises an event and a UI element that listens to it.
- Expose every tuning value in the editor and tune the jump or movement until it feels right.
- Fix one bug using a breakpoint and one using debug drawing.
- Commit after each working change.
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
Before moving on: A small Godot game written in typed GDScript: a player scene with a state machine, an enemy scene, a health component that emits a signal, and a HUD connected to it, with tuning values as @export variables.

Follow the official course for your engine, but after every lesson change the project without instructions: add an enemy, a power-up, a second level. The difference between people who can make games and people who can follow tutorials is exactly that moment of building something the video did not show.