Gamingcrystal-caveswebassemblygame-preservation
Crystal Caves runs in a browser after a C rewrite checked against the DOS game
Mylo Steamwitz still has crystals to collect, but the preservation work reaches into save-file validation and the original hub-only saving restriction.

Crystal Caves has escaped DOS. The path out involved more work than putting an emulator behind a Play button, because this developer wanted the logic running as native browser code while keeping a reference to how it used to behave. The developer disassembled the original executable and reimplemented the logic in C, describing the goal as “fidelity, not a remake” in the project README.
Apogee’s original game listing puts the release on October 23, 1991. Mylo Steamwitz heads to the Altairian star system looking for treasure and finds caves occupied by robots, creatures and traps. The full game has three episodes; this project targets the first, The Trouble with Twibbles. Keeping that boundary clear matters when a browser tab makes an old game look like the whole boxed package.
The caves also give a port plenty of ways to be subtly wrong. Apogee describes upside-down walking and low-gravity levels where firing the laser pistol can knock Mylo into danger. A familiar-looking screenshot cannot tell you whether that recoil survived. It takes movement, collisions and another poorly timed shot to find out.
The unusual part is what stayed behind to check the new version. The project uses a Unicorn-based emulator as an oracle for the old binary, comparing the rewritten game’s behavior against it. The emulator participates in verification; the browser game runs the port.
The README reports pixel-exact static rendering across 19 levels, plus frame-by-frame checks of physics, combat and other routines. Those are the developer’s fidelity claims, rather than an independent playtest here. The testing notes and fixtures are available in the repository, making those claims specific enough for another developer to challenge against the original routines.
Saving turns out to be another place where a browser conversion has to make decisions. The developer’s persistence notes document a 33-byte DOS save block. It recorded such things as ammunition, health, score and cave-completion flags. Restoring reloaded the hub and applied that block; the original did not preserve every moving object and changed cell.
The browser snapshot keeps more state so a restore can reproduce the hub exactly, including opened doors and the random-number state. The notes call it a “deliberate superset,” while the game’s shell still enforces the old hub-only saving restriction. Preserving what players could do and preserving every internal byte are different jobs, even inside the same save menu.
The new format also has a checksum, and a load is validated in temporary state before it can replace the live game. The developer says a failed load leaves play untouched. That’s a useful distinction when the treasure hunt depends on a browser storage entry: finding damaged data should not damage the session you still have open.
A future preservation project could borrow that division of work. Compare the old behavior where timing matters, document adaptations where the host platform forces a choice, and make the boundary inspectable. Otherwise the person who remembers a jump has to argue with the person who remembers a screenshot.
The source license covers the port’s own code; the README separately reserves the original game’s assets to Apogee. Open source doesn’t turn every file in a game project into somebody else’s building material.
The interesting next report would come from someone who knows every jump: where the browser version feels exactly right, and where that old muscle memory finds something the fixtures missed.