How We Reconstruct Darklands

The restoration starts with the original game and its data. Each supported route is checked against original code and, where possible, the running DOS version. The devlogs show this process in practice.

The reconstruction process

1. 01
   Start with the original

   Original version 483.07 bytes, assembly, resources, and observed machine state define the behaviour to recover.

2. 02
   Review structure and data flow

   Focused Ghidra analysis is checked against an independent Reko decompilation so disagreements are visible before implementation.

3. 03
   Certify the exact unit

   Darklays binds ownership, call targets, branches, memory effects, and evidence freshness to the specific original routine or selected path.

4. 04
   Rebuild the observable path

   The C# implementation preserves controllers, handlers, helpers, state effects, presentation, audio, time, acknowledgement, and destination settling.

5. 05
   Verify against the running game

   Autoprobe and the patched DOSBox-X runtime compare the reconstructed route with the original executable at focused observation boundaries.

Current toolchain: original Darklands 483.07 bytes and data  ·  Ghidra  ·  Reko  ·  Darklays  ·  patched DOSBox-X and Autoprobe  ·  C# / .NET 10  ·  SDL2

Implementation advances route by route. Where the evidence does not yet establish a branch or effect, that route remains unfinished rather than guessed.