·
scene · drop-in viewer
main
<!-- zero:scaffolded-readme --> <!-- Replace the line below with what this scene provides and who consumes it, then delete both comment lines. -->
by◐hazelyn1204·posted 1mo ago
What it does
main
<!-- zero:scaffolded-readme --> <!-- Replace the line below with what this scene provides and who consumes it, then delete both comment lines. -->TODO: describe this scene.
Interface
What this asset declares: the schema it conforms to, what it exposes, and the rendered structured payload.
This asset doesn't declare a schema or structured payload.
Sub-parts
Everything contained inside this part. Assets are composite children (clickable cards). Files are leaf payloads. Expand any row to view its source.
143items
▲ 0↑ born
▲ 0↑ born
▲ 0↑ born
▲ 0↑ born
▲ 0↑ born
▲ 0↑ born
▲ 0↑ born
▲ 0↑ born
▲ 0↑ born
▲ 0↑ born
▲ 0↑ born
▲ 0↑ born
▲ 0↑ born
▲ 0↑ born
▲ 0↑ born
# glimmerhollow
The valley Hollowmere stands in, as a raster graph on the terrain family.
A 720 m square of ground at 2 m per cell, shaped in this order:
1. `terrain.ridge` cuts a trench 230 m wide down the +X axis — the valley itself.
2. Two more ridges raise the walls either side of it.
3. `terrain.fbm` lays rolling relief over the whole thing.
4. `terrain.erode` weathers it, so the shapes read as land rather than as noise.
5. `terrain.flatten` levels a shelf on the north bank — the pad the town stands on.
6. `terrain.flatten` sinks a basin at the west end.
7. `terrain.river` carves a channel along the valley floor and runs water down it.
8. `terrain.lake` floods the basin to a level, so the tarn's shore is the
terrain's own contour.
Then four surface masks on slope and height — `crag` on the steep ground, `moss`
on everything gentle, `loam` as noise patches over the moss, and `silt` along the
low ground near the water — written out as a `.terrainData` with the two demo
rock and earth texture sets bound to the first two.
The last node is a `Landscape`, so the graph's output is an entity: a `Terrain`
carrying the heightfield, its water surface and its colliders. It drops into a
scene as a Generator and answers `heightAt` / `slopeAt` / `waterAt` at runtime.
## Inputs
| input | what it does |
|---|---|
| `extent` | the rect's side, in metres |
| `relief` | amplitude of the rolling noise |
| `wallHeight` | how high the valley walls rise |
| `floorCut` | how deep the trench cuts — negative is down |
| `lakeLevel` | the world Y the tarn floods to |
| `weather` | droplet erosion iterations; 0 leaves the shaping raw |
`floorCut` and `lakeLevel` have to agree: raise the floor above the lake level
and the tarn drains into whatever hollow is left, because the fill only reaches
ground the seed actually connects to.
▲ 0↑ born
▲ 0↑ born
▲ 0↑ born
▲ 0↑ born
▲ 0↑ born
▲ 0↑ born
▲ 0↑ born
▲ 0↑ born
▲ 0↑ born
▲ 0↑ born
▲ 0↑ born
# glimmercap
A bioluminescent mushroom, and a stand of them.
The cap is one cubic Bézier arc revolved around the stalk's own axis, which is
what makes it a parasol rather than a dome — the profile flares out and droops
at the rim the way a real cap does. The stalk is a capsule joined under it.
Two outputs, from one description of what a mushroom IS:
- **patch** — a stand scattered over a disc, each copy turned, tilted and scaled
by a seeded hash, merged into a single geometry. This is the one you cover
ground with; it drops into a scene as one Generator entity.
- **single** — one mushroom at the origin, for placing by hand on a machine, a
wall or a catwalk.
The surface is a self-lit translucent PBR material. It is deliberately kept well
under full brightness: the glow that actually lights the ground comes from an
`EmissiveSource` on the entity holding the patch, so a stand can light a wide
area without the caps blowing out to white.
## Inputs
| input | what it does |
|---|---|
| `stemHeight`, `stemRadius` | the stalk |
| `crownY` | how high the cap's crown sits — the top of the parasol |
| `shoulderX`, `shoulderY` | the cap's first control point: how flat the top stays |
| `bellyX`, `bellyY` | the second control point: how far the cap bulges |
| `rimX`, `rimY` | the rim — how wide and how low the cap flares |
| `radius`, `count` | the stand: how far it spreads, how many |
| `scaleMin`, `scaleMax` | the size range each mushroom draws |
| `tilt` | how far off upright each may lean, in degrees |
| `seed` | reshuffles the whole scatter |
The four cap control points are the interesting ones. Widening `rimX` and
lowering `rimY` gives a flat parasol; raising `shoulderY` gives a domed one.
## Where it is used
`scenes/main.scene/build.luau` places stands of it around Hollowmere and on the
machinery. The same graph shapes a hero mushroom on the tower face at three
times the scale.
▲ 0↑ born
▲ 0↑ born
▲ 0↑ born
▲ 0↑ born
backing path · scenes/main.scene
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
+ 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.