Lap Recorder FAQ
Track laps without losing the race context.
Answers for Torn racers using Lap Recorder to capture lap times, compare car and track records, and review racing sessions with cleaner, focus-safe context.
What is Lap Recorder?
Lap Recorder is a Torn racing userscript focused on capturing lap times and keeping those times tied to useful session context.
It is built for racers who want car-specific records, replay review, and a clearer way to compare pace without turning the race page into a full spreadsheet.
How do I install it?
Install it through a userscript manager such as Tampermonkey, or through Torn PDA if the release build supports it.
The latest public Greasy Fork release is v1.6.5. The current local v1.7.1 build is pending staff review.
After installing or updating, reload Torn and open the racing pages where you want lap recording available.
How are lap records organised?
Best Lap and Race Time do not use exactly the same track scope anymore.
Best Lap always uses just the base circuit name.
Race Time uses just the base track name when the race matches that circuit's official lap count.
Race Time uses Trackname - X Laps when the race uses a custom lap count.
The corrected official map now includes Two Islands as 6 laps, Sewage as 11 laps, and Convict as 10 laps.
What does replay-aware capture mean?
Replay-aware capture means the script is designed around race review as well as live racing.
The goal is to make recorded laps easier to connect back to the session or replay context that produced them.
The replay page no longer auto-clicks your driver. If no driver is selected, the UI prompts you to choose one manually.
Where is my lap data stored?
Lap Recorder is presented as a userscript, so any saved records or preferences should be treated as local browser or userscript-manager data unless the release notes say otherwise.
Back up anything important before clearing browser storage, reinstalling userscripts, or moving devices.
What should I look for in the screenshots?
The screenshots on the script page show the lap-recording interface and how timing context appears during review.
Use them as a quick visual check before installing or updating the script.
The recorder is not showing. What should I check?
- Make sure the userscript is enabled.
- Reload the Torn racing page after installing or updating.
- Check whether your userscript manager or Torn PDA has blocked the script.
- Confirm you are on a racing page where lap recording is expected to appear.
- Keep the Torn racing tab focused if you expect laps or the tab timer to update.
- If the recorder window feels misplaced after a resize, reopen it or drag it once; the newer build now clamps it back into view automatically.
- The current local build also uses a taller default window and a larger minimum height, so the panel should open with more room on fresh pages.
How do I report an issue?
Include the race page you were on, what you expected to be recorded, what was actually recorded, and whether you were live racing or reviewing a replay.
If your question is about the new Like this script! flow, mention whether you were in the recorder or already on the release thread when it stopped.
That context is usually enough to reproduce lap-recording issues cleanly.