Week 5: Save files as archaeological evidence

What a save file can tell you about a game you can't otherwise run, and how to read one without a working emulator yet

22 March 2027

A save file is often the most information-dense artifact that survives a lost game — sometimes the only thing that does, when the executable itself is gone or won’t run. This week treats a save file as evidence in its own right: a snapshot of state that can confirm what content existed, roughly how far a level or story went, and what systems the game tracked, all before you have anything running to test it against.

Meridian Drift’s save format returns here as the running example: its saves stayed readable long after the beta build itself stopped booting cleanly under emulation, and cross-referencing the two was how the missing final act was confirmed to exist at all.

Outline#

• what a save file usually encodes, and why it outlives the executable
• reading save state without a working build to compare it against
• worked example: confirming a lost act of Meridian Drift from saves alone
• save-file evidence as part of a recovery report, not just a curiosity