Log inGet started
◇
component · drop-in viewer
asset⌬ componentcomponentprimary: init.luau·originates fromworld e2fc9693-0…

Ciego

The first boss: five metres of blind bell-priest. Every attack is preceded by the bell that is its head RINGING (a flare and a ripple), so the fight reads by ear.

by◐Catapulta33·posted 9d ago
What it does

umbral.foes.Ciego — El Ciego de la Nave

The first boss: five metres of blind bell-priest. Every attack is preceded by the bell that is its head RINGING (a flare and a ripple), so the fight reads by ear.

state runs ring -> slam | sweep | charge -> recover; a landed charge ends in dazed, the punish window. At half its wounds phase goes to 2 behind a two second crack: the light in the bell turns from turquoise to blood, it stops resting and it gains sonar (three floor rings, answered by being off the ground). On death it spawns recompensa_vuelo_de_la_sal, an umbral.foes.Reward that grants the Vuelo de la Sal through umbral.foes.Awards.

Interface

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

conforms to

zero/source-extract/v2
AssetModel

setState(s: ?) → void

argtypedescription
s?

place( ) → void

ringBell(strength: ?) → void

argtypedescription
strength?

chooseAttack(px: ?, dist: ?) → void

argtypedescription
px?
dist?

awake( ) → void

fireWave( ) → void

spawnReward( ) → void

die( ) → void

update(dt: ?) → void

argtypedescription
dt?

takeHit(damage: ?, dirX: ?) → void

What `umbral.Combat.strike` calls on whatever the Badajo finds. A wound is a number here and a state change in update(); one hit never kills.

argtypedescription
damage?
dirX?

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.

24+items
▣
module · born here
❒asset
# umbral.foes.Sense The only place a foe is allowed to learn anything about Ilva. - `Sense.body()` — the entity twoDKit's motor drives. - `Sense.where(e)` — its position, read defensively. - `Sense.noise()` — `0` silence .. `1` a bell at arm's length, plus where the sound came from. Her feet on wet stone raise it, and so does her bell. - `Sense.bell()` — did her Badajo or her healing ring sound? It reads `umbral.Ilva`'s `swing`, `healing` and the fall of `coro`. - `Sense.hurtPlayer(amount, fromX)` — a wound, through `umbral.Combat` or `umbral.Ilva:takeHit`, falling back to writing `health`. Reports which one answered, `nil` if none could. Blind foes read `noise` and nothing else: they know where a SOUND was, never where she is.
▲ 0↑ born
❒
bundle · born here
❒asset
▲ 0↑ born
▣
module · born here
❒asset
# umbral.foes.Fx The shape a bell makes in the dark, for every foe in this slice. - `Fx.ring(r,g,b)` / `Fx.fire(ring,x,y,maxR,life,strength)` / `Fx.step(ring,dt)` — one flat emissive disc pre-spawned by its owner and re-fired, so a fight never spawns or despawns anything. Emissive rather than lit: the scene's light budget belongs to the creatures. `fx.ring` takes no light. - `Fx.light(parent,x,y,z,r,g,b,radius)` — a point light that exists only to be seen: the crack in a bell, a throat, a halo. - `Fx.set` / `Fx.ease` — writes and damps a light's intensity. - `Fx.glow()` / `Fx.bronze()` — this slice's own materials (`umbral.foes.art.echo_glow`, `umbral.foes.art.bell_bronze`).
▲ 0↑ born
◇
component · born here
❒asset
# umbral.foes.Reward What a boss leaves behind: a fragment of bell, floating, warm. She walks into it and `umbral.foes.Awards.grant(award)` gives her a way of moving. Not a number.
▲ 0↑ born
◐
material · born here
❒asset
▲ 0↑ born
△
mesh · born here
❒asset
▲ 0↑ born
▦
texture · born here
❒asset
▲ 0↑ born
▦
texture · born here
❒asset
▲ 0↑ born
▦
texture · born here
❒asset
▲ 0↑ born

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.