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

TitleScreen

The title screen, from `references/raw/title.texture/title.png`.

by◐Catapulta33·posted 9d ago
What it does

umbral.ui.TitleScreen

The title screen, from references/raw/title.texture/title.png.

TitleScreen.build({ width, optionsOpen }) returns the tree:

  • UMBRAL, drawn as SVG text in EB Garamond with a bronze gradient, a dark engraved offset and a turquoise halo, over a hairline and the subtitle BAJO EL MAR, ALGUIEN SIGUE LLAMANDO in wide-tracked small caps.
  • The drowned bell hanging in the shaft of turquoise light, its crack lit, the water line under it and the room blacking out at the edges.
  • Filigree corners mirrored on all four, and the menu down the left — NUEVA PARTIDA, OPCIONES, SALIR — each a serif caps row with a bronze gem in front of it, sliding in after the wordmark.
  • optionsOpen adds the controls panel, listing what the game binds on keyboard.

Callbacks are the row ids: title_new, title_options, title_quit; umbral.Hud handles them.

Interface

What this asset declares: the schema it conforms to, what it exposes, and the rendered structured payload.

conforms to

zero/source-extract/v2

UMBRAL · the title screen. From `references/raw/title.texture/title.png`: UMBRAL in worn bronze serif, the subtitle under it, the drowned bell hanging in a turquoise shaft of water, filigree in the corners and the menu down the left. Every box is placed in numbers computed from the canvas the caller passes, because an offset given as a percentage does not resolve here: a layer placed at "15%" lands in the flex flow instead of where it was meant to sit.

build(s: ?) → void

s = { width, height, optionsOpen }

argtypedescription
s?

px(v: ?) → void

argtypedescription
v?

layer(x: ?, y: ?, w: ?, h: ?, extra: ?) → void

argtypedescription
x?
y?
w?
h?
extra?

menuRow(text: ?, id: ?, delay: ?) → void

argtypedescription
text?
id?
delay?

optionsPanel( ) → 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
# umbral.ui.Theme The palette, the type and the drawn furniture every UMBRAL screen is built from. **Used by:** `umbral.ui.HudScreen`, `umbral.ui.TitleScreen`, `umbral.ui.MapScreen`, `umbral.Hud`. - `Theme.SERIF` — `"EB Garamond"`, the one face the game sets its type in. - `Theme.C` — hex copies of `umbral.Config.PALETTE`, lifted for legibility over moving water. - `Theme.caps(text, size, color)` — a small-caps serif label with the tracking and shadow the reference uses for VIDA and CORO. - `Theme.bar{ pct, tone, width, height, ticks }` — the tapered bronze-cased bar; `tone` is `"vida"`, `"coro"` or `"blood"`, and `ticks` divides the health bar into its bell fragments. - `Theme.emblem(size)` — the bell medallion at the head of the HUD, drawn in SVG. - `Theme.corner(flip, size)` — one mirrored filigree corner of the title frame. - `Theme.rule`, `Theme.diamond` — the hairlines and gem glyphs the rules are punctuated by. Nothing here holds state, so the screens rebuild freely from it.
▲ 0↑ born
backing path · umbral/ui/TitleScreen.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.