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

Screens

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

Screens

<!-- 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/ui/Screens.component/init.luau SLICE: ui — the screens. Everything on the glass, authored rather than default: the title card the game opens on, and the readout it is played under — the focus prompt the player reads an object with, the one-line objective, the caption band a memory's title and the family's faint lines print on, and what is carried. It is a pure CONSUMER of Core.state — it draws and it decides nothing. The one thing it offers back is `ui.flash`, so a slice that wants a wash over the frame does not have to know how a screen is built. THE SHAPE, which is what the first version got wrong: `ui.registerScreen` takes ONE widget tree, not a list — and a panel (`centralPanel`, `bottomPanel`, `topPanel`, `leftPanel`, `rightPanel`) is a ROOT-ONLY widget, so it has to BE that tree's root. Text lives in a label's `props`, and every visual property lives in its `style`; a `color` put at the top level of a widget is read by nothing. `ui.lastValidation(name)` is the verdict on all of it, and it is what this file is checked against.

titleTree( ) → void

The trees

hudTree(caption: ?, prompt: ?, objective: ?, held: ?) → void

argtypedescription
caption?
prompt?
objective?
held?

registerAll( ) → void

Driving them

setScreen(name: ?, on: ?, key: ?) → void

argtypedescription
name?
on?
key?

renderReadout( ) → void

The readout is rebuilt and written back whenever any of it changes. Writing the whole tree rather than one widget keeps the shape the registration validated — there is no second, subtly different shape to get wrong.

flash(colour: ?, seconds: ?) → void

argtypedescription
colour?
seconds?

say(text: ?, seconds: ?) → void

argtypedescription
text?
seconds?

screens( ) → void

validation( ) → void

awake( ) → 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.

7items
▣
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
backing path · game/ui/Screens.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. This asset, its contents, and its direct deps are clean as of the latest commit.
⌬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.