Technology

Repentance Plus Pulls Undisclosed AI Music After Steam Review Backlash

Martin HollowayPublished 4 min readBased on 1 source
Reading level
Repentance Plus Pulls Undisclosed AI Music After Steam Review Backlash
Image by Setupx3D from Pixabay

Repentance Plus, the expansion for The Binding of Isaac from Nicalis, Inc., was review-bombed on Steam after undisclosed generative AI music was found in the game. The Verge reported the episode on 2026-11-22 GMT.

The AI-generated songs sat inside a section themed on Grand Theft Auto. Audio files extracted from the build carried Suno metadata, which pointed to tracks on Suno's site. Suno is a service that generates music from text prompts. That embedded trail is how the material was traced to its source. Within hours of the discovery, Nicalis updated Repentance Plus and removed the generated music files.

Creator Edmund McMillen apologized. He said he had no idea the GTA parody used generative AI music, placing responsibility for the material in a context he did not control. The apology does not explain how the tracks entered the build in the first place.

The disclosure rules are the other half of the story. Valve requires developers to disclose how and when they use generative AI in development. Under that policy, the missing disclosure is what turned a single audio section into a platform-level problem. It is also why the Steam review section, rather than only the game's own community, registered the reaction.

In a 2024 TikTok, he described AI in game development as "uninspired and bland." Readers on Steam could set that remark against the discovery of generated audio in one of his studio's titles. The review campaign leaned on that juxtaposition without needing to add anything to the facts.

In my view, the episode is less about one soundtrack than about provenance. A game build is assembled from assets that originate in many places: in-house composers, licensed libraries, contractors, middleware, and tools that developers may not think of as generative. Once a generated track is in the package, working out who approved it and how it got there is difficult to do from the team's own records. The Suno metadata made the answer possible here because the files kept a trail back to their origin. Most shipped builds do not carry that trail by default.

The broader context here is the disclosure regime that platforms are building around generative content. Valve's requirement puts the obligation on the developer to state how and when generative tools were used. That is easier to meet when studios treat asset ingestion as an auditable pipeline, with source tags, licensing records and tool provenance stored alongside the files. The same embedded metadata that exposed the Repentance Plus tracks is a signal a studio can keep deliberately, rather than discover after release.

For developers, the immediate lesson is operational. Audit the audio, art and text that reached a build through outside hands, record what was generated and by whom, and tie disclosure statements to the actual asset list rather than to memory. For players, the episode shows that a review section can act as an enforcement layer for disclosure, quickly and bluntly. Whether that serves the medium well over time depends on whether studios make provenance cheap enough to verify before a patch is needed.