Record editor and package choices, validate imported assets and layouts, and prove a clean checkout can produce the documented playable baseline.
Choose the Unity Editor version, installed platform modules, target platform and render/input packages appropriate to the project. Record them in a setup note with the starting revision. Use the documentation for those versions; upgrading the editor, packages and assets at once makes a regression harder to locate.
Separate game-owned scenes, scripts, prefabs and source art using a documented folder convention. Keep third-party packages identifiable and record their licenses. Configure the engine’s actual scene list or build profile explicitly; a numeric filename prefix is only a naming convention. Introduce assembly definitions when their boundaries serve dependencies or tests, then measure any compile-time benefit.
Import a small set of textures, sprites, audio and models before the full library. Check the target-specific import overrides and the resulting stored format and dimensions. For a texture comparison, calculate its base or exact mip-chain data size and layer count, then inspect the real resource on target hardware. Save source assets and import settings together.
Build a scene with the main controls and text. Calculate exact aspect ratios for your chosen resolutions, then test anchors, safe areas, cropping, large text and input navigation in the actual layout. Physical PPI may describe a panel, but it does not validate logical UI scaling or accessibility.
Track the assets and their metadata, project settings, package manifest and package lock file required by your chosen workflow. Exclude generated caches and temporary build output according to that workflow. From a fresh checkout, use the recorded editor and modules, resolve packages, open the minimal scene and make a build. Record any manual prerequisite that was missing.
Run the clean build on the target device and capture startup, controls and representative scene behavior. Name the baseline revision and save its logs, build artifact and setup note. Record an owner for dependency upgrades and a way to recover the prior working baseline. Use the test matrix for later setup or package changes.
Write and download the environment, clean-checkout steps and baseline record.
Count texture data using the imported format, dimensions, mip choice and layer count.
Reduce target pixel dimensions to exact ratios before checking the real layout.
Record build and configuration checks during initial setup and later changes.
Loading your checklist…
Unity’s project manifest manages package dependencies and registry settings. Its lock-file setting supports deterministic dependency resolution; the editor version is a separate part of the environment record.
Unity’s documented Cloud Build auto-detection uses ProjectSettings/ProjectVersion.txt. Include the project’s editor-version record in source control and match the installed editor when reproducing the build. This reference documents that file, not a recommendation to adopt the historical Cloud Build workflow.
Record the result rather than assuming the setup is portable.
| Check | Evidence |
|---|---|
| Environment | Editor, modules, packages and starting revision |
| Import | Representative asset settings and resolved resource |
| Build | Build profile, scene list and output version |
| Reproduction | Fresh-checkout instructions and actual device result |
Keep a working baseline and retest the representative scene after each dependency change.
Choose conventions the team can follow; measure whether an assembly split improves iteration.