Joystick Jammers

Design site. The one place design work is reviewed, on a phone or a laptop: the accepted UI references, the in-world look, audio, motion, and a review page for every vehicle. Sections list their newest work first; each entry carries its date, bead and status. Tell the session what to change and it comes back as a bug bead citing the entry.

Keys: in the TV mocks, H returns to their contents page; every state has its own link, so you can send one back by URL. The phone mock's Mock ▾ button jumps between states and turns on the edge-safe and thumb-reach overlays. Open the TV items on the TV laptop (full screen, from the couch) and the phone items on your own phone, once in a dim room. Nothing here sends anything anywhere. Your checklist: docs/playtests/owner-checklists.md §1.

Bring everyone — the trailer

One minute at 60 fps, narrated by Stevo. The host grid grows from one screen to 64 in a real 64-car race, then generated tracks, a loop-the-loop, all seven vehicles and the controllers. Subtitles are burned in, with a captions track as well. The footage is staged in the real game with the autopilot driving, not 64 people playing.

Bring everyone — earlier picture draft

A one-minute preview with all seven vehicles, controller choices, roads, pileups and a weapons derby. Music and vehicle effects are included; Australian Maya1 narration is still pending.

Design guide and tokens

One palette, two self-hosted fonts (Barlow Condensed for display, Barlow Semi Condensed for everything else), a type scale per viewing distance, the identity kit and a copy glossary, all as data that a script checks. Why: every UI task builds from the same numbers.

Brand and components

One wordmark, an app icon, and a QR that's plain, quiet-zoned and at least 8 px per module on the TV; a component sheet with every state, including keyboard and gamepad focus. Why: every generated image drew a different logo, and a logo inside the QR stops phones scanning it.

The TV grid

Round 5: every tile the same size, filling the screen (no bands above or below). The join QR (with Join now) and the positions only take the spare cells the arrangement leaves anyway; with none, both dock in the footer and clicking the QR pauses with it big. Third person by default, first person per seat; the per-tile HUD in the corners. Why: the game gets every pixel the layout can give it.

The lobby

Every player on one screen over a still view of the upcoming track, with their number, name and state (joining, choosing a car, ready); the cards shrink and drop detail as the room grows, never a scroll or a cap. The join card and Start race share the screen. Why: the lobby shows the room.

Round complete and highlights

One screen: the highlight replay leads (half to two thirds of it), the placings, the join card, the next-race timer and the host's three buttons packed beside it. Why: the highlights are the fun.

Host controls, the pause menu and the captions

The footer carries the room, the readouts and Pause, Full screen and the host menu; anything that needs the screen pauses first. The pause menu keeps the join card beside it; camera and distance are each player's own (phones on the phone, pads and keyboards over their own tile); laps are locked during a race. One caption style everywhere. Why: nothing covers a player's view while racing.

Derby Overview (reference for later)

One shared view of the bowl at a fixed 60° pitch that frames every car and never rotates; identity rings under the cars; thin bands for the timer and damage points; your Grid ↔ Overview switch. Why: derby needs one screen everyone can read; it's built in Full.

The in-world look

The comic treatment live on the real Cruz Missile (toon ramp, ink outlines, halftone in the shadows, grade) in an outback dressed toward H4, under the real HUD at 24 tiles. At 24 tiles it runs without bloom and FXAA, which cost far more than the rest of the look together. Why: the look has to hold at 24 tiles on a laptop GPU (measured: 120 Hz at 1080p). Needs a WebGPU browser (Chrome or Edge).

Round 2: Mad Max looks, ink, lighting. Five Mad Max looks on the same scene (Fury road is the recommendation) plus round 1's, switched live from the bar at the bottom; ink on the car's outer silhouette, or none; shadow, AO, AA and road options with their measured cost; halftone only on the ground, never on a car; brake lamps, boost flames, hazard beacons and roadside flares. Why: you asked for a Mad Max tone with the choices side by side.

Engine sound

The Cruz Missile's procedural engine: RPM, throttle, boost, surfaces, damage and a scripted lap, playable on the TV and your phone (P1-A04).

Announcer voice

The current lines first, then the earlier audition: four prompt-only candidates, two restyle-once references and two TTS engines side by side (P1-A01b).