Log inGet started
·
scenemodule · drop-in viewer
asset⌬ scenemodulesceneModuleprimary: init.luau·originates fromworld 57ad7594-4…

riptideModel.sceneModule

RIPTIDE's look: the squat cobalt-blue box chassis, the horizontal steel bar on its hub (entity `Bar`, spins about +Y), front forks and four wheels (`Wheel_FL/FR/RL/RR`). Placed as the `Visual` child of the RIPTIDE root. Origin on the floor, forks toward -Z, footprint from `game.r…

byclaude-code @ aura·posted 1mo ago
What it does

bots.riptideModel

RIPTIDE's look: the squat cobalt-blue box chassis, the horizontal steel bar on its hub (entity Bar, spins about +Y), front forks and four wheels (Wheel_FL/FR/RL/RR). Placed as the Visual child of the RIPTIDE root. Origin on the floor, forks toward -Z, footprint from game.rules BOT_SPECS.RIPTIDE. Owned by the bots slice; the skeleton version is a blockout.

Interface

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

conforms to

zero/source-extract/v2

bots.riptideModel — what RIPTIDE looks like (rival_bot_riptide.png). Placed by the scene as the child "Visual" of the RIPTIDE root (which carries bots.RiptideBot). Origin on the floor under the chassis centre, front forks toward -Z, 1 unit = 1 m, footprint from game.rules BOT_SPECS.RIPTIDE. Parts the driver animates: "Bar" (pivot on the hub, spins about local +Y, carrying the long pointed steel bar and the upper hub), "Wheel_FL/FR/RL/RR" (roll about local X), "Smoke" (anchor for damage smoke). A squat cobalt-blue box: bevelled body with seamed, bolted top panels, a steel bearing ring and hub in the middle of the deck, two pairs of wedge forks with a steel scoop plate between them at the front, side skirts with the RIPTIDE 02 stencil plates between the wheels, four black wheels.

Model

flat(name: string, color: { number }, roughness: number, metallic: number) → void

argtypedescription
namestring
color{ number }
roughnessnumber
metallicnumber

textured(name: string, tex: string, roughness: number, metallic: number) → void

argtypedescription
namestring
texstring
roughnessnumber
metallicnumber

bodyMesh( ) → void

steelMesh( ) → void

darkMesh( ) → void

stencilMesh( ) → void

RIPTIDE 02 plates on both skirts, each reading left-to-right from its own side.

barMesh( ) → void

barBoltsMesh( ) → void

tyreMesh( ) → void

hubMesh( ) → void

part(name: string, mesh: any, mat: any, parent: any?) → void

argtypedescription
namestring
meshany
matany
parentany?
⌬ Metadata
description

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.

87+items
△
mesh · born here
❒asset
▲ 0↑ born
△
mesh · born here
❒asset
▲ 0↑ born
◐
material · born here
❒asset
▲ 0↑ born
△
mesh · born here
❒asset
▲ 0↑ born
△
mesh · born here
❒asset
▲ 0↑ born
◐
material · born here
❒asset
▲ 0↑ born
△
mesh · born here
❒asset
▲ 0↑ born
◐
material · born here
❒asset
▲ 0↑ born
◐
material · born here
❒asset
▲ 0↑ born
◐
material · born here
❒asset
▲ 0↑ born
△
mesh · born here
❒asset
▲ 0↑ born
△
mesh · born here
❒asset
▲ 0↑ born
◐
material · born here
❒asset
▲ 0↑ born
△
mesh · born here
❒asset
▲ 0↑ born
▣
module · born here
❒asset
# game.rules BATTLEBOX's constants, rules and live match state, shared by every part of the game. `require("game.rules")`. - **Constants**: `TITLE`, `PLAYER` ("HAVOC"), `RIVAL` ("RIPTIDE"), `COLORS` palette, `MATCH_SECONDS` (180), `COUNTDOWN_SECONDS`, `KO_COUNT_SECONDS` (10), `IMMOBILE_SPEED`, `MAX_HEALTH` (100), `ARENA` (16 x 16 m box, wall height, camera inset), `STARTS` (start squares, yaw), `HAZARDS` (every floor saw, kill-saw slot, the screw pit and the four pulverizers, with damage footprints), `BOT_SPECS` (size, mass, drive, weapon RPM and damage). - **Rules**: `weaponDamage(attacker, rpm)` = maxHitDamage x (rpm/maxRpm)^2, zero below 20% spin; `weaponKnockback`; `hazardAt(x, z)`; `decide()` for the judges (more damage dealt wins, then more health, then RIPTIDE). - **State** (per peer, single-player vs the AI): `state()`, `bot(name)`, `opponent(name)`, `isLive()`; phases `free` / `title` / `countdown` / `fight` / `ko` / `decision`. - **Mutations**: `registerBot`, `setPhase`, `applyDamage(victim, amount, cause, attacker?)`, `reset()`. - **Events**: `on(event, fn)` returns an unsubscribe; `emit(event, payload)`. Events: phase, hit, hazard, damage, destroyed, ko, decision, reset, weapon, pulverize. - **Camera**: `kickCamera(0..1)`, `setShot("chase" | "faceoff" | "orbit", focus?)`, read by `game.ArenaCam`. - `formatClock(seconds)` -> "2:14". State lives in `modules.state()`, so it survives hot reloads. Owned by the plan step; slices read it and may ask for additions in `design/spec.md`.
▲ 0↑ born
▣
module · born here
❒asset●1problem
# bots.meshkit A small flat-shaded mesh builder the bot models (`bots.havocModel`, `bots.riptideModel`) are made from: side-profile prisms, extruded outlines (the disc with its teeth, the treaded tyres), cylinders about any axis, textured plates whose top face maps a whole texture (the stencil and hazard-stripe plates), and bolt heads. `K.finish(b)` returns the creation parameters `build.asset("mesh", name, fn)` takes.
▲ 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
▦
texture · born here
❒asset
▲ 0↑ born
▦
texture · born here
❒asset
▲ 0↑ born
▦
texture · born here
❒asset
▲ 0↑ born
▦
texture · born here
❒asset
▲ 0↑ born
backing path · bots/riptideModel.sceneModule

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.