Play
<!-- zero:scaffolded-readme --> <!-- Replace the line below with what this component provides and who consumes it, then delete both comment lines. -->
Play
<!-- 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/v2game/play/Play.component/init.luau SLICE: play — the rules. This is what makes the thing a game rather than a scene. It owns: * FOCUS — which thing the player is standing in front of, chosen from Core.interactables. Every other slice REGISTERS what it owns; none of them knows this file exists, and this file implements none of them. * INTERACT — E (the `interact` control) calls the focused spec's own `onUse`. That is the whole implementation. * THE SEQUENCE — the fourteen steps, advanced off state and events. * THE LOCKS — the sideboard drawer and the boarded door in the basement, each gated on an item, each opening onto the next step. * THE DOOR LEAVES — every doorway the shell left a hole for gets a leaf, hinged at one edge, which swings when used.
nearestUsable( ) → void
Focus
setFocus(spec: ?) → void
| arg | type | description |
|---|---|---|
| spec | ? |
interact( ) → void
Interaction
buildDoors( ) → void
enabled( ) → void
onUse( ) → void
registerLocks( ) → void
The locks
enabled( ) → void
onUse( ) → void
enabled( ) → void
onUse( ) → void
enabled( ) → void
onUse( ) → void
advance( ) → void
The sequence Advanced off what is actually true, not off a script: which room the player is in, what is in focus, what has been picked up, and what the memory slice has announced. Every one of these is idempotent.
wire( ) → void
Lifecycle
awake( ) → void
focus( ) → void
start( ) → void
update(dt: ?) → void
| arg | type | description |
|---|---|---|
| dt | ? |
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.
Showing up to 3 levels deep. Open a part to see what it holds further down.
Problems
Everything affecting this asset right now: its own problems, anything wrong inside it, and problems on its direct dependencies.
agent_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.