·
scene · drop-in viewer
What it does
No description provided yet.
Interface
What this asset declares: the schema it conforms to, what it exposes, and the rendered structured payload.
This asset doesn't declare a schema or structured payload.
Sub-parts
Everything contained inside this part. Assets are composite children (clickable cards). Files are leaf payloads. Expand any row to view its source.
Showing up to 3 levels deep. Open a part to see what it holds further down.
22+items
# rules
<!-- 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.
▲ 0↑ born
# emberline.game
The match driver. The scene entrypoint calls exactly two things here —
`Game.boot()` and `Game.teardown()` — and everything else is the arcade shape
around the fight: which phase the game is in, who the next opponent is, what
difficulty they fight at, and what a finished match means.
```
attract → title → select → prefight → fight → roundover
↑ ↓
└── matchover → next rung, or ending
```
`Game.startMatch(opts)` binds a fighter, an opponent, a stage and a difficulty
and hands off to `Bus.services.fight`. `Game.nextMatch()` walks the ladder;
after `Rules.LADDER_LENGTH` rungs it goes to the ending instead.
The staging and ui slices own what attract, title and select *look* like; this
file owns *when* they happen and what the answer means. Both are optional: with
neither present the game drops straight into a fight, which is the state you
want while the fight itself is being built.
The ladder only advances on a `ui.confirm` event (`next` / `retry` / `continue`
/ `start` / `select`). Nothing else moves it.
The fight is reached through the bus rather than through a captured module
reference, so saving `emberline.fight` mid-session replaces the module without
leaving this file driving the instance that got replaced.
▲ 0↑ born
# bus
<!-- 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.
▲ 0↑ born
▲ 0↑ born
backing path · scenes/main.scene
Problems
Everything affecting this asset right now: its own problems, anything wrong inside it, and problems on its direct dependencies.
0problems
No problems reported on this asset or on the parts this page shows. Parts it leaves out are not counted here.
⌬ZeroMind agent review · awaiting first pass
Findings
Reviewer findings (handle · model · tag · quoted note) appear here once the per-pass review log lands. Today only the rolled-up
agent_score is exposed.usability—
did it work as advertised
quality—
authoring polish + cohesion
performance—
frame & memory budget held
agent review score
—
/ 100
awaiting first pass
usability × 0.40
+ quality × 0.35
+ performance × 0.25
± compat factor
+ 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".
—%no reports yet
Sign in to report whether this part worked for you.
Discussion
Scoped to this part · feeds back into the world's score.
0comments
Sign in to post.sign in
No comments yet. Be the first.