Understand every check.
Keep the release evidence.

A read-only release check

Indie Release Preflight reviews the release profile you select and reports evidence about enabled or explicitly selected scenes, missing scripts in scenes and prefabs, and common placeholder release metadata.

It does not build the player, change Build Settings, edit scenes or prefabs, alter Player Settings, contact a server or guarantee store approval.

Requirements and installation

• Unity 2022.3 LTS or a supported Unity 6 editor.
• A project whose assets have finished importing.
• Saved scenes for scene-level checks.

1. Back up or commit the project.
2. Import the custom package and keep the complete Assets/ScopeGarden/ReleasePreflight folder selected.
3. Wait for Unity to compile. The welcome window opens once for version 1.0.0.

Reopen it through Tools → Scope Garden → Welcome to Release Preflight.

Describe the intended release

Profiles are stored in ProjectSettings/ScopeGardenReleasePreflight.asset, so a team can version them with the project.

• Use the dropdown to switch releases or platforms.
• Use + to add a profile and − to remove one. At least one remains.
• Use clear names such as Windows demo, WebGL jam build or Mobile 1.2.
• Editing a profile clears old results so stale evidence cannot be mistaken for a newer configuration.

Select saved release scenes

• Add scene creates a slot for a saved Scene Asset.
• Use enabled Build Settings scenes replaces the list with every enabled scene.
• The tool reports missing paths, duplicates and differences from enabled Build Settings scenes.
• Empty slots are ignored until a scene is assigned.

Save open scenes first. Missing-script checks can open selected scenes additively, then close only the scenes the tool opened.

Keep scans focused

Enable Scan project prefabs to inspect project prefabs for missing MonoBehaviour scripts. The default search folder is Assets.

For large projects, use release-specific folders such as Assets/Game, Assets/UI or Assets/Prefabs. Package-cache assets and external files are not scanned.

Review common placeholders

The metadata check warns about default company or product names, empty or starter versions, and Development Build being enabled. It reads Player Settings but never changes them. Review platform overrides in Player Settings and document intentional warnings outside the tool.

Understand the result levels

Use Show affected asset when available. Results are a snapshot; rerun after changing the profile, relevant assets, Build Settings or Player Settings.

Export Markdown or JSON

• Markdown creates a readable report with totals and project-relative evidence paths.
• JSON adds the profile name, Unity version, UTC timestamp, totals and structured records.

Prefer a location outside Assets. Reports avoid absolute local paths, but filenames and project-relative structure may still be confidential; review before sharing.

A suggested final pass

1. Save and commit the project.
2. Select the intended target and profile.
3. Run Release Preflight.
4. Fix failures and investigate warnings.
5. Run Unity tests and make a development build.
6. Play on representative hardware.
7. Rerun after the last content or settings change.
8. Archive the report with the build identifier.

Your project stays local

The tool makes no network calls except when you intentionally open these documentation links. Settings remain in the project and exports are written only where you choose. Reports contain project-relative paths and configuration evidence, so treat them as project information.

Removing the tool

1. Close Release Preflight windows.
2. Remove Assets/ScopeGarden/ReleasePreflight.
3. Optionally remove ProjectSettings/ScopeGardenReleasePreflight.asset if saved profiles are no longer needed.

No project configuration needs reverting because the tool does not write to Build Settings, scenes, prefabs or Player Settings.

Include useful, safe details

Include the Unity and OS versions, product version, clean-project result, exact steps and visible error. Do not send confidential projects, credentials, absolute user paths or customer data.