On a phone, reading vertically is fine. Code and interactive tasks are more comfortable in landscape mode.
Lesson 001
001. Project, Scene, and Node
The first practical step: understand that a Godot project stores the game, a scene describes one piece of the game, and nodes are the parts inside that scene.
What we will do
- understand what a Godot project is;
- see what a scene is for;
- learn why scenes need nodes;
- prepare for the first script.
First path in Godot: project → scene → Node2D
Node2D is the root of our first 2D scene. After creating Node2D, save the scene as main.tscn, so you can close the project and open it later without losing the scene.
Project
A project is the folder for the whole game. It contains scenes, images, sounds, scripts, export settings, and the files Godot uses to run everything.
Simply put, the project answers: where does the whole game live?
Scene
A scene is one piece of the game. It can be a player, menu, level, button, item, or full screen.
Scenes are convenient because small pieces can be assembled and then reused inside larger scenes.
Node
A node is a part of a scene. Sprite2D shows an image, Button receives clicks, Timer counts time, and Area2D notices overlaps.
project → scene → nodes → behavior
The first script comes next
Do not rush into code yet. First notice where the object lives, how it sits inside the scene, and what role it plays.
Mini-check
What does a project store?
The whole game: scenes, assets, scripts, and settings.
What does a scene describe?
One piece of the game: a screen, level, player, button, or another object.
Why do nodes matter?
They give a scene concrete abilities: image, button, timer, overlap detection, sound, or logic.
Next step
Next we will add a short GDScript to a scene and make an object do something simple.
Lesson 002