All stories
decomp.dev Debates Community reports

AI turned decompilation into a numbers race, says decomp.dev as it closes its index

The maintainer blames hostile forks and rushed PC ports for breaking collaboration. Existing project pages and historical tracking remain available.

Sources (3)

Why now An October 20 Hacker News submission renews attention to the sunset statement, already reported by VGC on October 19. The statement itself is undated; this is renewed discussion of an existing closure decision, not a new October 21 shutdown.

decomp.dev has disabled its public index and the addition of new projects after its maintainer said AI-assisted competition was damaging the community the tracker was built to support. The decision leaves existing individual project pages, historical data and tracking in place. It is a retreat from the public leaderboard, rather than the disappearance of every tracked decompilation.

The maintainer, encounter, describes projects being forked so outsiders can use AI to finish them, alongside races to ship rough PC ports using work those outsiders did not contribute to. These are the maintainer’s allegations and assessment of community behavior; the statement does not establish that every AI-assisted fork has those characteristics.

Matching code and making a port are different goals

Matching decompilation reconstructs source that compiles into the original machine code. A playable port is a separate outcome. encounter argues that conflating the two shifts attention from understanding a game toward claiming completion, turning progress percentages into a competition to spend tokens and increase the number.

The statement is unusually explicit that AI itself is not the sole problem. With guidance, human input and code review, encounter says it can substantially accelerate decompilation. The maintainer instead rejects the burden of defining and moderating acceptable work across hundreds of projects as a solo hobbyist. This is not a blanket ban on AI-assisted projects.

The discussion is new attention, not a newly dated announcement

VGC reported the decision on October 19, and a Hacker News submission followed on October 20 at 00:17 UTC. The original sunset page supplies no announcement timestamp. Those dates establish the sequence of reporting and discussion; today’s review does not reset the underlying event’s date or prove a surge in participation.

There is also a licensing distinction for anyone considering a replacement tracker. encounter says decomp.dev’s own code has never carried an open-source license and remains all rights reserved. That statement concerns the tracker code, not the licenses of the game projects it lists. A replacement cannot assume the site’s source is available for reuse simply because tracked projects welcome contributions.