Packaging and Distribution · Version 0.5
Build Preflight
Validate project metadata, JSON content, assets, scenes, references, casing, and content classification before packaging a Windows game.
Build preflight is the shared release gate used by the editor and packaging tools. It checks whether the active project can be collected into an editor-free Windows build without unsafe or ambiguous content.
Preflight checks
- Project metadata, build target, window settings, and entry scene.
- Supported versioned JSON documents and registry integrity.
- Referenced scenes, assets, audio, tilesets, dialogue, templates, and RPG content.
- Project containment and refusal of external or escaping paths.
- Exact filename case and duplicate Windows destinations.
- Missing assets, missing scenes, old unsupported formats, and unclassified content.
- Content-manifest rules that decide what ships with the build.
Run preflight in the editor
- Save the active scene.
- Open Windows → Package Windows Game.
- Choose Run Preflight.
- Wait for the background operation to finish.
- Review the error and warning counts plus structured diagnostics.
- Repair project content and rerun until the result is acceptable.
One validation authority
The editor window calls the same BuildPreflight authority used by the command-line tool. There is no separate simplified UI validator that can disagree with the actual build.