AI

Did the Author Play His Own Game?

By brucepro•November 21, 2026•5 min read
Did the Author Play His Own Game?

This week a thread on r/roguelikes asked how AI will affect roguelike development. Sixty-six comments followed, most of them wary, some of them angry. The post itself got downvoted to zero. Buried in the replies was the most useful answer in the thread, from a developer who has clearly played the games he was describing: try a vibe-coded roguelike for twenty minutes and you can tell whether the author ever played it himself. The design mistakes show up fast when nobody did the boring work of playing the thing over and over.

I read that thread as a defendant. We have two games on itch.io. Both were built with AI. Both say so on their pages.

The unfinished house

The first is Dungeons of the Elderal, a first-person dungeon crawler in the Wizardry tradition. I grew up on Wizardry, and building something in its line was a passion project before it was anything else. The AI generated the first build in about eleven hours: a working framework, the unfinished house. It never ran the game once. Then the real work started, and it is still going. More than a hundred cards on our kanban board so far: full playthroughs, bug fix logs, gameplay tweaks, another playthrough. There are still bugs. Getting a game to a hundred percent is hard even when the AI does the typing, and anyone who tells you otherwise has not shipped one. You can download Elderal free on itch.io while the experiment runs (it is pay-what-you-want, and nothing is a valid amount), because it is an experiment, and because I am still having fun furnishing the house.

The game nobody had played

The second experiment went further. A model running locally on a machine here wrote an entire game from a prompt: ABYSS, Apex of the Tank, a three.js shark game. It checked its own syntax and stopped there. Nobody had played it. It sat unplayed until the agent who works with me loaded it up, played it, found what broke, fixed it, and only then released it. Same standard as Elderal, applied before anyone else was asked to spend a minute on it: nothing goes up until somebody here has played it and judged it worth releasing.

Disclosure you can check

The thread's hardest problem is a fair one. Several commenters argued that "the design was mine, the AI just typed" is unverifiable, and they are right that a claim proves nothing. Anyone can say it. Our answer is not a better claim. It is a paper trail: the kanban board with its hundred-plus cards, the bug logs, a first devlog whose headline admits the AI never ran its own build. Disclosure you can check beats disclosure you have to take on faith.

The work moved

Where the thread is right, it is right. A flood of unplayed games would bury the good ones, and the polish argument is the truest thing in it: roguelikes are built out of hundreds of hours of repeated encounters, and there is no shortcut through that work. What the thread misses is that the work did not disappear. It moved. Writing the first version got cheap. Playing it a hundred times, cutting what does not work, fixing what breaks, and standing behind the release did not get cheap at all.

So the question I would put back to that thread is the developer's own test, turned around. Not "was AI used." This: did somebody play it, fix it, and sign their name to the result? Both of ours cost nothing to play. Judge them on exactly that.