gdh

Change a Godot 4.7+ project without fighting the Godot editor, and keep its UIDs right. Use whenever you create, edit, move or delete scenes (.tscn), resources (.tres), GDScript, shaders or project settings in a folder with project.godot; whenever uid:// references, .uid files or unique_id come up; and when the user wants a scene opened, saved or run in their editor. Covers gdh bridge (a live link into the editor), editing open scenes so the user can undo, and what the gdh hooks refuse and why.

Build a Godot 4.7+ game for players — export presets, export templates, debug and release builds, and checking the build runs. Use when the user wants to export, package, ship or build their Godot game, make a Linux/Windows/macOS/web build, or when an export fails.

Write GDScript that is correct for Godot 4.7+ — typed, idiomatic, and free of Godot 3 leftovers. Use when writing or reviewing any .gd file, a @tool script, a custom Resource, signals, await/coroutines, exports, input handling, or physics movement, and whenever you're unsure whether an API name or GDScript feature exists in Godot 4.

Lay out and grow a Godot 4.7+ game project — scene structure, autoloads, the Input Map, physics layers, groups, scene changes, saving player data, and folder layout. Use when starting a Godot project or a new system in one (a player, a level, a menu, a save system), when adding input actions, autoloads or project settings, or when deciding how scenes should talk to each other.