Crimsonland, rebuilt¶
Crimsonland (2003) rebuilt twice: a reimplementation that plays exactly like the original, and a matching decompilation whose source also plays the original game in your browser. These docs cover how the game plays, how the rebuilds work, and the reverse engineering that ties them to the original executable.
-
Play in your browser
The original game, compiled from the recovered source, with ranked play. Nothing to install; saves stay in the browser. Keyboard and mouse, or a gamepad.
-
Play the reimplementation
Windows, macOS and Linux, with controllers, replays and ranked play. Install uv, then:
-
Leaderboard
Survival and every quest, where each score is a whole run the server replays before it counts.
-
Source and story
The code, the progress of the matching decompilation, and how it all came together.
Highlights¶
-
Matching decompilation: every game and engine function of 1.9.93 comes from recovered C/C++ source that compiles to the original machine code. 1.9.8 is measured from the same source.
-
Perks: all 58 perks with exact numbers, interaction rules, and original bug notes verified against two builds of the binary.
-
Fire Bullets (1.9.8 vs 1.9.93): how fire bullets changed from an additive bonus (1.9.8) to a full weapon replacement (1.9.93), with per-weapon DPS showing most weapons lost 80-95% of their output.
Sections¶
-
How the game actually plays: behavior specs, reference tables, and game rules written without decompiler details.
-
The Python port and the recovered core: architecture, module map, debug views, parity status, and a feature matrix of every client.
-
Static analysis, runtime probes, struct layouts, and file formats extracted from the original binary.
-
Differential testing, the evidence ledger, and parity matrices that connect claims to proof.
-
Setup, workflows, and project tracking.