Move from Unity
Translate GameObjects, Prefabs, MonoBehaviours, input, and C# habits into Godot's scene-first workflow.
Rebuild one small Unity-style prototype with clear node ownership.
Choose one outcome, open its dedicated page, and keep building. Guides explain, labs let you practice, and references stay out of the way until you need them.
Reviewed for Godot 4.7.x0 of 15 focused modules completed
Translate GameObjects, Prefabs, MonoBehaviours, input, and C# habits into Godot's scene-first workflow.
Continue: Move from UnityEach path opens a page dedicated to that subject. Nothing changes silently inside this hub.
Translate GameObjects, Prefabs, MonoBehaviours, input, and C# habits into Godot's scene-first workflow.
Rebuild one small Unity-style prototype with clear node ownership.
Map Actors, Components, Blueprints, UMG, input, and Data Assets into focused Godot systems.
Plan and prove one migration-ready vertical slice.
Learn nodes, scenes, scripts, signals, and project structure through a small playable loop.
Understand why each node exists and which scene owns it.
Connect input, movement, collision, scene composition, and saving in production order.
Finish a responsive, saveable 2D gameplay slice.
Use these when a path sends you here or when one concept is blocking your project.
Build scene trees with visible ownership instead of empty containers.
Translate familiar Unity and Unreal terms into Godot concepts.
Choose body types, layers, masks, and a useful debugging order.
Persist plain game state without serializing live scene nodes.
These destinations change state and ask for input. They are kept separate from reading guides.
Assemble a node tree and generate a clean starting script.
Try Scene BuilderComplete coached GDScript proofs instead of reading another example.
Try Code LabSee actions, dead zones, and device input update live.
Try Input PlaygroundDraft and inspect short GDScript snippets before testing in Godot.
Try Code SandboxShort, direct material for an active build.