Build a multiplayer card roguelite behind a shared rules engine and push gates

A solo developer used Claude Code across 1,644 commits since January to build a 1 to 4 player card roguelite in 14 languages, with 172k lines of game code and 135k lines of tests, ahead of a December store launch.

Done withClaude Code· Nov 13, 2026

What they did

Reddit user u/Tommyruin, who says they lack a coding background, has been building Aita: The Dark Domain since 5 January, a roguelite played with a standard deck of cards, solo or in online co-op for up to four players, translated into 14 languages. Claude Code co-authored 943 of the 1,644 commits. The setup that held it together: a single rules core that solo play, co-op, the game server and a headless test player all call; a markdown file every session reads first covering naming, architecture and what counts as done; handoff notes so each session picks up where the last stopped; and checks before every push for lint, tests, a build, docs and stale translations. The headless AI player plays runs and reports data used to tune difficulty.

How it went

The project reached about 172k lines of game code and 135k lines of tests, with a free demo on Steam and a paid release set for 1 December on Steam, Google Play and the App Store. The main lesson was drift: rules first lived inside each mode, so fixes landed in one of three engines but not the others. Moving them into one core started in February, yet stray rule code kept turning up until October. Rendering was also split two ways until everything moved onto one pixel canvas in October. Parity tests compared the modes before the merge. The headless player also helped with performance passes, alongside testing on several real devices.

Worth knowing

The poster says they would set up the shared core, the session file and the push gates on day one next time. A commenter suggested a build check that fails when gameplay code outside the core imports anything but its public API, to catch rules put in the wrong place. The post is partly promotional, and no cost figures are given; the poster rotated between subscriptions over the year.

Try it

With Claude Code· 7 parts to fill in

We are building [game type] in [repo]. Before any feature work, set up the guard rails: 1) one rules module that every mode ([solo, co-op, server]) must call, with parity tests that run the same scenario through each mode and fail on any difference; 2) a [CLAUDE.md] covering naming, architecture and what done means, plus a handoff notes file you update at the end of every session; 3) a pre-push check that runs lint, tests, a build and [translation or docs checks]; 4) a headless player that can play [number] runs and log results. Then take [feature] from the backlog. Stop and show me the diff once all checks pass.

Square brackets are the parts to fill in. The prompt is ours; the story is theirs.

Where they said it

Related