Documentation map

A task-oriented path from an empty Unity project to an accepted release package. Read only the stage you are working on.

1. ConnectPackage, component, events 2. First mechanicHits, score, completion 3. Local verificationMock Launcher and failures 4. Linux buildProjector, fullscreen, 60 FPS 5. Game packageManifest, media, checksums 6. AcceptancePhysical target and QA

By role

GAMEPLAY

Programmer

Start with lifecycle, hits, API and Mock Launcher.

Open integration →

ART / UX

Designer

Study coordinates, pause behavior, localization and projection requirements.

Open coordinates →

RELEASE

Technical producer

Use requirements, packaging, compatibility and QA as acceptance criteria.

Open requirements →

Minimum before development

Unity 2022.3 LTS installed Linux x86_64 module installed Stable game ID agreed One-player or 1/2-player support selected Team understands that the game talks only to Launcher