The lookHow the number behaves, per site — and a phone to try it on

open the real game

This frame plays practice, not money. Same file, same CSS, same JavaScript as the real client — but fun.html has no API in it at all. An admin session and a live payment screen in one browser frame is one mistake away from a signed-in admin placing a real bet, so the real game opens in its own tab and signs in as a player like anyone else.

Which styles come up

A weight of 0 means that style never appears. 3 means it comes up three times as often as a style on 1. The style is still drawn from the round id, so every player in the same round sees the same one — that survives any setting here.

PlainHeavy mono. Reads at any size.

OdometerRolling wheels. Mechanical, inevitable.

SwellSteps up a size at each band below.

Gradient was dropped: it was the only style that changed what the glyphs are — transparent text with a background clipped to it — which kills the text-shadow the others rely on and reads as a second typeface.

Where the number steps up

The band boundaries, in multiples. The cash-out treatment crosses the same lines, so moving one here moves both: the size of the number and the size of the celebration are reporting the same thing.

Fewer, further apart is better than more, closer together. If every step is noticeable then none of them mean anything — the same rule that graded the crash endings and the cash-outs.

The two engineering numbers

Both have a floor for a reason, and the page refuses to go under it.

Blur fromDigits per frame before the fastest odometer wheel blurs.

Render lagHow far behind the server the screen draws, in ms.

Render lag is not a taste setting. It is what keeps the screen behind the settlement. Drop it and a player reads 4.10x, taps, and is paid at 3.95x — and they will be right that the screen lied. 120ms is the floor; 200 is measured.

The sky

Four skies and an automatic. A player's own choice always wins — this sets what somebody sees who has never chosen, and which choices they get.

Opens onWhat a first-time visitor sees.

Automatic maps the player's own hour: 5–10 day, 10–16 midday, 16–19 dusk, otherwise night. It never turns over mid-round — a sky that changes while a number is climbing reads as something going wrong, so the change waits for the gap.

Untick a sky to stop offering it. Worth thinking about twice: a theme is the one setting where the person looking at the screen is the only one who can be right, and the commonest reason to want a dark option is not taste.

Save it

Nothing is saved until you press this. The phone on the right is already showing your unsaved changes.

This site has no look.js — it is running the defaults compiled into the game.

Every site

Drift is the thing this table exists to show. Ten sites quietly running four different looks is how a house style stops being one.

site↕	look.js↕	styles in the draw↕	bands↕	opens on↕	render lag↕	↕

Nothing here

practice · no API showing unsaved changes

Let a round run to 20x to feel the last step.
open this in its own tab

Saving writes one file per site: <site>/new/look.js. Nothing else changes — no settings rows, no .env, no database. Delete it and the game runs on its own defaults.