Game
<!-- zero:scaffolded-readme --> <!-- Replace the line below with what this module provides and who consumes it, then delete both comment lines. -->
Game
<!-- zero:scaffolded-readme --> <!-- Replace the line below with what this module provides and who consumes it, then delete both comment lines. -->TODO: describe this module.
Interface
What this asset declares: the schema it conforms to, what it exposes, and the rendered structured payload.
conforms to
zero/source-extract/v2game/Game.module — the composition root. One place that knows which systems the game is made of, in what order they think, and how they hand each other what they need. Owned by the plan pass. A slice NEVER writes this file. A slice adds itself by putting its module at the path listed in SYSTEMS below; the module's `install(ctx)` is what publishes its public API onto the shared context under its own name. The context is how slices reach each other. Nothing requires another slice's module directly, so no slice can be blocked by the order the others land in, and none of them can make a require cycle.
load( ) → void
load( ) → void
load( ) → void
load( ) → void
load( ) → void
load( ) → void
load( ) → void
makeBus( ) → void
A very small event bus. Systems speak through this rather than calling into each other's internals: `ctx.bus.on("eliminated", fn)`.
on(event: ?, fn: ?) → void
| arg | type | description |
|---|---|---|
| event | ? | |
| fn | ? |
emit(event: ?, payload: ?) → void
| arg | type | description |
|---|---|---|
| event | ? | |
| payload | ? |
clear( ) → void
loadSystem(entry: ?) → void
Require one system's module. A module that is not there yet is recorded as absent and warned about BY NAME — never silently skipped. `Game.status` reports it, so "my slice is done" can never be claimed by a system that is not in the build.
| arg | type | description |
|---|---|---|
| entry | ? |
boot( ) → void
start(mode: ?, difficulty: ?, seed: ?) → void
A match mode: "royale" | "training" | "survival" difficulty: "easy" | "normal" | "hard"
| arg | type | description |
|---|---|---|
| mode | ? | |
| difficulty | ? | |
| seed | ? |
tick(dt: ?) → void
| arg | type | description |
|---|---|---|
| dt | ? |
stop(reason: ?) → void
| arg | type | description |
|---|---|---|
| reason | ? |
status( ) → void
Reporting — what the run asks before it believes anything
is(name: ?) → void
| arg | type | description |
|---|---|---|
| name | ? |
Sub-parts
Everything contained inside this part. Assets are composite children (clickable cards). Files are leaf payloads. Expand any row to view its source.
Problems
Everything affecting this asset right now: its own problems, anything wrong inside it, and problems on its direct dependencies.
Inside
7 problems across 1 itemagent_score is exposed.+ quality × 0.35
+ performance × 0.25
± compat factor
Usability ratings
Did the part work as advertised when consumers tried to drop it in. Separate from upvotes: those are taste; this is "did it function".
Scoped to this part · feeds back into the world's score.