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

Play

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

by◐niharrk24·posted 1mo ago
What it does

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/v2

game/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.

ModelBoxCollider

nearestUsable( ) → void

Focus

setFocus(spec: ?) → void

argtypedescription
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

argtypedescription
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.

12+items
▣
module · born here
❒asset
# core <!-- 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
·
inputmap · born here
❒asset
# gameplay The one control scheme **The House That Remembers** adds on top of whatever the player's camera rig and avatar already activate. It declares a single control, `interact`, and nothing else — looking and walking belong to the first-person camera and the character controller, and input maps compose rather than override, so this one sits alongside them. | Control | Label | Kind | Keyboard | Gamepad | Touch | |---|---|---|---|---|---| | `interact` | Interact | button | `E` | south face button | a large labelled button, lower right | ## What it is for `interact` is the whole of the game's input. Press it and the play slice uses whatever it is currently in focus — the keepsake you are standing in front of, the door you have walked up to, the drawer the brass key opens — and while a memory is running it is what lets the room go. ## What kind of world it suits A first-person exploration or narrative game where the player walks a place and touches things: `fps`, `exploration`, `narrative`, `mystery`, `single-player`. It is deliberately minimal — one button — because everything else the player does is movement and looking, and those come from the engine's own first-person rig rather than from here. ## Group `player`. A menu that stands the `player` group down takes Interact with it and nothing else, which is what a pause card needs.
▲ 0↑ born
·
inputbinding · born here
❒asset
# interact The single control of **The House That Remembers**. A press edge, bound on all three device classes so no one is left out: | Class | Binding | |---|---| | Keyboard and mouse | `E` | | Gamepad | the south face button (A on Xbox, Cross on PlayStation, B on Nintendo) | | Touch | a large labelled button in the lower right zone | ## What it does A press reaches the play slice's focus system: whatever is currently in focus — a keepsake that remembers, a door, a locked drawer — has its `onUse` called. The prompt the player reads (`E · REMEMBER · Family Photograph`) is drawn from the same focus, so the button and the label always agree. The button is marked `large` with a low `priority`, because in a game with one button that button should be the one the eye finds first on a phone.
▲ 0↑ born
backing path · game/play/Play.component

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

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.