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

screens

The `game.screens` module manages all user interface and visual displays in the game "LAST CARRIAGE: EVACUATION." This includes the main menu, opening cinematics, the heads-up display (HUD), in-game documents, and both the success and failure ending sequences. Other game slices,…

by◐chefcho·posted 2d ago
What it does

screens

The game.screens module manages all user interface and visual displays in the game "LAST CARRIAGE: EVACUATION." This includes the main menu, opening cinematics, the heads-up display (HUD), in-game documents, and both the success and failure ending sequences. Other game slices, such as game.core (to update HUD elements) or game.survival (to display documents), will call this module to present information or transition between different screen states.

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/screens.module — every screen between the player and the station. SLICE: screens. Contract: start(ctx), update(dt), onPlayer(player), stop(). What is here: lc_title the menu, over the tunnel-mouth key art lc_cine the opening cinematic: the blast seen from inside the carriage lc_hud the in-play HUD — objective, dust, what is carried lc_doc the document reader, a page of what Team Four left behind lc_end both endings, on the same cold tally The phase of the run lives in Core.state.phase and moves intro -> playing -> escaped | died. This module drives it, and follows it if another slice moves it. Every screen is registered from this module and driven by its own callback environment (`ui.registerCallbackEnv`), because a slice module is not a component instance and has no `onCallback` of its own to be called.

abs(l: ?, t: ?, w: ?, h: ?, extra: ?) → void

Small builders. A node is { type, props, style, children }.

argtypedescription
l?
t?
w?
h?
extra?

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

argtypedescription
text?
style?
props?

V(style: ?, children: ?, props: ?) → void

argtypedescription
style?
children?
props?

H(style: ?, children: ?, props: ?) → void

argtypedescription
style?
children?
props?

Spacer(flex: ?) → void

argtypedescription
flex?

anim(keyframes: ?, duration: ?, delay: ?, easing: ?, iter: ?) → void

argtypedescription
keyframes?
duration?
delay?
easing?
iter?

fadeIn(duration: ?, delay: ?, fromY: ?) → void

argtypedescription
duration?
delay?
fromY?

loop(frames: ?, duration: ?, delay: ?) → void

argtypedescription
frames?
duration?
delay?

pad(n: ?) → void

argtypedescription
n?

fmtClock(seconds: ?) → void

argtypedescription
seconds?

nowSeconds( ) → void

titleScreen( ) → void

The title screen — the menu over the tunnel-mouth key art.

letterbox( ) → void

The opening cinematic — the blast, from inside the carriage.

caption(text: ?, delay: ?, color: ?) → void

argtypedescription
text?
delay?
color?

skipHint( ) → void

cinePlate(tex: ?, extraStyle: ?, filter: ?) → void

argtypedescription
tex?
extraStyle?
filter?

cineTree(beat: ?) → void

argtypedescription
beat?

inventoryChips( ) → void

The HUD. Corners only: the middle of the frame stays the game's.

dustTone(pct: ?) → void

argtypedescription
pct?

hudTree( ) → void

hudSignature( ) → void

docById(id: ?) → void

The document reader — a page of what Team Four left behind.

argtypedescription
id?

docIndex(id: ?) → void

argtypedescription
id?

docBodyLines(body: ?) → void

argtypedescription
body?

docScreen( ) → void

tallyRow(name: ?, value: ?, tone: ?) → void

The endings — one cold tally, two headlines.

argtypedescription
name?
value?
tone?

endingScreen(which: ?) → void

argtypedescription
which?

register(name: ?, tree: ?, layer: ?) → void

Showing and hiding. Every call is guarded: a screen that fails to register must not take the game down.

argtypedescription
name?
tree?
layer?

show(name: ?) → void

argtypedescription
name?

hide(name: ?) → void

argtypedescription
name?

refresh(name: ?, tree: ?) → void

argtypedescription
name?
tree?

toast(text: ?, tone: ?) → void

Flow: title -> cinematic -> playing -> escaped | died

argtypedescription
text?
tone?

showTitle( ) → void

beginCinematic( ) → void

endCinematic( ) → void

showEnding(which: ?) → void

argtypedescription
which?

openDoc(payload: ?) → void

argtypedescription
payload?

closeDoc( ) → void

beginAgain( ) → void

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

argtypedescription
id?
data?

hook( ) → void

The contract.

dispatch(evt: ?, payload: ?) → void

argtypedescription
evt?
payload?

onEvent(evt: ?, payload: ?) → void

argtypedescription
evt?
payload?

start(ctx: ?) → void

argtypedescription
ctx?

update(dt: ?) → void

argtypedescription
dt?

onPlayer(player: ?) → void

argtypedescription
player?

stop( ) → 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 The `game.core` module defines the shared constants, rules, and global state for the game "LAST CARRIAGE: EVACUATION." It provides a central source of truth for game data like world layout, noise levels, item definitions, and narrative documents. All other game slices (`game.atmos`, `game.player`, etc.) require this module to access consistent game parameters and to interact with the shared game state and event bus.
▲ 0↑ born
backing path · game/screens.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.