Evidence, status and limitations¶
This wiki is a development reference built by static repository inspection. Catalogue snapshots are not new gameplay tests. A Current entry can still have open human, network or performance acceptance.
Source precedence¶
Current runtime source plus the definitions actually referenced by authoring determine current behaviour. Design documents determine intent. Validation records determine what a particular check proved. When they conflict, record the discrepancy rather than silently treating the newest prose as implementation.
Example: historical checkpoint prose described one entrant after choices; current RunRules requires all participants to enter before selection. Another example: four sequence entries reuse maps and do not establish a completed four-biome campaign.
Existing evidence records¶
The testing procedure defines fresh versus reused evidence, identity and failure classification; the catalogue maps all current fixtures/harnesses. The test refinement execution record separates new tooling checks from historical gameplay acceptance. These links use the existing collector, not another policy source to edit.
| Area | Record |
|---|---|
| Overall roadmap and latest state | Project plan |
| Current AI wiki inspection and dirty state | Wiki update record |
| Shooter/search checkpoint evidence and later deltas | AI implementation record |
| Spawning/boss/debug evidence and pending coordination | Spawn companion |
| Later exposed-target firing / oscillation checkpoint | Focused fix record |
| Session foundation | Prototype validation |
| Combat foundation | Combat validation |
| Encounter/run polish | Encounter validation |
| Build library | Ability menu validation |
| Cores/menu/feedback | Feedback validation |
| Pack Advance/action lifecycle | Pack action validation |
| Tracer collision/presentation | Tracer validation |
| Natural arrivals/owner observation | Arrival validation |
| Protocol identity | Network protocol validation |
These links expose selected repository text locally, outside normal wiki search. Their test totals/build labels are historical evidence scoped to those reports; they are not rerun or generalized here.
Remaining game acceptance¶
The latest project record leaves the bounded natural-arrival campaign and roster expansion work open. Human balance/feel/readability, representative four-player hardware profiling, separate-network acceptance and permanent unlock persistence remain distinct milestones. Consult the live repository plan for changes after this wiki snapshot.
Static collector limits¶
The collector parses supported C# catalogue declarations and Unity text serialization using safe YAML construction and typed GUID/fileID references. It does not execute C#, virtual properties, shared resolvers, fallback code or scene lifecycle.
Authored fields and their source interpretation can differ through schema migration, inherited slots, duration overrides, target resistance and runtime clamping. Entries show those distinctions and reference related assets. Missing/unsupported required input fails the export rather than producing a partial current catalogue.
Source hashes include paths/content and metadata, so additions, deletions and changed .meta files invalidate the snapshot. Concurrent changes detected before publication preserve the previous complete export. Generated content is deterministic apart from the separate provenance timestamp/revision record.
See wiki implementation evidence for the documentation checks actually run.