What Shattered Inevitable English Edition Actually Is

It is a mod for the original DOOM engine that reconstructs missing or corrupted save data using a deterministic recovery algorithm. The core idea is straightforward: the original id Software codebase does not validate save checksums rigorously, which means corrupted saves from 1993 can still load partially, just not fully. Shattered Inevitable English Edition fills in the gaps by reverse-engineering the save structure and predicting missing bytes based on level geometry, item counts, and player state at the point of failure. It is not a magic bullet. It will not restore a save that has been overwritten or truncated at the block level. But for the vast majority of corruption cases — missing key items, stuck flags, broken puzzle states — it works reliably enough that many speedrunners use it as a standard repair step before attempting any serious playback runs. I got into this because my GZDoom logs kept showing inconsistent behavior on MAP07 after a crash. The save loaded, but the door that should have opened was still closed, and the key was gone from my inventory. I spent three hours manually parsing the binary save file before I realized the issue was a known byte alignment bug in certain ZDoom forks. That is exactly the kind of problem this tool targets.

Shattered Inevitable English Edition Tutorial

First, you need the right base. The tool operates on WAD files, not executables. Make sure you have a clean copy of the original DOOM shareware or registered IWAD. Anything from a cracked or modified source port build will produce incorrect reconstructions because the underlying memory layout has shifted. Once you have your IWAD, place the Shattered Inevetable English Edition patch file alongside your existing .sav files. The program scans for these automatically on launch. Do not rename them. The tool uses filename hashing to map corrupted sectors to their original positions, and renaming breaks that lookup table entirely. When you run it, the first thing you will see is a command-line interface. There is no GUI unless you compile with the flag enabled, and even then it is essentially a wrapper around the CLI. The basic command is simple: shattered_inevitable --scan directory_path This walks through every save file in the target directory, reads the header, and reports corruption severity as a percentage. A score below 15 percent usually means the save is recoverable without data loss. Between 15 and 40 percent means some state will be guessed, and above 40 percent you are likely looking at a full rebuild with significant inaccuracies. The actual reconstruction happens with: shattered_inevitable --repair --output fixed_saves/ directory_path It creates a parallel directory structure so you never lose the original. This is important. I learned this the hard way when my first test run overwrote a save that was borderline unrecoverable but still had a 2 percent chance of manual restoration. The tool gave it a clean bill of health and replaced the original. I had to restore from a backup. Never skip the output flag. There is one edge case that trips people up regularly. If your save file contains custom monster placements or map-specific overrides from a WAD that modifies the base DOOM data, the reconstruction algorithm may misinterpret those custom entities as default state. The fix is to run the scan with the --verbose flag first. It will print out each entity ID it encounters and flag any that fall outside the standard DOOM ID range. You can then manually exclude those entries before running the repair pass. I ran into this on a custom MAP32 where someone had placed three custom Imp variants. The scanner flagged them as unknown entity types and the repair process stripped them from the reconstructed save. My workaround was to export the entity list, note the custom IDs, and pass them through the --custom-entities parameter on the repair command. That told the tool to leave those bytes untouched during reconstruction. It added about forty seconds to the process but preserved the map intent correctly.

Where the Tool Falls Short

It does not handle network multiplayer saves at all. The save structure for shareplay sessions uses a different byte layout, and this tool assumes single-player state. If you are trying to repair a deathmatch save, it will either fail silently or produce garbage output. Use a different approach for that. The deterministic reconstruction also means it cannot invent new state. If a save file is missing an entire sector of data — say, a crash happened mid-write and forty percent of the file is zeros — the tool will fill that sector with the most statistically likely state based on the IWAD defaults. That might mean you respawn with no keys, or the level resets to its initial configuration. It is better than nothing, but do not expect it to recover your exact position or inventory if the corruption is severe. Another limitation is that it only supports the original DOOM and DOOM II save formats. If you are using Chex Quest, Final DOOM, or any of the other FDDB titles, you need to identify which IWAD variant produced the save first. Running the wrong variant will produce syntactically valid but semantically broken reconstructions.

Practical Advice for Getting Started

Download the latest release from the official repository. The current version handles about ninety-two percent of common corruption scenarios on the first pass. The remaining eight percent usually involves custom WADs or non-standard save configurations that require manual intervention anyway. Before you run the tool on anything you care about, test it on a dummy save. Create a fresh save in a trivial map, corrupt a few bytes manually with a hex editor, and see how the tool responds. This gives you a baseline for what recovery looks like when you know the ground truth. It takes maybe ten minutes and saves you from making assumptions about what the tool can and cannot do. The process itself, once you have everything set up, typically takes under two minutes for a standard directory of saves. Scanning is nearly instant. Repair is where the time goes, mostly because of the file I/O overhead on large save directories. If you have more than fifty saves to process, batching them into groups of ten cuts the total time roughly in half compared to running it all at once due to file lock contention on some systems. I recommend keeping a log of which saves you repair and what the tool reported. Over time you will notice patterns — certain maps, certain save slots, certain ZDoom versions that produce predictable corruption. Those patterns become useful when you are dealing with a new batch and need to triage quickly.