LESSON 1 OF 6

Open a room and understand its parts

Import the starter, find the scene and scripts, and make one small visual change you can identify.

Godot 4.7.2 stable · standard edition · GDScript · 15 minutes estimated practice

0 of 6 lessons completeGuest progress stays in this browser. Account progress is separate.

Continue your working project from the previous lesson. Each download is the completed version of this lesson, for recovery and comparison. Start lesson one with checkpoint 01.

Start with a working foundation

The first checkpoint supplies a small room and a stationary courier. It includes the scene, drawing code and status label so you can concentrate on one new rule at a time. The ZIP is an editable project, not an application installer.

For lesson one, use checkpoint 01 as your starting point. For later lessons, continue editing your own project from the preceding lesson. Each download is the completed state of its lesson, useful for recovery and comparison.

Download checkpoint 01, extract it to a folder named Delivery-Working, and keep the ZIP as an untouched reference.
Open Godot 4.7.2. In Project Manager choose Import, select Delivery-Working/project.godot, then choose Edit. Open main.tscn from the FileSystem dock if it is not already open.
Press F5 to run the project. You should see a room, a courier near the lower left and a starting instruction. Arrow movement is added in the next lesson. Press F8 to stop.

Read the scene before editing it

The scene root DeliveryRoom is a Node2D with game.gd attached. Its Player child is a CharacterBody2D with a circular CollisionShape2D and player.gd. Floating motion mode suits this top-down game. The Status child is a Label that displays feedback.

The game.gd script draws the board with simple original shapes. player.gd draws the courier. Names such as $Player and $Status are scene paths: the script and scene must agree about those names.

DeliveryRoom (Node2D, game.gd)
├── Player (CharacterBody2D, player.gd)
│   └── CollisionShape2D (CircleShape2D, radius 12)
└── Status (Label)

Make one visible change

Stop the game. Open game.gd in the Script workspace and find the following line inside _draw(). It paints the floor. Change only dce6d4 to another six-digit color, save, and run again. Return it to the original color when you have compared the two versions.

This is a small test: you know which input changed and which result to look for. The next lesson adds behavior while preserving the room.

Save with Ctrl+S, press F5, and check that the room floor changed while the courier and text remain visible.
Stop with F8. Restore the original floor color and save. Keep this working folder for the following lessons.

	draw_rect(Rect2(40, 140, 880, 440), Color("dce6d4"))

OBSERVE THE RESULT

Check your work.

The project opens without red parser errors.
F5 starts the room and F8 stops it.
Changing the floor color changes that part of the scene, and restoring the value restores it.

I ran these checks and observed the expected results.This is self-reported practice, not a qualification.

If something went wrong.

Import project.godot from the extracted folder; running files inside a ZIP will not give you a normal editable project.
Choose the standard Godot 4.7.2 edition and Compatibility renderer. This workshop uses GDScript.
Keep the Player and Status node names exactly as written because the scripts use those paths.

TAKE THE CONTEXT TO YOUR OWN CHATGPT

Ask about one small step.

I am using Godot 4.7.2 standard edition for First Play Studios’ One Small Delivery workshop, lesson room. My scene is DeliveryRoom with Player/CollisionShape2D and Status. Explain one unfamiliar scene or script concept, then ask me to make one small change and describe how I can verify it.