It's 11 pm. Your game just crashed, you don't know why, and you're afraid a tool will wreck the Mods folder you spent months building. Bedside tells you which of your mods breaks your game — and why. And it touches nothing without your say-so.
Bedside diagnoses what breaks your game, not what makes your save annoying: a mod making questionable gameplay choices is not a breakdown.
← Tanven, the publisher · My game crashes: what to do? · Support · Logbook
Tuning conflicts read INSIDE the files, duplicates, damaged files, mods overriding game resources. The verdict names the file — never "something is wrong somewhere".
A small companion watches from inside the game: hard crashes that leave no report, mods that never load, script collisions. What no external tool can see.
"Can I remove this CC without breaking my save?" Bedside cross-checks your saves and library against every file — and suspends judgment when it could not read everything.
The game's error reports, turned into concrete leads — cross-referenced with your disk state and change history. The 50/50 assistant narrows the culprit down in a few restarts.
Startup and every session are timed from inside the game. When a save takes longer to load than before, Bedside says by how much, and which files arrived in between — without accusing them.
A crash that leaves no error report at all? Bedside dates your last session that ended cleanly and lists what changed in your folder since. That is not proof, and it says so in as many words: it is where the trail starts.
Naming a file is not enough: you have to have watched the failure happen, then go away. These three were reproduced in the game, cut down to the offending setting, then found again cold on disk — without launching the game.
One curly brace without a valid token in an object's name, and the game falls over as soon as you type in the build mode search. Reproduced and controlled in game on 3 September 2026; across 189 packages, not one healthy file wrongly accused.
Four recipes in a cooking mod point at an object that exists nowhere — not in the mod, not in the game. The game raises an error at every lot load, and its own report blames two perfectly innocent script mods. Measured in game on 7 September 2026 on version 1.127.41: Bedside names the right file.
A block-compressed texture, with non-power-of-two dimensions, carrying a whole chain of detail levels: the object never shows up. Two objects placed in game the same night. The next day a flagged rug displayed perfectly — so the detector was tightened that very day, rather than left to lie.
A fourth lead was dropped: the two mods players were blaming load without a single error on this version of the game. Bedside stays quiet, and that is the right verdict. As for the third cause, it is not demonstrated — only observed on three packages that were played, and the program says so in those terms.
Nothing is ever destroyed. Reversible quarantine, recycle bin, snapshots before any mass operation. Never a silent overwrite.
Never more confident than the evidence. A failure never shows green; "couldn't read" is never "nothing found"; every finding declares its remedy.
Local first. Diagnosis is fully offline. Seven network functions, not one more, all visible, and not one of them is needed to reach a diagnosis — telemetry only exists if you opt in, with the exact payload shown before anything is sent.
The closed beta is taking shape on the Bedside Discord — invitations and announcements land there first. The public, signed release will follow.
Bedside is a Windows application. A macOS version is being built; it has never yet run on a Mac, and nothing will be announced as ready before we have seen it with our own eyes.
Join the DiscordFree, and it will stay free. If it helped you: support Tanven.
The verification sheet: a dated, reproducible statement about one specific file — what was checked, and above all what was not. Verifiable by anyone re-running Bedside on the same file. Free, on principle: charging to be "verified" would destroy the statement's worth.
Want a sheet for your mod? Ask on the Discord.
No — it complements them. Tools that read error reports see what the game managed to catch; Bedside reads your Mods folder, the caches and the freezes, which none of that can see. They get along fine.
No. Bedside doesn't sort, download or update your mods: it diagnoses. When something breaks, it tells you which file, and why.
Today, Bedside is a Windows application. Diagnosis is fully offline — no connection needed to treat your game.