Finish with a real request in a player build, not only a clean visual preview.
Final guided checklist#
- Save your design copy, post data, registry connections and changed scenes/prefabs.
- Enable the destination and safe-menu scene in the active build list.
- Run every real start action, including repeated input and busy-request handling.
- Verify readiness success and a deliberate timeout/recovery path.
- Test video natural end/Skip, Continue and countdown routes. Confirm time, input and gameplay targets restore.
- Review fonts, translations, safe areas, portrait/wide profiles and Reduced Motion.
- Test ordinary tracks, video audio, countdown sounds and mute in the target player.
- Measure activation/initialization, memory and frame time on representative hardware.
Glossary#
| Term | Meaning |
|---|---|
| Prepared / Activation | Operation at its activation boundary / making the destination live. |
| Game Ready / Complete | Required readiness finished / the entire flow exited and released its hold. |
| Profile / Override | Aspect-matched reference space / local change to inherited data. |
| Checkpoint | Signal/task stage with stable ID, phase and completion contract. |
| Panel | Baked native UI driven manually or used to start the saved-design loader. |
Version scope#
This web documentation adapts the supplied 20 October 2026 English guide. The publisher's compatibility statement is Unity 6000.3.13 or newer; earlier Unity versions have not been tested. The guide's inspected source environment is Unity 6000.3.13f1. This website does not add runtime or platform testing. Screenshot values are examples: None, unchecked fields and Missing references can show unfinished setup, as the walkthroughs explain.
The supplied PDF describes source review of LoadingScreenBuilder.cs, Runtime/Core, Runtime/Data, Editor views, GettingStarted.md and DeveloperAPI.md. This website uses the provided PDF and screenshots; it does not claim new runtime or device tests.
Source material#
- All 28 supplied Builder screenshots are included in the relevant web chapters.
- The supplied cover, package card and icon remain the product artwork, including their original ERAGANX branding.
- Eight complete C# scripts from PDF pages 38–45 are available in Runtime C# examples.
- The original 54-page document is available as a downloadable English PDF.
The PDF's portable-authoring section references a Documentation/FullGuide folder and a Guide_Code_Examples ZIP in its source project. Those are descriptions of that project, not additional downloads provided by this website. Individual scripts are available here.