Upload your run.txt file to submit it for Moderator review.

• Already have a Run submitted on Speedrun.com?
• Provide the link to your pending submission.
• Submitting to Speedrun.com next?
• Submit your file(s) then paste the provided Verification Key into the description of your Speedrun.com submission.

Reviewing a Submission: Click a row in the Moderator Queue below to open it. Note the Category will show a Speedrun Category if the file attached is a run.txt, LOGS if the file attached is a console.txt/DebugLog.txt and [BOTH] if a console.txt and run.txt are attached. Opening a run.txt queue entry runs the Hash Chain / Splits / Sandbox / Mods List verification against the submission's run.txt.

Key Points to check when verifying a Submission:

• Chain Verified: Confirms the run.txt hasn't been edited.
• No Run Invalid Banners: Debug Mode, Multiplayer topology or any active Mods besides DeadSplit will mark a run as Invalid. Don't rely solely on this indicator to reject a submission and use judgement backed by the video.
• Verification Key: There are 2 Different Types of Keys. The first Key is generated in-game by DeadSplit and matches the Key displayed in run.txt to their Video evidence. The 2nd Key is generated by the Website for console.txt/DebugLog.txt submissions. Both types of Keys are what we use to match their File submission here to their Speedrun.com submission description.
• Speedrun.com Username/Link: Matches the actual Speedrun.com submission being reviewed.
• Category, Splits & Time: Match what's shown in the Runner's video evidence.
• DeadSplit Fingerprint: Confirms the Runner's mod files weren't modified. See "Results appear in the Fingerprint card" below for what each comparison means.
• Critical Constants: A Match indicates the Runner's real required kill counts, skill levels, and floor thresholds match both at the start and end of their run, and against the reference version loaded in to this page. A Mismatch indicates one of these was edited to make a category easier. The Fingerprint above can miss a same-line numeric edit like this, so this check exists specifically to catch it.
• Any Warning Banner: Banner: (DSP_Config.DEBUG, Run Key Hidden, Run Not Completed) use judgement backed by the video, these don't auto-invalidate a run.

DeadSplit Reference Version: Use the pre-loaded Version presets (Uploaded by Nox when a new Version of DeadSplit is released) or drop in the DeadSplit folder from your own copy of the Mod (Located at SteamLibrary\steamapps\workshop\content\108600\3795485367). The correct Folder is the Folder containing 42\media... & common\media... This lets you compare the Fingerprint embedded in a Run against a verified clean copy to check whether the Runner attempted to modify or tamper with DeadSplit's code. Load it once and it applies to every submission you open afterward, whether from the Queue or a one-off upload.

Results appear in the Fingerprint card: "Setup vs Export" compares the Fingerprint taken at the start of the Run against the one taken when it was exported (catches someone reverting changes before exporting); "Setup vs Reference" and "Export vs Reference" only appear once a reference Folder is loaded, and compare against your verified copy. Each shows a green MATCH or a red difference count with the specific files listed.

World Record Verification: When an eligible completed Run is loaded, select Validate World Record at the bottom of the results. Confirm the Record Holder Name and UTC Date, then Save World Record. This writes directly to the shared master WorldRecords.txt — every other Category's record is kept as is, and if the master already has a faster or equal time for this Category, you'll be asked to confirm before overwriting it.

DeadSplit Users need to download the current master and place it in Zomboid\Lua\DeadSplit to see up-to-date records in-game — the download link is shown in the Validate World Record window after saving, or always available directly from the master file link.