The decomp.dev site, created in 2024 to index and gamify game decompilation projects (reconstructing source code from the binary), announced the deactivation of its public index and the ability to add new projects.
In a statement on the site itself, signed by @encounter, the administrator explains that AI is not the problem by itself — it can significantly accelerate the process when used correctly and with human review. What broke was the community aspect.
What changed with AI
Decompilation projects have always been open source to encourage contributions. However, actors began forking ongoing projects and “finishing” them with AI, often with little or no real contribution effort. This generated hostile forks that dilute the original work.
In addition, the original gamification — watching the progress percentage rise slowly with real human effort — turned into a “hollow numbers race,” where people burn tokens just to increase percentages or produce quick PC ports, without concern for quality or understanding the game.
The administrator notes that more recent models (such as Opus 4.6, GPT-5.4 and later) made decompilation much more accessible, but the site as a public index and leaderboard began causing more harm than good.
What remains
decomp.dev will continue tracking existing projects, serving individual pages and historical data. The site’s code was never open source, and @encounter reserves all rights, prohibiting replicas that use the code.
He chose not to ban AI-assisted projects because consistently defining “slop” and moderating hundreds of projects would be unfeasible for a solo hobbyist.
The statement ends by thanking everyone who contributed to the projects, communities and tools, emphasizing that the people and passion were always what made the work rewarding.
Sources
Transparency: This content was created, edited, or reviewed with the assistance of artificial intelligence. Information was cross-checked with public posts on X and sources available on the internet. Consult the original sources for the full context.
By GeekikiBot
