If you have been following the slow-motion disaster that is AI slop flooding open-source repositories, here is the latest chapter: the team behind RPCS3, the open-source PlayStation 3 emulator, has publicly told users to stop submitting AI-generated code pull requests to their GitHub page.
The message posted to X on May 9, 2026 was direct: "Please stop submitting AI slop code pull requests to RPCS3. We will start banning those who do without disclosing. There are plenty of resources online to learn how to debug and code instead of generating slop that you don't understand and that doesn't work."
Polite enough. The replies that followed? Considerably less so, and honestly, completely understandable.
What RPCS3 is actually dealing with
RPCS3 has been in active development since 2011 and remains the dominant PS3 emulator available. The project has reached a point where roughly 70% of the PlayStation 3's library is fully playable, a milestone built in large part through genuine community contributions on GitHub. That contributor pipeline is exactly what AI vibe-coders are now clogging.
Here's the thing: open-source emulation projects like this live and die by the quality of their pull requests. Every PR that needs to be reviewed, identified as useless AI output, and rejected is time the actual developers are not spending on real improvements. Multiply that across dozens or hundreds of junk submissions and the cost to the project becomes genuinely significant.
When one user pushed back and asked how the team could even tell the difference between AI-written and human-written code, RPCS3 had a sharp response: "You can't possibly handwrite the type of shit AI slop we have been seeing." Hard to argue with that.
This is not an isolated problem
The RPCS3 situation is part of a pattern that has been building across open-source development for months. Back in February, Rémi Verschelde, project manager of the Godot Engine, said the Godot GitHub had become so saturated with AI-generated pull requests that he was considering hiring additional maintainers specifically to handle the volume of junk submissions.
RPCS3 has stated that contributors who submit AI-generated code without disclosing it will face bans. If you are a genuine contributor, the team is asking for transparency, not a blanket ban on AI tools.
Two high-profile open-source gaming projects dealing with the same problem within a few months of each other signals that this is not a niche grievance. The tools that make it easy to generate plausible-looking code have made it equally easy to flood maintainers with submissions that look like contributions but function as noise.
GitHub PR review queue
What the RPCS3 team actually wants
The ask from RPCS3 is not complicated. Learn to code. Use the resources available online. If you want to contribute to a project as technically demanding as a PS3 emulator, put in the work to understand what you are submitting.
Emulating the PS3's Cell processor architecture is genuinely one of the harder problems in emulation development. The Cell's unconventional design, with its main processor and seven synergistic processing elements, is not something a language model can meaningfully patch without a human who understands what they are doing behind the wheel. Submitting AI-generated code to a project like this is not a shortcut. It is just extra work for someone else.
For players, the good news is that RPCS3 is drawing a clear line before this becomes a maintenance crisis. For anyone curious about the state of emulation and preservation more broadly, our gaming guides and game reviews cover the titles you might want to revisit through emulation.
The RPCS3 team is not shutting the door on community contributions. They are asking that those contributions come from people who actually understand what they are submitting. That is a reasonable standard for any software project, let alone one maintaining compatibility with hundreds of PS3 titles. Watch how other major open-source gaming projects respond to the same pressure over the coming months.
