Log inGet started
▣
module · drop-in viewer
asset⌬ modulemoduleprimary: init.luau·originates fromworld b49f5634-1…▲6problems

nring

A module script.

byzero-proxy @ DESKTOP-DB3UJOJ·posted 4mo ago
What it does

nring

A module script.

Interface

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

conforms to

zero/source-extract/v2

nring: Nürburgring Drive port library (Phase 1). Faithful Luau port of esc5221/drive-game: track geometry + analytic surface queries, 240 Hz vehicle physics, DEM terrain, lap timing, mesh builders.

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.

182+items
◐
material · born here
❒asset
▲ 0↑ born
◐
material · born here
❒asset
▲ 0↑ born
◐
material · born here
❒asset
▲ 0↑ born
▦
texture · born here
❒asset
▲ 0↑ born
▦
texture · born here
❒asset
▲ 0↑ born
◐
material · born here
❒asset
# [name] One-paragraph description of what surface look this material produces and where it's intended to be used. ## Shader Name the shader bound in `mat.yaml::shader` (e.g. `@builtin/shaders/standard` or a custom shader path). ## Inputs - `floats.<name>` — value, units, valid range. - `colors.<name>` — what colour channel/term it drives. - `textures.<name>` — what map slot it fills. Add more `floats:` / `colors:` / `textures:` keys as the shader exposes them. ## Usage ```luau Material.Apply(entityId, "[name]") ```
▲ 0↑ born
▦
texture · born here
❒asset
▲ 0↑ born
▦
texture · born here
❒asset
▲ 0↑ born
▦
texture · born here
❒asset
▲ 0↑ born
▦
texture · born here
❒asset
▲ 0↑ born
▦
texture · born here
❒asset
▲ 0↑ born
▦
texture · born here
❒asset
▲ 0↑ born
▦
texture · born here
❒asset
▲ 0↑ born
◇
component · born here
❒asset
# ForestDetail Quality-tier density switch for the Nürburgring Drive Eifel forest. Attach it to the forest root entity `nring_tree_forest` (built by `nring.forest`). The root's children `nring_tree_<near|far>_<core|mid|high>` each carry a `Population` component; this component enables the layers the tier affords (low: core, medium: core + mid, high: all) and re-reads `renderer.qualityTier()` once a second so a graphics setting applies live. `tierOverride` forces a tier.
▲ 0↑ born
▦
texture · born here
❒asset
▲ 0↑ born
◇
component · born here
❒asset
# ForestPart Data-only marker for one piece of the Nürburgring Drive Eifel forest: a 200 m LOD cell (the LOD0 and LOD1 twins of every near-band tree in it) or a denser proxy / far density layer. It lives on a child of the forest root `nring_tree_forest` and holds the `.population` as a statically pinned asset field; the root's `ForestDetail` component reads it and draws it locally per device (cells near the camera, layers by quality tier). It draws nothing itself and needs no sibling components.
▲ 0↑ born
▦
texture · born here
❒asset
▲ 0↑ born
▦
texture · born here
❒asset
▲ 0↑ born
▦
texture · born here
❒asset
▲ 0↑ born
▦
texture · born here
❒asset
▲ 0↑ born
◐
material · born here
❒asset
▲ 0↑ born
◐
material · born here
❒asset
▲ 0↑ born
▦
texture · born here
❒asset
▲ 0↑ born
▦
texture · born here
❒asset
▲ 0↑ born
▦
texture · born here
❒asset
▲ 0↑ born
◐
material · born here
❒asset
▲ 0↑ born
◇
component · born here
❒asset
# TracksideDetail Draws the Nordschleife trackside detail that is gated by quality tier, locally on each device: the race-weekend spectators (instanced `ts_crowd` billboards) and the small camp clutter. It sits on `nring_ts_detail` under the `nring_trackside` root and holds three `.population` refs written by `nring.trackside`: `low` (drawn at every tier), `medium` (medium and high) and `high` (high only). It follows `renderer.qualityTier()` (or `tierOverride`), draws nothing into shadows and replicates nothing. Needs no sibling components. `refresh()` redraws after a rebuild.
▲ 0↑ born
▦
texture · born here
❒asset
▲ 0↑ born
backing path · nring.module

Problems

Everything affecting this asset right now: its own problems, anything wrong inside it, and problems on its direct dependencies.

These counts cover only the parts this page shows. Problems on the parts it leaves out are not counted here.

6+problems

Inside

6 problems across 3 items
▲
dep.dangling.checksum_drift · L7
dep `nring.terrain` -> 303121b7-35ec-44a9-b9c9-5ed9dc8a6916 no longer resolves (checksum_drift)
▲
dep.dangling.checksum_drift · L8
dep `nring.physics` -> 146e9b90-0094-41b9-8f64-7540ca2b5ccb no longer resolves (checksum_drift)
▲
dep.dangling.checksum_drift · L12
dep `nring.buildmesh` -> c1f6fc58-6cef-4e25-96f0-49e6be61ef4c no longer resolves (checksum_drift)
▲
dep.dangling.checksum_drift · L13
dep `nring.track_data` -> 6f797dd1-8485-48ba-8d59-ea8c21f52b3e no longer resolves (checksum_drift)
▲
dep.dangling.checksum_drift · L4
dep `nring.fixtures.track_queries` -> d66a271d-e2af-4e75-889d-713b2241e1b6 no longer resolves (checksum_drift)
▲
dep.dangling.checksum_drift · L3
dep `nring.fixtures.vmath` -> f9af81c7-fc54-4e0f-a1f5-cf78d24ab840 no longer resolves (checksum_drift)
⌬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.