Log inGet started
·
toolbox · drop-in viewer
asset⌬ toolboxtoolbox·originates fromworld a333e7c2-f…

firstLightMaps

The circuit catalogue lives at rainline/maps/catalog.module/init.luau. It defines five independent closed layouts, names, descriptions, biome and road half-width. rainline.shared builds their smooth paths, and rainline.visuals.circuit produces the road, barriers, details and ligh…

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

FIRST LIGHT map authoring

The circuit catalogue lives at rainline/maps/catalog.module/init.luau. It defines five independent closed layouts, names, descriptions, biome and road half-width. rainline.shared builds their smooth paths, and rainline.visuals.circuit produces the road, barriers, details and lighting.

Use in edit mode:

  1. tools.use("firstLightMaps","inspect",4) — inspect length, bounds and source points.
  2. tools.use("firstLightMaps","setLayout",4,points) — save an ordered array of {x,z} points. Use 6–80 points at least24m apart. Coordinates exclude the circuit's world offset. Crossing control polygons are rejected.
  3. tools.use("firstLightMaps","rebuild",4) — switch to that circuit as the root editing scene, rebuild and save it.
  4. tools.use("scene","load","scenes.rainline") — return to the multiplayer game.

Always inspect the smoothed result from above and road height. Polygon validation does not prove spline/road clearance. Rebuild after changing catalogue parameters or circuit set dressing. Preserve literal references when extending StageLoader with a new stage. The menu paginates the catalogue automatically. Stage content stays unloaded until selected.

Black Quarry uses biome3 rock cuts without the forest canopy; Saltspan uses biome1 with an open-water viaduct instead of an infield. Their structural detail is authored in circuit.sceneModule, alongside the reusable apron props, tar seams, drainage and road fixtures.

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.

Showing up to 3 levels deep. Open a part to see what it holds further down.

20+items
·
tool · born here
❒asset
Returns circuit names, lengths, bounds, sampled geometry counts and source control points from rainline.maps.catalog. Used before editing or rebuilding a layout.
▲ 0↑ born
·
tool · born here
❒asset
Loads one selected circuit as the root editing scene using layers.load, builds its deterministic geometry, and saves it. Existing additive loads are replaced safely. Requires edit mode. Return to scenes.rainline for multiplayer play.
▲ 0↑ born
·
tool · born here
❒asset
Edits an existing circuit control polygon in edit mode. Rejects non-finite coordinates, points less than 24 m apart and crossing segments. Preserves biome and road width. After editing, run firstLightMaps.rebuild and inspect the smoothed road visually.
▲ 0↑ born
▣
module · born here
❒asset
# shared Cross-tool helpers for the firstLightMaps toolbox. Every tool inside the toolbox can pull these in with `require(".shared")`. Holds the small set of helpers that more than one tool needs — typically the `ok(value, formatted?)` / `fail(message, exitCode?)` constructors that produce the canonical `firstLightMapsToolResult` shape, plus any toolbox-wide parsers, validators, or shared state. Per-tool implementation stays inside each `<x>.tool/init.luau`; this module is not a place to forward logic from. ## Exports - `M.ok(value: any?, formatted: string?) -> firstLightMapsToolResult` — success envelope (`exitCode = 0`, `ok = true`). - `M.fail(message: string, exitCode: number?) -> firstLightMapsToolResult` — failure envelope (`exitCode` defaults to 1, `ok = false`). Types: - `firstLightMapsToolResult = { stdout: string, stderr: string, exitCode: number, ok: boolean, value: any? }` - `stdout` — human-readable formatted output; empty when the op produces no text. - `stderr` — error message on failure; empty on success. - `exitCode` — POSIX-style exit code: `0` success, `1` generic failure, `2` bad arguments. - `ok` — `true` iff `exitCode == 0`. - `value` — structured return from the underlying op; `nil` for void ops. ## Usage ```luau local shared = require(".shared") function M.someTool(args) if not args.id then return shared.fail("missing id", 2) end return shared.ok({ id = args.id }, "created " .. args.id) end ``` ## Notes - Pure constructors — no engine calls, no state. Safe to call from any context. - Tools that opt into this shape get a stable envelope every other tool in the toolbox can rely on. Tools that do something custom can return whatever shape they want — `firstLightMapsToolResult` is opt-in. - Per-tool implementations still own their own `--!desc` / `--!arg` / `--!return` / `--!example` annotations even when their result is constructed through these helpers.
▲ 0↑ born
▣
module · born here
❒asset
# shared One-paragraph description of what this module provides and who consumes it. ## Exports - `M.exampleFn(arg) -> result` — what it does and when to call it. - `M.exampleValue: type` — what value it carries. ## Usage Replace `<identity>` with the string `asset.create` returned — this module's source path with `/` written as `.` and each segment's type suffix dropped, the way a module at `/source/lib/thing.module` is `lib.thing` and one at `/source/kit.package/thing.module` is `kit.thing`. ```luau local M = require("<identity>") M.exampleFn("foo") ``` ## Notes - Anything callers need to know about THIS module: required runtime ordering, state ownership, side effects.
▲ 0↑ born
▣
module · born here
❒asset
Authoritative five-circuit catalogue: ids, names, descriptions, control polygons, biome and half-width. Consumed by rainline.shared, the circuit builder, selection menu and firstLightMaps tools.
▲ 0↑ born
backing path · firstLightMaps.toolbox

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.