Guides / Godot Game Development - Complete Learning Guide / Godot Basics: Interface, Scenes, and Nodes

Godot Basics: Interface, Scenes, and Nodes

What you'll learn

By the end of this chapter you will know how to move around the Godot 4 editor, understand what a scene and a node are, save your work safely, and run a project with a clear main scene. This is the foundation every later chapter builds on.

These steps assume Godot 4.x (4.2 LTS or newer is ideal). If you use a slightly older 4.x build, menu names may differ slightly, but the ideas stay the same.

Prerequisites

Godot installed from the <a href="https://godotengine.org/download/">official site</a> (no account required for the standard editor).
About ten minutes of focused time.

Step 1: Create or open a project

Launch Godot. You will see the Project Manager.
Click New Project.
Choose an empty folder for your project path (avoid spaces in the path if you can).
Pick a renderer: for learning, Forward+ or Mobile is fine; you can change later for new projects.
Click Create and Edit.

You should now see the main editor with a default empty scene prompt.

Pro tip: Keep one small “learning” project for these guides, separate from serious prototypes, so you can experiment without fear.

Step 2: Map the main editor areas

Get oriented with five regions you will use constantly:

| Area | Purpose |

| --- | --- |

| Viewport | Visual preview of the open scene. You pan and zoom with the mouse wheel and middle button (or editor shortcuts). |

| Scene tree (usually top-left) | Hierarchical list of nodes in the current scene. Parent-child order matters for transforms and logic. |

| Inspector (usually right) | Properties of the selected node: transform, scripts, materials, collision, and more. |

| FileSystem dock | Files inside your project folder (<code>res://</code>). Scenes, scripts, and assets live here. |

| Output / Debugger | Errors, prints, and profiler output when you run the game. |

If a dock is closed, use Editor → Editor Layout or drag dock tabs to restore a comfortable layout.

Step 3: Nodes, scenes, and why Godot is “scene-first”

A node is a single building block: a sprite, a camera, a collision shape, a UI button, or an empty organizer.

A scene is a tree of nodes saved as a file (<code>.tscn</code>). Scenes can be instanced inside other scenes, which is how Godot encourages reuse (player, enemy, level chunk, HUD).

Mental model: A scene file is like a prefab plus level hierarchy in other engines, but it is the default way Godot structures everything—not an optional feature.

Step 4: Build your first minimal scene

When Godot asks to create a root node, choose 2D Scene (or add a Node2D as root manually).
With the root selected, click Add Child Node and add a Sprite2D or, if you have no image yet, a ColorRect under a Control root for a quick visual placeholder.
Save the scene: Scene → Save Scene (or <code>Ctrl/Cmd + S</code>). Name it <code>main.tscn</code> in a folder like <code>scenes/</code>.

You now have a real scene file on disk under <code>res://</code>.

Step 5: Set the main scene and run the game

Open Project → Project Settings → Application → Run.
Set Main Scene to your <code>main.tscn</code> (or right-click the scene in FileSystem and choose Set as Main Scene).
Press F5 (Run Project) or click the Play button in the top-right.

You should see a window with your scene. An empty window usually means the camera sees nothing yet—add visible nodes or move the camera.

Step 6: Parent and child transforms (short version)

Child nodes inherit the parent’s position, rotation, and scale. Moving a parent moves every child with it. This is how you group a character body, weapons, and pickup points.

Common mistake: Putting world-level objects under a moving player node. Keep environment scenes separate from the player hierarchy unless you intend them to follow the player.

Mini exercise

Create a new scene with a CharacterBody2D root (you will use this in later movement chapters).
Add a CollisionShape2D and a Sprite2D (or AnimatedSprite2D) as children.
Save as <code>player.tscn</code> and instance it into <code>main.tscn</code> using Instance Child Scene from the Scene tree toolbar.

You do not need working movement yet—only a clean hierarchy to reuse in the next chapters.

Troubleshooting

The editor looks empty after opening a project

Use Editor → Editor Layout → Default and confirm you opened the correct project folder.

Run does nothing or errors about main scene

Set the main scene explicitly in Project Settings or via the FileSystem context menu.

I saved but cannot find the file

Check the FileSystem dock path. Godot only shows files inside the project root.

Nodes are grayed out or missing

You might be in a tool mode or have a read-only project on OneDrive/cloud sync—copy the project to a local folder if sync causes file locks.

Common mistakes to avoid

Mixing 2D and 3D nodes under one root without understanding separate viewports (stick to 2D roots for 2D games).
Editing resources in the Inspector without saving scenes afterward—save early and often.
Putting scripts on the wrong node—attach gameplay scripts to the node that owns the behavior (often the root of that scene).

Pro tips

Learn the shortcut Ctrl/Cmd + Shift + O to Quick Open scenes and scripts.
Name nodes predictably (<code>Player</code>, <code>Hitbox</code>, <code>Camera2D</code>) so signals and paths stay readable.
Use Remote scene tree while the game runs (Debugger tab) to inspect live node state.

Next steps

Continue to GDScript Fundamentals in the next chapter to attach a script to your <code>CharacterBody2D</code> and react to input. If you want official reading alongside this guide, bookmark the <a href="https://docs.godotengine.org/en/stable/">Godot 4 documentation</a> section First steps.