AI Slop Forces Major Decompilation Tool to Shut Down

Ever cheered when a decompilation project hit 100%? That satisfying tick of the progress bar might be a thing of the past. Decomp.dev, a site that tracked the painstaking, human-driven process of decompiling classic games, is shutting down. Developer Luke "encounter" Street announced the closure, citing the negative effects of AI on the community.

For years, decomp.dev gamified decompilation. As each line of code was recreated and matched with functions from the original game, a percentage meter would tick up gradually until it reached the coveted 100% mark. It was a simple celebration of human effort. But that simplicity has gotten a lot more complicated with the rise of AI. "It is now clear that, with the right guidance, human input, and code reviews, AI can expedite the decompilation process in a significant way," Street writes. "What is also now clear is that the community aspect of decompilation has been broken."

So what went wrong? Street points to bad actors abusing open-source projects. That includes "forking existing decompilation projects to 'finish' them with AI," even if it goes against the wishes of the original developers. Some AI-first devs are also "racing to port games" ahead of traditional developers. "While community members put in the effort to decompile a game, opportunists have frequently raced to release a half-baked, barely-functional port from it."

To understand the frustration, it helps to know the terms. Decompilation is the painstaking process of reverse-engineering a game's code, recreating every function line by line. Devs can then recompile that code, often using it to port games to new platforms. "For years, decompilation communities attempted to establish that decompilation is primarily for research: we love these games and want to understand how they work, and to uncover the mysteries that the original developers left behind," Street says. "That's not to say that ports aren't fun too; they're just not the sole reason a decompilation exists."

Then came static recompilation tools, which skip decompilation entirely by automatically translating original code to run on modern PCs. AI entered the picture, and the barrier to creating static recompilation-based PC ports went from "low" to "essentially nonexistent." Street explains: "decomp.dev was originally designed to gamify decompilation: watching the progress go up was a fun way to stay motivated when every fraction of a percent took real human effort. Today, that same idea has warped decompilation into a hollow numbers game, exacerbated by folks who just want to burn tokens to make number go up or 'port game to PC', all else be damned."

While the increased attention has brought in genuine folks who want to learn and contribute meaningfully, Street believes that decomp.dev serving as a public index and leaderboard is now causing more harm than good. The community's love of recomps has gotten so strong that even Microsoft seems to want in on it, and AI is certainly making these recomps easier to build. But for many in the community, it's also wrecking the beauty of the effort that it took to get here in the first place, with real, human time and effort on display in the form of these massive decompilation projects, and an emphasis on the work rather than just the output.

Here's hoping the old guard continues doing the work the old-fashioned way. What do you think about AI's impact on decompilation? Will you miss seeing those progress bars tick up? Let us know in the comments.