Open and explain a playable scene

Open and explain a playable scene — guided practice

Import a complete project and connect its scene, script and visible result.

Install the free Godot 4 editor suitable for your computer. Extract project.godot, main.tscn and main.gd into one new folder, keeping the names unchanged. In Godot Project Manager choose Import, select project.godot, then Import & Edit. Open main.tscn; use Run Project (F6 runs the current scene, while F5 runs the configured project). The game is a 640×480 top-down collection activity with no external assets. Arrow keys move; Space pauses; R restarts. Finish each changed case, then restore the supplied baseline before the next lesson.

1. 1. Import and run

   Import the three supplied files as described in setup. Open main.tscn and run the project.

   You should see: A blue circle and four gold squares appear with Score: 0/4.

   Starting from a complete runnable project gives each later edit a visible baseline.

2. 2. Inspect the saved scene

   Stop the game. Read main.tscn: one TokenTrail node of type Node2D has main.gd attached.

   You should see: The scene references res://main.gd and matches the file on disk.

   A broken resource path prevents a scene from finding its behavior.

3. 3. Find the runtime child

   Read _ready in main.gd, then run again. Expand the Remote scene tree while the game is running.

   You should see: A Label child exists under TokenTrail at runtime.

   add_child creates the HUD during execution, so it is absent from the saved scene file.

4. 4. Record a baseline

   Write project version, three file names and the starting visible state in playtest.md.

   You should see: The record distinguishes saved nodes from the Label created at runtime.

   A baseline helps identify what a future edit actually changes.