Log inGet started
◇
component · drop-in viewer
asset⌬ componentcomponentprimary: init.luau·originates fromworld 76197f6f-8…●1problem

Session

<!-- zero:scaffolded-readme --> <!-- Replace the line below with what this component provides and who consumes it, then delete both comment lines. -->

by◐Daksh·posted 1mo ago
What it does

Session

<!-- zero:scaffolded-readme --> <!-- Replace the line below with what this component provides and who consumes it, then delete both comment lines. -->

TODO: describe this component.

Interface

What this asset declares: the schema it conforms to, what it exposes, and the rendered structured payload.

conforms to

zero/source-extract/v2

game/Session.component/init.luau THE MISSING FLOOR — the run itself. Session owns the shape of a play session and nothing about how it looks or what is in it: * it starts on the title card (gameplay held), and leaves it on NEW GAME or CONTINUE * it plays the two intro lines over the first few seconds of a new run * it holds the checkpoint the presence sends you back to * it turns a reached ending into a bus event the HUD renders * it restarts cleanly, which is the one thing a game like this always gets wrong It reaches every other system through `Core.Bus` and never through a direct reference, so the HUD, the story, the presence and the building can all be written, rewritten or missing without this file changing. BUS IT RECEIVES "ui" { id } the UI's buttons. It answers: new_game | continue | restart | quit | resume "caught" {} the presence took the player -> back to checkpoint "checkpoint" { pos, floor } a new place to be sent back to "reach_end" { id } something decided the run is over BUS IT EMITS "menu" {} show the title "begin" {} the run is live; drop the cards "intro" { lines } the two opening lines "objective" { text } the current objective line (also on "stage") "dark" { seconds } fade the screen down (the presence taking you) "restart" {} a clean run just began

avatar( ) → void

placePlayer(x: ?, y: ?, z: ?) → void

argtypedescription
x?
y?
z?

onModuleReload(path: ?) → void

argtypedescription
path?

toTitle( ) → void

beginRun(fresh: ?) → void

argtypedescription
fresh?

checkpoint(x: ?, y: ?, z: ?, floor: ?) → void

argtypedescription
x?
y?
z?
floor?

caught( ) → void

What the presence does to you: not a death screen — the lights go, and you are somewhere else with no memory of the walk.

reachEnding(id: ?) → void

argtypedescription
id?

wire( ) → void

awake( ) → void

start( ) → void

onDestroy( ) → void

Sub-parts

Everything contained inside this part. Assets are composite children (clickable cards). Files are leaf payloads. Expand any row to view its source.

3items
This part has no composite children. See the Files segment for its leaf payloads.
backing path · game/Session.component

Problems

Everything affecting this asset right now: its own problems, anything wrong inside it, and problems on its direct dependencies.

1problem

Inside

1 problem across 1 item
●
dep.unresolved · L52
could not resolve `./core.module`
⌬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

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.