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

Enemies

What lives in Véspera, and where. The scene calls `Enemies.populate(map, Config)` once during the build; every foe is a `spawnSynced` entity carrying its own component from `umbral/foes/`.

by◐Catapulta33·posted 9d ago
What it does

umbral.Enemies

What lives in Véspera, and where. The scene calls Enemies.populate(map, Config) once during the build; every foe is a spawnSynced entity carrying its own component from umbral/foes/.

FoeWhereWhat it teaches
Penitente CiegoEl Campanario x15, La Nave x80It is blind. It hunts the SOUND of her feet and her bell, never her body. Stand still and walk past behind it.
Ahogado OficianteEl Corredor x33Its chant seals a ring round her. Leaving the ring (dash) or ringing her bell breaks it.
Salinoledges at x61 and x77An enemy above you is a different problem. It clings, it aims, it spits.
Siete Cuerdasx66 and x68.6, two out of phaseUnkillable. It teaches the beat: quiet, tight, cutting.
El Ciego de la Navethe dais, x100The boss. It rings before every attack, cracks at half health, and leaves a way of moving behind.

The damage contract

Every foe exposes a synced health field. Writing it down is a hit — the foe watches it and reacts (staggers, cracks, dies). So Ilva's Badajo can hurt anything here by writing health on the entity it found with its cast, without knowing what it hit. Enemies.hurt(name, amount) does the same by name.

A foe hurts her through umbral.foes.Sense.hurtPlayer(amount, fromX), which calls umbral.Combat or the umbral.Ilva component by whatever name the ilva slice exposes, and falls back to writing health on the body.

SieteCuerdas cannot be killed: a drop in health only tightens its beat.

Sense

umbral.foes.Sense is the only place a foe is allowed to learn anything about Ilva: Sense.noise() (0 silence .. 1 a bell at arm's length, with where it came from), Sense.bell(), Sense.body().

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 · what lives in Véspera and where. The scene calls `Enemies.populate(map, Config)` once, during the build. Every foe is a `spawnSynced` entity carrying its own component out of `umbral/foes/`, so every peer runs the same living things and a rebuild does not duplicate them. Damage contract, for whichever slice owns Ilva: * every foe exposes a synced `health` field. WRITING IT DOWN IS A HIT: the foe watches it and reacts (staggers, cracks, dies). So Ilva's Badajo can hurt anything here without knowing what it hit. * `Enemies.hurt(name, amount)` does the same by name, for a script. * a foe hurts her through `umbral.foes.Sense.hurtPlayer`, which calls `umbral.Combat` or the `umbral.Ilva` component by whatever name they expose, and falls back to writing Ilva's `health`.

roster( ) → void

alive(name: ?) → void

argtypedescription
name?

populate(map: ?, Config: ?) → void

Spawn every foe that is not standing already. Called by the scene build.

argtypedescription
map?
Config?

hurt(name: ?, amount: ?) → void

Wound a foe by name. Any authority may do this (Ilva's Badajo, a script).

argtypedescription
name?
amount?

report( ) → void

What each foe is doing right now, for a HUD, a test or a curious agent.

Sub-parts

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

3items
This part has no composite children. See the Files segment for its leaf payloads.
backing path · umbral/Enemies.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.