SpeedRunners (developed by DoubleDutch Games and published by tinyBuild) is a competitive platformer where save data is crucial for tracking player progression, unlocked characters, and statistical performance. Unlike many indie titles from its era, SpeedRunners transitioned between save systems during its lifecycle, meaning file management depends heavily on which version of the game you are playing.
Here is a breakdown of how the save files work, where they are located, and how to manipulate them.
Let’s distinguish between the casual save and the runner’s save. A normal player saves at the start of a dungeon. A speedrunner saves inside the dungeon, right before the hardest trick, with exactly the right amount of health, ammo, and inventory items required to practice a specific 10-second sequence.
A speedrunner’s save file is a laboratory save. It is a save state (or in-game battery save) positioned at the most difficult choke points of a run.
For example:
These aren't full playthroughs. They are surgical incisions into the game's timeline. speedrunners save file
As we move into an era of always-online gaming and cloud saves, the nature of the speedrunning save file is changing. You cannot easily corrupt a save file that lives on a secure server 2,000 miles away. Modern games like Elden Ring or Cyberpunk 2077 have patched out many of the exploits that relied on save manipulation.
Yet, the legacy of the "Speedrun Save File" remains. It represents a shift in how we view video games. It is the realization that the game is not a linear story told by a developer, but a sandbox of code waiting to be exploited.
So the next time you back up your save file to the cloud, remember: somewhere out there, a speedrunner is deleting theirs, corrupting theirs, or loading a broken one—all to shave four seconds off a world record that only a handful of people will ever see.
To provide a proper report for SpeedRunners save file issues or bugs, you should include specific diagnostic data so developers can identify the cause. 1. Locate and Include Log Files
The most critical part of a "proper report" is the log file created when the game crashes or errors occur. SpeedRunners Save File: A Technical & User Guide
Path: Press Windows + R, then copy/paste: %AppData%/SpeedRunnersLog.txt.
Action: Open this text file and paste its entire contents into your bug report thread.
Alternative (Event Viewer): If the log file is missing, open Windows Event Viewer by typing eventvwr in the Run box. Look under Windows Logs > Application for errors related to SpeedRunners and include those details. 2. Identify Save File Location
If your report concerns lost progress or corrupted saves, you may need to provide the actual save file for inspection.
Local Steam Cloud Storage: C:\Program Files (x86)\Steam\userdata\[YourSteamID]\239140\remote. What Exactly is a "Speedrunner Save File"
Direct Access: You can also check the game's properties in Steam under Local Files > Browse Local Files to find related data folders. 3. Necessary Report Details A high-quality report should be structured as follows:
Issue Description: Clearly state what happened (e.g., "Game failed to save progress after reaching Level 10").
Steps to Reproduce: List exactly what you were doing right before the issue occurred.
Visual Evidence: Attach a screenshot or a video clip of the error message or the glitch.
If you are playing offline or moving data to a PC without internet access:
%localappdata%\SpeedRunners on the OLD computer..dat files.%localappdata%\SpeedRunners on the NEW computer, overwriting the files created in step 2.%LocalAppData%\Speedrunners\Saved\SaveGames\
C:\Users\YourUsername\AppData\Local\Speedrunners\Saved\SaveGames\Slot_0.sav (or Slot_1.sav, Slot_2.sav if you use multiple profiles).🔍 Quick access: Press
Win + R, paste%LocalAppData%\Speedrunners\Saved\SaveGames\, press Enter.