Rewrite¶

The Python + raylib implementation reproduces Crimsonland Classic v1.9.93, with live gameplay and deterministic replay tooling. The recovered core (crimson-core/) compiles the recovered C/C++ into a native executable and a WASM module; it verifies replays and agrees with Python under both bug policies. Native behavior is established from the executable and recovered source; passing port regression tests alone does not establish parity with the original.

Start with setup, coverage and scope, or the feature matrix of the Python port and the web and native clients.

Python remains the fast iteration platform and records ranked runs. The core also builds the whole recovered game into a WASM module that plays the original natively and in the browser, held to the verifier on every gate stream. The core and its staged gates are documented in crimson-core/README.md and crimson-core/ROADMAP.md, the clients in crimson-core/PORT.md.

Architecture and contracts¶

• Module map: package boundaries, screen ownership, and runtime components.
• Deterministic session: live/replay tick order, input, and presentation.
• Timing domains and mode scheduling: original clocks, mode differences, and Python counterparts.
• Run startup: shared initialization, the run boundary, and terrain RNG.
• Perks architecture: explicit effect phases and ordering.
• Rendering pipeline and terrain: drawing and decal application.
• Local multiplayer: the ¾-player extension to native ½-player behavior.

Parity work¶

• Original bugs: intentional fixes and --preserve-bugs behavior.
• Float policy and precision map.
• CDT trace format.
• Evidence records.
• RNG caller mapping.