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

Echo

The wire between a rung bell and the light it throws. `umbral.Combat.ring` announces every bell that is struck; `umbral.Art.echoPulse` knows how to draw the ring. `Echo.install()` joins the two once per scene, at load — `umbral.art.EchoRing` requires this module when the componen…

by◐Catapulta33·posted 10d ago
What it does

Echo

The wire between a rung bell and the light it throws. umbral.Combat.ring announces every bell that is struck; umbral.Art.echoPulse knows how to draw the ring. Echo.install() joins the two once per scene, at load — umbral.art.EchoRing requires this module when the component loads — so a bell rung from the combat path, from Ilva, or from anything else in the world spawns an echo without the gameplay code ever naming the art.

Echo.ready() answers whether the wire is in place. Installing twice is a no-op, thanks to the echo_bus marker entity it leaves in the scene.

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 · Echo — the wire between a rung bell and the light it throws. `umbral.Combat.ring` announces every bell that is struck; `umbral.Art` knows how to draw the ring. This module joins the two once, when the world loads: after `install` has run, ringing a bell anywhere in Véspera spawns an echo without the combat path knowing anything about art. `umbral.art.EchoRing` requires this file at load, so the wire is in place before the first bell is touched.

ready( ) → boolean

!desc Whether a bell struck anywhere already reaches the echo's art.

install( ) → boolean

!desc Join the echo bus: `Combat.ring` -> `Art.echoPulse`. Idempotent.

Sub-parts

Everything contained inside this part. Assets are composite children (clickable cards). Files are leaf payloads. Expand any row to view its source.

Showing up to 3 levels deep. Open a part to see what it holds further down.

11+items
▣
module · born here
❒asset
# Art The architecture and decoration of Véspera, built at scene load. `Art.decorate(map, Config)` is called once by `scenes/main.scene/build.luau`, after the map's solids, braziers and bells are placed. It hangs everything under a single `art_root` entity, dropping the previous one first, so a scene that rebuilds on every write lands the same content once. What it builds: - **The three depth bands** — a far card at z=-36 (the drowned city), silhouette arches at z=-26 separating it from the middle card, the middle card at z=-18, and the real arcades at z=-9 in front of both. - **The near silhouettes** at z=+2.5 — columns and hanging chains the frame is seen through. - **El Campanario** — two tiers of blind arcading, corbels under every climbing ledge, wall sconces with flame, chains from the vault, banners. - **La Nave de las Cuerdas** — an arcade on the play plane's shoulder, vault ribs, the jellyfish of cold light adrift above the water, candle ledges, rubble. - **The props the map names** — each brazier's plan-pass cube is replaced by the generated copper bowl while its amber light is kept; each bell is replaced by the generated cracked bronze bell and given a black-oak yoke, iron straps and the chain that carries it into the dark. Adds no colliders: the play plane stays exactly what `umbral.Config.MAP` states. `Art.echoPulse(x, y, radius)` is the echo's visible half — a ring of turquoise light leaving a struck bell, carried by `umbral.art.EchoRing`. `ilva` calls it if it is there; the game runs without it.
▲ 0↑ born
▣
module · born here
❒asset
# umbral.Combat The combat core: everything the Badajo obeys, in one place, so the enemy, HUD and progression slices read the same numbers instead of three copies of them. **Called by:** `umbral.Ilva` (the swings, the echo, the ladder). Read by the enemies slice for `takeHit` and the HUD slice for nothing at all — the HUD reads `umbral.Ilva`'s public fields. ## What it exports | Name | What | |---|---| | `Combat.SWING` | `light` and `heavy`: damage, whole-swing time, `chainFrom`, `hitAt`, reach, height, all from `Config.PLAYER`. | | `Combat.CORO_PER_HIT` / `CORO_PER_HEAL` / `HEAL_AMOUNT` / `HEAL_TIME` / `INVULN` / `KNOCKBACK` | The Coro economy and the feel of taking a blow. | | `Combat.ECHO_TIME` / `ECHO_RADIUS` | How long hidden geometry stays lit, and how far a bell's echo reaches. | | `Combat.ABILITIES`, `Combat.LADDER` | The movement verbs as data: `dash`, `doubleJump`, `wallJump`, `glide`, all locked at the start. | | `Combat.unlock(id)` / `Combat.lock(id)` / `Combat.unlocked(id)` / `Combat.onUnlock(fn)` | The ladder. `umbral.Ilva` mirrors it onto the motor, so a region handing her a verb is one call. | | `Combat.strike(cx, cy, hw, hh, damage, dirX, skip)` | Resolve a hit box. Returns `landed, rung`. | | `Combat.ringNearest(x, y, radius)` | Ring the closest `bell_` entity in reach. Returns its bare name. | | `Combat.setHiddenVisible(on)` | Show or hide every `hidden_` entity. | | `Combat.registerScheme()` | Register controlsKit's `umbral` scheme: platformer + attack / echo / heal, on keyboard, gamepad and touch. | ## The two conventions other slices use - **Anything a swing can hurt** carries a component with a `takeHit` method, called as `comp:takeHit(damage, dirX)`. Nothing registers and nothing is listed: `strike` finds it by reflection over the scene, so an enemy written tomorrow is hittable the moment it exists. - **Hidden geometry** is any entity named `hidden_<anything>`; **a bell** is any entity named `bell_<name>`. These are the spec's words, not a list this module holds.
▲ 0↑ born
backing path · umbral/art/Echo.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 on this asset or on the parts this page shows. Parts it leaves out are not counted here.
⌬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.