The people behind the open source PS3 emulator RPCS3 are sick of dealing with bad code submissions from AI users, and are telling vibe coders exactly where they can stick it. The project has updated its policies on AI use, promising to ban anyone who tries to pass off AI-generated work as their own, and the team has been making its feelings on "AI slop" known on social media.
"Please stop submitting AI slop code pull requests to RPCS3," reads a tweet from RPCS3 posted on May 9 (thanks, Time Extension). "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."
As open-source software, anyone is free to make contributions to RPCS3 through pull requests. If the project's maintainers think it's a valuable addition, they'll then merge that update code into their main release. The rise of AI-generated code – typically known as "vibe coding" within the community – means it's suddenly a lot easier for anyone to make submissions, even if they haven't thoroughly tested them beforehand.
That's created some headaches for RPCS3's developers. AI adherents will tell you that vibe coding is great – heck, even Gabe Newell has been singing AI's praises from a coding perspective – but that's not what RPCS3 has been seeing. Addressing concerns that they might end up banning legitimate code with these policies, the devs respond, "It either is obviously slop or isn't. You can't possibly handwrite the type of shit AI slop we have been seeing."
In another tweet, they say that "programmers that can understand the problem, the solution, and the implementation can write the same code without AI, and tend to use LLMs to automate repetitive code refactoring instead. It is not the case with the AI slop PRs we have seen."
To that end, they're not fully banning AI-generated code – they're simply requiring submissions to designate which parts were vibe-coded. "Pull requests opened by AI agents or automated tools must include a disclosure in the PR description stating the scope of AI involvement – which parts were AI-generated and what human testing or review was performed prior to submission," according to the newly updated readme on Github. "PRs that omit this disclosure may be closed without review."
"As for all the AI bros seething on our socials, we're simply blocking you," the devs say in one last tweet. "Learn how to debug, code, and leave behind something useful to humanity when you're gone, instead of peddling slop."
