First-run drop-off in a browser runner is often blamed on difficulty. In practice, many exits happen after a death the player cannot explain. If a press silhouette or sweeping indoor arm never reads before the commit window, Boost and roll tricks cannot save the session. In CGT Rocket X Racer — a fan-made rocket-car runner for desktop browsers — we treat hazards as a readability system first, and a difficulty dial second. A fair death says “I read late.” An opaque one says “the game lied,” and there is no second run after that.
Fan-made · Desktop-only · Not affiliated with any car maker.
Real first-run failure modes
Three failure modes turn a miss into a betrayal.
Muddy silhouette. The press that is about to stamp, or the arm that is about to sweep, never presents a clear outline early enough. Particles and motion blur win the frame; the lethal shape loses. The player dies inside noise and has no mental replay of what hit them.
Phase that lies after Boost. Hazard timing that feels honest at cruise speed can feel dishonest when approach speed jumps. If telegraph stays locked to a slow-car rhythm while the car is already closing faster, the same stamp that felt fair becomes a surprise clip. The player does not blame their Boost timing — they blame the obstacle for “changing.”
Rewards buried in the kill path. When a part pickup sits inside a hazard’s motion arc, death feels like the game baited a collect. The HUD may have been honest about which bin was weak; the track placement still taught the wrong lesson: greed was punished by geometry the player could not negotiate.
Product conclusion: each of these converts “I mistimed” into “this cheated.” First-run trust dies with the car.
The readability contract
We nail these rules as a checklist, not as engine lore.
- Silhouette before spectacle. Press and arm outlines outrank particles. If the lethal shape is unreadable, the VFX is wrong even when it looks expensive.
- Safe lane stays visible. Indoor sweep patterns keep a lane the eye can hold. A pretty kill box with no readable escape is not difficulty — it is fog.
- Distance sampling, not wall-clock. Hazard phase follows track distance so Boost changes approach speed without rewriting the beat the player already learned. We treat this as a readability fix, not a separate Boost essay.
- Death attribution stays readable. After a crash, the player should be able to replay “I read late” or “I cut late,” not invent a story that the capsule quietly resized.
- Landscape framing under Boost. At Boost speed the camera still has to keep forward hazards legible in a wide desktop frame. Readable approach is a framing job, not a portrait crop.
That contract is what we mean by fair. Hard is allowed. Opaque is not.
Feedback loop: before, at, and after death
Readable hazards are a three-beat loop.
Before death. Telegraph — rotation, outline, motion phase — must land before the commit window. The player needs time to choose a lane or hold Boost, not time to invent a conspiracy. Surprise without telegraph is cheap; telegraph that arrives after commit is worse, because it looks like feedback while offering none.
At death. Feedback stays short and specific. A flash or hit read that still shows what you hit beats a full-screen wash that erases the culprit. If the frame after impact cannot answer “press or arm?”, the death screen is decorating failure instead of teaching it.
After death. A one-line, soft attribution is enough: something that points at late read or late cut, without a lecture. The goal is the next run’s attention, not a tutorial modal. Weak bin red on the collect HUD is a collecting lesson; hazard readability is a survival lesson. Those two lessons should not fight for the same visual channel. When they collide, players stop knowing which skill they failed.
Knobs we are still turning
Honesty over polish theater.
Compatibility mode plus frame drops still ask how heavy telegraph must be before it reads “in time” on a tired tab. A stamp that is clear at 60 fps can smear into a lie when the tab hitching hides the outline for two frames. Boost hold stretches how much track distance fits inside the same commit window, so we keep asking whether telegraph should lean slightly earlier as speed rises — without turning every stamp into a neon billboard. We also keep auditing pickup placement against hazard arcs so the collect loop never reintroduces baited deaths.
If you ship Godot 4 browser runners, we want the cheap signals: outline weight, earlier phase, softer post-death copy, or anything that makes a first-run death feel like the player’s miss instead of the build’s lie.
Why readable hazards are the first-run floor
Readable hazards are infrastructure for first-run trust on the desktop web build. Without them, every other system — Boost, collect bins, end-of-run payoff — spends trust it never earned. With them, a death can still sting and still earn one more try.
Desktop build on cgt.monster.
When a first-run death hits, do players more often blame unclear telegraph or unfair judgment?
Fan-made · Desktop-only · Not affiliated with any car maker.
Top comments (0)