PC (DOS)
Betrayal at Krondor
2 projects on the board for the PC (DOS) version: 0 recomp, 1 source port, 1 decomp.
- First released
- 1993
- Also released on
- PC (Windows) (per Wikidata; no project on the board works from these versions)
| Kind | Project | Claimed | Claimed through | Maintainer | Description (the repository's) | Toolchain | Status | Runs on | Version | Released | Last commit | Started | Licence | Language | Repository | Approach (owner's) | Notes (owner's) | Wants help with | Links | ID |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| source port | BaK-Again | claimed | its .recomp.json file | JvE | A modern, moddable remake of the 1993 role-playing game Betrayal at Krondor, built in Unity. It runs the original game's story, world, rules and art from your own copy of the game, and plays on Windows, Linux and Android. | Unity | Playable | Windows / Linux / Android | v0.7.3-beta | 2026-11-19 | 2026-11-22 | 2026-09-27 | MIT | C# | public | Engine rewritten in Unity from the game's reverse-engineered file formats and logic; reads the player's own copy of the game data. | Alpha. Every chapter can be played to the end. Moddable: replacement assets go in an Overrides/ folder. | playtesting bug reports | Website Forum | betrayal-at-krondor-stellargames |
| decomp | canassa/betrayal-at-krondor | no | Betrayal at Krondor: A byte-perfect recompilation of the 1993 classic. | toolchain-v1 | 2022-05-09 | 2026-08-02 | 2012-09-07 | Other | Assembly | public | betrayal-at-krondor-canassa |
Rows come from the projects' public repositories, read every day; status and notes are the owner's word once they claim the row. Game facts are from Wikidata (CC0). The whole table · Add or correct a project
If one of these projects is yours
A .recomp.json to start from
Committed at the root of the repository, this file claims the row and writes it. The values below are what the board reads from the project today: correct what is wrong, choose the status, add what only you can say (notes, the help you want, who maintains it), and change the file when the status changes. Every field and the values it takes.
Save it as .recomp.json on the default branch. The board reads it every day; the
row then shows as claimed and says what the file says. Left without a status, the row shows none.