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

Atmos

The medium of Véspera: no sky, no sun, deep water and fog.

by◐Catapulta33·posted 9d ago
What it does

Atmos

The medium of Véspera: no sky, no sun, deep water and fog.

Atmos.apply(root, Config, M) is called from umbral.Art.decorate during the scene build. Every step is written again rather than stacked, so a rebuild is safe.

  • Sky and light — the sky is turned off outright (Skybox kind="none"), so the background is the deep-water clear colour rather than the engine's fallback daylight; the ambient and the key are re-stated on the sea's own terms.
  • Fog — exponential height fog, cold blue-green, dense enough that the middle distance dissolves and the far band reads as light rather than as geometry.
  • Post — the display transform is pinned (curve 3, exposure 1.0), bloom is registered on the scene layer with its threshold held above the limestone so only the bell's crack, the sea-lamps and the braziers bloom, and a vignette closes the frame in.
  • Salt and dust — three umbral.art.Motes fields (the tower's falling salt, the nave's, and the amber dust that catches the braziers) drifting on slow sines.

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 · Atmos — the medium, not the objects. Véspera is underwater three hundred years after it stopped sinking. That means: no sky, no sun, deep blue-black air, fog that eats the middle distance, bloom on the only two saturated lights in the world, and salt and dust drifting through all of it. Split in two because the engine divides it that way: `Atmos.apply(root, Config)` runs in the scene build and places entities (the salt and dust fields). `Atmos.runtime()` runs when the scene loads, from `umbral.art.Atmosphere`, and sets the fog and the post-process chain — runtime state the build cannot hold. Every step is written again rather than stacked.

attempt(label: ?, fn: ?) → void

argtypedescription
label?
fn?

light( ) → void

The scene carries its own `sky` entity with the Skybox turned off, which is what stops the engine's bright fallback sky from lighting the whole level pale blue from every direction. This only re-states the light the sea gives.

fog( ) → void

hasPass(name: ?) → void

argtypedescription
name?

ensurePass(name: ?, shader: ?, opts: ?, props: ?) → void

argtypedescription
name?
shader?
opts?
props?

post( ) → void

motes(root: ?) → void

argtypedescription
root?

apply(root: ?, Config: ?, M: ?) → void

Build-time: the things that are entities.

argtypedescription
root?
Config?
M?

runtime( ) → void

Load-time: the things that are runtime state.

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.

7+items
◇
component · born here
❒asset
# Motes A field of small emissive flecks drifting through the air — the salt and the dust of Véspera. Attach it to an empty entity placed where the field should be centred; it spawns its own `mote_*` children on `awake` and moves them on three slow sines in `update`. Re-attaching gathers the children already present rather than building a second field, so a hot reload does not double it. Fields: `count`, `width`, `height`, `depth` (the extent it fills), `size`, `speed`, `seed` (arrangement), `colorR/G/B` and `glow` (how hard the evidence blooms). It needs no sibling component; give it a parent under the scene's map. `umbral.Atmos` places three of them: the tower's falling salt, the nave's, and the amber dust that catches the braziers.
▲ 0↑ born
backing path · umbral/Atmos.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.