Reference Quest

Editor Guide

Learn the editor workflow that makes Godot fast: scene tree, inspector, debugger, and dock rhythm.

10-20 min Practice first Godot 4.6

Godot editor orientation

Use the editor as a daily production loop

Learn the panels and shortcuts by workflow: scene tree, inspector, script editor, debugger, project settings, then the shortcuts that speed up real iteration.

What to practice

A useful first editor loop

Create a focused test scene.
Add the smallest set of nodes needed.
Expose tuning values in the Inspector.
Run with F6 and inspect Remote.
Save reusable node branches as scenes.

Current section

Daily Workflow

The normal loop is: create or open a scene, select nodes, edit properties, run, inspect the live tree, then commit the working pattern into reusable scenes.

3 practices

Use scenes as prefabs

Ctrl+Shift+A

Instance reusable scenes into other scenes. This is the Godot habit that replaces many Unity prefab and Unreal Blueprint Class workflows.

Practice Create Player.tscn, then instance it into Level01.tscn.

Run the smallest useful scene

F6

Use Run Current Scene while building a player, pickup, menu, or enemy. Switch to F5 once the whole project flow matters.

Practice Open a test scene and make F6 your default iteration key.

Split work by node responsibility

Scene tree

Keep each node's job obvious: movement script on the character body, detection script on the area, animation on the animation node.

Practice Rename three nodes so their role is clear at a glance.

Tutor Checkpoint

Lock the pattern in

Before jumping to the next page, turn the idea into one tiny scene or script. That is where the Godot habit sticks.

Unity habit

The editor is lighter, so iteration depends more on clean scene structure.

Unreal habit

Expect fewer wizard flows and more direct scene/script ownership.

Godot habit

Use docks, quick open, debugger, and remote scene tree as daily tools.

Try this

Debug one running scene with the Remote tab and inspect live node values.