KEEP THIS HANDY
Controls at a glance.
- Mouse
- Steer.
- Click / double click
- Brake / jump.
- R
- Restart.
Learn the shared click gestures
Braking and jumping use related gestures. Try each in a clear section so that a planned jump does not become an unexpected brake. The enhanced build also has pointer-lock behavior, so the original host may ask for an interaction before the pointer behaves as expected.
Look ahead to the next obstacle
The README describes trees and rocks and suggests swerving or jumping past them. Choose one response early enough to understand its effect. Steering around an obstacle while already braking and attempting a double click makes it harder to identify why an attempt succeeded or failed.
Use checkpoints as the immediate target
The creator states a twenty-second opening allowance and ten additional seconds per checkpoint. Those are the documented rules, rather than a measured completion time for this profile. The road is generated anew, so a route remembered from a screenshot is not a reliable map of the next run.
What happens to your progress?
Persistent campaign saving has not been established by the reviewed documentation. Treat the linked build as a session unless its menu says otherwise.
Check the save and backup guide ↗A FEW USEFUL ANSWERS
Before the next click.
Does every attempt use the same road?
The README says the road is randomly generated each time.
Is the two-kilobyte file the only version?
No. The repository also hosts an enhanced version with additional features.
A useful next read.
Browser racers: learn the brake before the lap. ↗Follow the source.
Frank Force / Killed By A Pixel. Licence notice. GPL-3.0 repository; retain creator notices.
Latest collected source change: Add files via upload (opens a new tab) . Repository activity does not identify the hosted game version.
All media and source credits ↗
