Story
<!-- zero:scaffolded-readme --> <!-- Replace the line below with what this component provides and who consumes it, then delete both comment lines. -->
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/v2game/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).
y(n: ?) → void
| arg | type | description |
|---|---|---|
| n | ? |
storyRoot( ) → void
place(entry: ?) → void
Put one entry into its storey, if that storey is standing.
| arg | type | description |
|---|---|---|
| entry | ? |
say(text: ?) → void
HANDLERS
| arg | type | description |
|---|---|---|
| text | ? |
read(title: ?, body: ?) → void
| arg | type | description |
|---|---|---|
| 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
| arg | type | description |
|---|---|---|
| ... | ? |
endRun(id: ?) → void
| arg | type | description |
|---|---|---|
| id | ? |
handle(entry: ?, ev: ?) → void
| arg | type | description |
|---|---|---|
| entry | ? | |
| ev | ? |
wire( ) → void
awake( ) → void
LIFECYCLE
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.
Problems
Everything affecting this asset right now: its own problems, anything wrong inside it, and problems on its direct dependencies.
Inside
2 problems across 1 itemagent_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.