-
-
Notifications
You must be signed in to change notification settings - Fork 4
Home
Daniel Nylander edited this page Aug 26, 2026
·
22 revisions
Status reviewed 2026-08-25. Firestaff has five active game targets. DM1 V1 and DM2 now have playable source-owned routes; CSB has bounded native real-media routes, Theron reaches a bounded JP Track 02 runtime, and Nexus remains real-data bring-up work where its end-to-end boundaries are still open. See Project status, preservation status and the documentation index for the canonical matrix.
Firestaff reimplements five classic Dungeon Master game engines with source-level parity to the originals. It is a pure C application targeting macOS, Linux, Windows, iOS (AltStore Classic sideload), and Android, rendering via SDL3.
| Game | Platform | Reference Source | Wiki Pages |
|---|---|---|---|
| Dungeon Master (DM1) | PC DOS 3.4, Atari ST, Amiga and FM Towns data paths | ReDMCSB | Technical Reference, PC34 Internals, FM Towns guide, RE Documentation |
| Chaos Strikes Back (CSB) | Amiga default; Atari ST and FM Towns native paths; STX title-to-FTLCODE runtime proof; PC-shaped reference data | ReDMCSB and CSBWin | Technical Reference, FM Towns guide, DSA and Save Internals, RE Documentation |
| Dungeon Master II (DM2) | DOS, Amiga (including native CHARSHEET), FM Towns and Macintosh real-media routes | skproject, DMWeb and disassembly | Technical Reference, FM Towns guide, GDAT Internals, RE Documentation |
| Theron's Quest | PC Engine CD | PC Engine disassembly and CD analysis | Technical Reference, Track 02 Internals, RE Documentation |
| DM Nexus | Sega Saturn | Saturn SH-2 disassembly and retail media analysis | Technical Reference, DGN/PRS3 Internals, SAL/MAP Internals, RE Documentation |
- macOS — DMG/ZIP install, Homebrew build, Gatekeeper notes
- Windows — installer/portable ZIP, MSYS2 build
- Linux — deb/rpm, Steam Deck (pacman/AppImage), build from source
- iOS — AltStore Classic sideloading, SideStore, game data via Files app
- Android — APK sideloading, game data transfer
- Players: start with the repository README, game-data setup and project status.
- Developers: read architecture, building and installing, the active per-game TODO files, completed per-game DONE ledgers and missing functions by game.
- Reverse-engineering researchers: use the reverse-engineering index, source-lock pages and parity evidence.
- Preservation researchers: start with preservation and provenance, verified hashes and game-data setup.
- Reverse Engineering Index — overview of all RE documentation, cross-game formats, parity evidence
- DM1 RE — 1388 F-numbered functions, DUNGEON.DAT format, creature types, ReDMCSB file map
- CSB RE — IMG1 graphics format, DSA scripting system, 357 CSB modules
- DM2 RE — 56 skproject files, GDAT format, symbol audit, hex-offset modules
- Theron RE — PC Engine CD layout, Track 02 format, champion/item system
- Nexus RE — Saturn disc structure, DGN geometry, BPK/PRS3 archive, MNS materials
- Building and Installing — build from source, install release packages, sideload on iOS/Android
- Architecture Overview — layer model, module layout, data ownership
- Release Process — versioning, CI/CD, release artifacts
- Parity Evidence — how source-lock documents work
- Preservation — provenance, evidence levels, captures and data boundaries
- Game Data — what original data files are needed and where to place them
- Game-data Formats — verified containers, records and save boundaries
- Native Platform Verification — actual CLI/start-menu evidence by original platform
- Documentation Index — complete cross-game status and page map