CodeRecorded November 4, 20261 model

The Cybertruck rally

A Tesla Cybertruck monster-truck rally in one HTML page - a small stadium, a crowd all the way round, and five trucks slamming into each other. The spectacle is the easy half. The spec underneath it asks for exactly five trucks, a named arena, a `#demo` URL mode that starts at 20 seconds and 5000 points through real game state, and a photo mode on P that actually stops the simulation. Every one of those is checkable in ten seconds, and they are what separate a model that read the brief from a model that recognised the genre and shipped the version it already knew. This challenge also has a second job. A LoRA adapter was fine-tuned on 120 generated Cybertruck rally games and is public at `johanna09/qwen38-27b-cybertruck-rally-full`. Run it here and you are looking at a deliberately contaminated entrant: it produces a beautiful rally and misses spec items it was never trained to see. That is the control for what benchmark contamination looks like from the scoreboard.

The prompt every model got

You are a game developer who ships browser demos that have to work on the first click, in front of an audience, on someone else's laptop.

Build me a Tesla Cybertruck monster-truck rally as one self-contained HTML page. A fairly small stadium, a big crowd in the stands, artificial hills and debris across the floor, and trucks slamming into each other.

Then make it match the spec below exactly. The spec is the challenge; a great-looking rally that ignores it is a miss.

The build

One file. Everything — HTML, CSS, JS — in a single .html page. No build step. Saved to disk and double-clicked, it runs.
One external request, maximum. You may load three.js from a CDN, pinned to an exact version. That is the only network request the page is permitted to make. No second library, no font, no stylesheet, no image file, no audio file.
Sound is optional, and if you include it, generate it with the Web Audio API. No audio assets.
No storage. No localStorage, sessionStorage, cookies or indexedDB. It runs in a sandboxed frame where touching them throws.

The spec

Exactly five trucks. One the player drives, four rivals under AI. Not four, not six — five.
Name the arena. Invent a name for the venue and show it in the HUD, on screen, during play.
The HUD shows the arena name, a score, and a clock. Nothing else is required.
At least three distinct obstacle types on the floor — the trucks should have something to hit besides each other.
A crowd in the stands that is visibly a crowd, all the way round.
Drive with the keyboard. Arrow keys or WASD. Say which in the HUD or an overlay.
Collisions matter. Ramming a rival does something — score, a visible reaction, a wreck state. Your call, but it must be visible.

Two modes that are not the game

Both are checkable in ten seconds, which is why they are here.

#demo — if the page URL ends in #demo, the game starts with 20 seconds on the clock and the score already at 5000. This must run through the real game state, not a cosmetic overlay. Everything else behaves normally.
P for photo mode — pressing P freezes the action and overlays the arena name and the current score, held until P is pressed again. The simulation stops; it does not keep playing behind the card.

Answer in exactly these sections

The pitch

One sentence: the name of your rally and what it looks like.

The game

Exactly one fenced html block containing the whole page and nothing else.

The notes

Exactly four bullets.

Five trucks: how you kept four AI rivals from clumping into one moving wall.
Demo mode: the line of real game state #demo sets, and why it is not an overlay.
Photo mode: what you actually stop when P is pressed — the render loop, the physics step, or both.
Collisions: one short paragraph on the collision model you implemented. Not what it looks like — what it computes.

Answers

Sorted by cost. Open a row to load its answer.