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

Story

<!-- 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

Story

<!-- 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/Story.component/init.luau THE MISSING FLOOR — what is in the building, and what it means. Every readable thing, every carryable thing, the six investigation stages, the puzzles and the five endings. It is DATA plus the rules over it: the table below is the whole of the building's contents, and the handlers below turn touching one into state. It places its content LAZILY. The world builds a storey the first time anybody needs it, so this waits for a storey's root to exist and then puts that storey's things in it — which means the notes and keys arrive with the floor and cost nothing until you go there. THE CHAIN, so it is legible in one place: the desk key (under the desk) -> the desk drawer -> the 703 key the 703 key -> 703 -> the photograph, the cassette the plant room on 10 -> the blueprint, the watch, the fuse box the abandoned flat on 9 -> the access card -> the eleventh floor the eleventh floor -> the coin, and what happened to Maya Voss ENDINGS: escape (the front doors, early), the loop (the front doors with the coin and the photograph), the truth (Maya's last page, on 11), the eleventh floor (staying up there too long), and the shape of the building (the desk computer with the whole record in hand).

ModelBoxColliderInteractable

y(n: ?) → void

argtypedescription
n?

storyRoot( ) → void

place(entry: ?) → void

Put one entry into its storey, if that storey is standing.

argtypedescription
entry?

say(text: ?) → void

HANDLERS

argtypedescription
text?

read(title: ?, body: ?) → void

argtypedescription
title?
body?

evaluateStage( ) → void

The stage rule: a stage follows from what is in the journal, not from a script. Any clue can move it.

all(...: ?) → void

argtypedescription
...?

endRun(id: ?) → void

argtypedescription
id?

handle(entry: ?, ev: ?) → void

argtypedescription
entry?
ev?

wire( ) → void

awake( ) → void

LIFECYCLE

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.

27items
◇
component · born here
❒asset
# interact <!-- 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.
▲ 0↑ born
◐
material · born here
❒asset
▲ 0↑ born
◐
material · born here
❒asset
▲ 0↑ born
◐
material · born here
❒asset
▲ 0↑ born
◐
material · born here
❒asset
▲ 0↑ born
◐
material · born here
❒asset
▲ 0↑ born
·
png · born here
❒asset
▲ 0↑ born
·
png · born here
❒asset
▲ 0↑ born
·
png · born here
❒asset
▲ 0↑ born
·
png · born here
❒asset
▲ 0↑ born
·
png · born here
❒asset
▲ 0↑ born

Problems

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

2problems

Inside

2 problems across 1 item
●
dep.unresolved · L46
could not resolve `./core.module`
●
dep.unresolved · L47
could not resolve `./world.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.