What problem does it solve?
This Skill solves the problem of structuring a Godot game so the main scene stays persistent while levels are loaded, swapped, and freed safely underneath it. It helps avoid scene-tree replacement mistakes that break UI, cameras, viewport rigs, or other long-lived systems.
Core Features & Use Cases
- Persistent Main Scene: Defines a thin
main.tscn entry point that owns the shell of the game and survives level swaps.
- Safe Level Loading: Loads level scenes into a dedicated host node and frees old levels cleanly to prevent double cameras and rendering conflicts.
- Paradigm-Aware Camera Layout: Supports top-down or isometric projects with a persistent camera in Main, and first-person or third-person projects where the camera stays with the Player inside the level.
- Project Integration: Guides how to set
run/main_scene, organize folders, and record conventions so the entry point remains consistent.
- Use Case: When a project needs a reusable gameplay shell, this Skill helps create the startup scene, wire level swapping, and keep UI and global systems intact across scene transitions.
Quick Start
Ask for a Godot main scene setup that creates main.tscn, loads the first level under a LevelHost, and follows the correct camera ownership pattern for the project’s genre.