Who’s recompiling what.
Hundreds of games are still waiting for a recomp, while some get started three or four times over. One row per project, a public repo behind every row, activity read from the commits: check here before you pick a game, and put your time where nobody is working yet.
- Rows
- Recomp
- Decomp
- Active
- Want help
- Unclaimed
Loading the table…
| Expand row | Notes |
|---|
Version (newest release or tag) and Last commit are read from the repo once a day. The dot next to the date: green under 3 months, amber from 3 months, grey from 6. Toolchain is filled in only when the repo names its recompiler or toolkit, or by whoever claims the row. System is the platform of the binary the project recompiles or decompiles (console, computer or arcade), as its owner states it; Runs on is where this project's build lands, as its owner states it; until they do, it lists the platforms named in the file names of the newest release, marked "latest release", and says "not stated" when those names say nothing. Status, Notes and the maintainer's name are written by whoever claims the row. On an unclaimed row they stay empty rather than guessed. Click a row to expand it.
Nothing matches those filters. Clear them, or add the project yourself.
The table data didn’t load. If you’re opening this file straight from disk, serve
the folder instead: npx serve .
Rules
-
01 / Repo required
A row needs a public repository that already exists. That keeps the table from filling up with games reserved by people who never start. The URL is checked when the row is added and again every day.
-
02 / Silence expires
Quiet after 3 months without a commit, Dormant after 6, whatever the status. Automatic, no judgement involved. Dormant is not a verdict: read it as “ask before assuming anyone is on this”.
-
03 / Recomp and decomp are separate
Different work, different skills, different timelines. They share the table but never the same row of it. Filter to one and the other disappears. A repository that does both gets two rows, one of each.
-
04 / Anyone can add, the owner decides
You can add a row for a project you found, so the table isn’t empty on day one. It lands marked unclaimed, built only from what the repo says. The person who owns that repo can claim it in one message, and a claimed row is then theirs alone to word, untouched by later scans. Until then, anyone may fix its details.
-
05 / Duplicates allowed
Two projects on the same game both get a row. The point is knowing who does what, not stopping anyone from doing it better.
-
06 / No ROMs, ever
No game files, no links to them, no “where do I find it”. Rows carrying one are rejected automatically and removed on sight.
Add a project
Yours or someone else’s, a correction or a claim: a file in your repository, or a form. A bot checks the repository and writes the row within a few minutes.
What this is
The problem it fixes
Recomp work is scattered across a dozen Discord servers, a few repos and the occasional Reddit thread. There’s no way to see, before you start, whether someone is six months into the game you just picked. There are thousands of games and not many of us. Overlap is the expensive mistake.
Where the rows come from
Maintainers who post or commit their own row, and a periodic sweep of public repositories, seeded in part by the community catalogues that came before this one. The sweep copies only what a repository states about itself: game, system, kind of work, commit dates, release tags. It never writes a status, a note or a person’s name. Those cells stay empty on an unclaimed row, and a value the repository doesn’t state plainly is checked by hand. Still, it is a script reading prose, and it gets some rows wrong. Every correction sent through the form fixes one and teaches the sweep, but the owner is the only reliable source: claim your row and it becomes yours to write.
What it isn’t
Not a claim system, not a quality bar, not a launcher. A row reserves nothing, grants nothing and judges nothing. It says only that this person is working on this game, and here is the code. No ROMs, no builds, no links to either.
Terms of use
Free to use
Read the table, search it, link to it, follow the feed, and let an assistant read it for you. Quoting a few rows with a link back to the board is fine.
Not free to copy
Copying the whole table, or a substantial part of it, into another site, list or dataset needs written permission. Each row states public facts about a public repository and those facts belong to no one; what is protected is the collection and the work of finding and checking it. The site’s code is not licensed for reuse.
Yours stays yours
What a maintainer writes in their own .recomp-board.json remains theirs.
The board only displays it, and stops the day the file is deleted.