Godot Desktop Applications

Build desktop apps around explicit state, predictable form behavior, full keyboard access, reusable themes, and durable user data. Use Godot's scene system for composition without putting the entire application in one scene script.

Inspect Before Editing

Scale this inspection to the change's risk, and complete the relevant checks before changing scenes, scripts, project settings, or persisted formats.

1. Locate project.godot and confirm the root. Read config/features, main scene, window size and mode, minimum-size handling, stretch/content scale, DPI settings, locale, input actions, and GUI theme configuration.
2. Run the project's established Godot executable with --version when available. Match code, resources, and platform APIs to that exact Godot 4.x release.
3. Inspect representative .tscn, .gd, and .tres files. Record feature boundaries, scene ownership, unique-name use, signal conventions, typed GDScript style, autoloads, services, navigation, dialogs, and naming.
4. Inspect every existing data path and format: ConfigFile, FileAccess, JSON, custom Resource, databases, user://, user-selected files, schema versions, migrations, autosave, and error handling.
5. Inspect themes, fonts and fallbacks, icon strategy, light/dark/system preference, UI scale, focus styles, shortcuts, menu actions, localization, and right-to-left support.
6. Run the current application. Resize to the smallest and largest supported sizes; complete primary workflows with keyboard only; test invalid forms; locate the actual user data directory; and note existing warnings.

Never replace a shipped persistence format or change application identity/user-data location without a migration plan.

Architecture