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

MapScreen

The map screen. It is drawn from `umbral.Config.MAP`, so every solid the scene builds appears as a room outline, the one-way ledges as hairlines, the bells as turquoise lanterns and the braziers as amber points — the map cannot drift from the rooms it describes.

by◐Catapulta33·posted 9d ago
What it does

umbral.ui.MapScreen

The map screen. It is drawn from umbral.Config.MAP, so every solid the scene builds appears as a room outline, the one-way ledges as hairlines, the bells as turquoise lanterns and the braziers as amber points — the map cannot drift from the rooms it describes.

MapScreen.build({ width, player }) returns the tree with the bone mark at player and the close_map callback on the way back. Opens from the region row of the HUD, and from M.

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 map. Drawn from `umbral.Config.MAP`: every solid the scene builds is a line in the plan, so the map cannot drift from the rooms. Bells are turquoise, braziers amber, and Ilva is the bone mark that moves.

bounds(map: ?) → void

argtypedescription
map?

take(x: ?, y: ?) → void

argtypedescription
x?
y?

build(s: ?) → void

s = { width, height, player = { x, y } }

argtypedescription
s?

px(v: ?) → void

argtypedescription
v?

place(x: ?, y: ?) → void

argtypedescription
x?
y?

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
# umbral.Config The one shared module. Every number UMBRAL obeys and every table it reads lives here so a system never invents its own copy. **Read by:** `scenes/main.scene/build.luau` (which builds the map from `MAP`), `umbral.Art` (region palettes and backdrop depths), `umbral.Ilva` (the `PLAYER` tuning table), `umbral.Enemies` and `umbral.Hud`. ## What it holds | Table | What it is | |---|---| | `PALETTE` | The seven colours the whole game is drawn in, as linear rgb. Void, stone, bronze, turquoise, amber, bone, blood. | | `PLAYER` | Ilva's tuning: health, the Coro's maximum and what fills and spends it, the healing ring, i-frames, the two swings' damage and timing, the Badajo's reach, the echo's radius and duration. | | `REGIONS` | The nine regions: id, display name, the palette tint it leans on, its musical bordón, and the depth band its backdrop sits at. | | `MAP` | The geometry: `solids` (solid rectangles), `oneWay` (jumped up through), `braziers`, `bells`, and the spawn point. | ## Conventions A tile is **one world unit** and the grid is whole units. Gameplay is the plane `z = 0`. Rectangles are `{ x, y, w, h }` with `x, y` the bottom-left corner. Ilva's collision box is `0.625 × 1.25`, so a corridor is at least 3 units high and a doorway at least 2. A bell is named `bell_<name>`; hidden geometry is named `hidden_<anything>`. Those two names are the only contract between the art pass and the echo mechanic. `Config.colour(name)` returns the three channels of a palette entry so a light can be built from a name rather than from numbers repeated in five files.
▲ 0↑ born
▣
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/MapScreen.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.