Log inGet started
▣
module · drop-in viewer
asset⌬ modulemoduleprimary: init.luau·originates fromworld 07a07267-3…

menu

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

by◐lolboy21·posted 1mo ago
What it does

menu

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

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.menu — every screen the game has, and the phase each belongs to. The look is `design/references/title-screen.png`: a condensed heavy title in the upper left, a hairline rule under it, a letterspaced strap-line, and a left-aligned stack of thin-bordered entries each carrying an amber accent on its leading edge — over a live 3-D backdrop that is the actual district, not a painted image. ONE SCREEN PER PAGE, and exactly one visible at a time. A screen per page rather than one screen rebuilt with a different body: a rebuild is a new tree every time the phase moves, and the engine's UI is declarative, so a page that exists in its own screen keeps its own layout and only the visibility changes. The phase is the only input to which page shows. Nothing here decides when the match starts — it asks `Core.setPhase` and the phase does the rest, so the menu can never disagree with the game about what is happening.

L(id: ?, text: ?, style: ?) → void

Builders

argtypedescription
id?
text?
style?

col(style: ?, children: ?) → void

argtypedescription
style?
children?

row(style: ?, children: ?) → void

argtypedescription
style?
children?

abs(l: ?, t: ?, r: ?, b: ?, extra: ?) → void

argtypedescription
l?
t?
r?
b?
extra?

backdrop(children: ?) → void

The shell every full-screen menu page shares: the district shows through the right two thirds and the page's own type sits on a graded left. The page's block is placed by FLOW — centred vertically, pinned left by a large padding — rather than by an absolutely positioned box. An absolute child of this root that states one edge and not the opposite one is stretched on the unstated axis, and a menu block stretched to 1500 points tall is a menu block that is clipped off the screen entirely.

argtypedescription
children?

entry(id: ?, text: ?, action: ?, suffix: ?) → void

One entry in a stack: the accent rule, then the button. The rule is the reference's leading edge, and it is a sibling rather than a border because a border on one side of a button is not a thing this renderer draws.

argtypedescription
id?
text?
action?
suffix?

heading(text: ?, sub: ?) → void

argtypedescription
text?
sub?

sliderRow(id: ?, label: ?, value: ?, min: ?, max: ?, onChange: ?) → void

argtypedescription
id?
label?
value?
min?
max?
onChange?

mainPage( ) → void

Pages

loadoutPage( ) → void

pickList(title: ?, slot: ?) → void

argtypedescription
title?
slot?

settingsPage( ) → void

audioPage( ) → void

controlsPage( ) → void

The bindings, read off the input map the game actually runs on rather than retyped — a controls screen that disagrees with the controls is worse than none.

pausePage( ) → void

loadingPage(progress: ?, status: ?) → void

The load screen. Its bar is driven by REAL work — the number of slices the scene has managed to attach — so it cannot finish before the game exists, and it cannot sit at 90% for a minute while nothing happens.

argtypedescription
progress?
status?

stepCamera(dt: ?) → void

The main-menu camera lives in a slow drift down the street the district was built around, so the backdrop moves between two captures a second apart the way the reference's does.

argtypedescription
dt?

wantedScreen( ) → void

Which screen the current phase wants on the glass. Exactly one.

sync( ) → void

treeFor(name: ?) → void

Rebuild one page's tree. Called on show and whenever its data changes.

argtypedescription
name?

applySetting(name: ?, value: ?) → void

Callbacks

argtypedescription
name?
value?

onCallback(id: ?, data: ?) → void

argtypedescription
id?
data?

build( ) → void

Lifecycle

update(dt: ?) → void

argtypedescription
dt?

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

11items
▣
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
▣
module · born here
❒asset
# hud <!-- 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/menu.module

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.