Development setup and workflow¶
Use the pinned Editor and repository setup records for future game work. The wiki itself runs independently of Unity and can be built or previewed without launching the Editor or game.
Game work reference¶
Start with the current project brief. Use the agent workflow for experience-led experiments, risk-based technical/gameplay/UX review and promotion into the normal game. The workflow evaluation records documentation checks and read-only walkthroughs, not measured agent savings or gameplay. Read the frozen project history only when a past decision or evidence identity matters. These are refreshable source-text snapshots; the repository Markdown is canonical. Older history does not override current policy.
The repository's setup document covers opening the Editor, foundation/combat menus, Windows builds and online prerequisites. Integration scripts launch development players and use online services; they are documented references here and were not run for this wiki.
Do not enable paid billing, buy assets or start paid generation without authorization. Preserve package/Editor pins and record asset licences. Share the entire Windows build folder rather than the executable alone.
Validation categories¶
Choose checks using the canonical testing procedure and complete catalogue. Root agent guidance owns policy; these documents own commands, selection, identity, recovery and evidence limits. Full suites retain full meaning; prose-only edits normally need no Unity checks.
| Category | What it can establish |
|---|---|
| Static source inspection | Authored inventory and traced rules; no live execution |
| Automated rules tests | The tested rules under their fixture assumptions |
| Editor checks | Actual authored objects/components/runtime paths inspected |
| Built-player/network checks | The measured build/protocol/session scenarios |
| Human gameplay | Feel, readability and behaviour under actual control |
| Hardware profiling | Measured cost on named representative hardware |
Passing one category does not stand in for the others. See the evidence guide for source records and remaining limits.
Wiki commands¶
From the repository root, Tools/Wiki/Setup-Wiki.ps1 prepares the isolated pinned documentation environment. Build-Wiki.ps1 checks and builds; Preview-Wiki.ps1 serves a local preview; Test-Wiki.ps1 runs documentation tests and integrity checks. Refresh-Wiki.ps1 regenerates source snapshots after reviewed changes.
These commands do not invoke Unity, compile C# or launch gameplay. The upkeep guide explains the static collector's limits.
Source: setup, foundation evidence, debug arena guide, asset provenance.