{"id":579092,"date":"2026-05-12T01:56:21","date_gmt":"2026-05-12T01:56:21","guid":{"rendered":"https:\/\/www.newsbeep.com\/uk\/579092\/"},"modified":"2026-05-12T01:56:21","modified_gmt":"2026-05-12T01:56:21","slug":"learn-how-to-code-team-behind-ps3-emulator-rpcs3-has-had-enough-of-people-peddling-ai-slop","status":"publish","type":"post","link":"https:\/\/www.newsbeep.com\/uk\/579092\/","title":{"rendered":"Learn How To Code” – Team Behind PS3 Emulator RPCS3 Has Had Enough Of People “Peddling AI Slop"},"content":{"rendered":"

\""Learn<\/a> Image: Damien McFerran \/ Time Extension<\/p>\n

The team behind the excellent open-source PS3 emulator RPCS3<\/a> has been forced to update its guidelines for submitting AI-generated code after being inundated with time-wasting “vibe coded” pull requests.<\/p>\n

“Please stop submitting AI slop code pull requests to RPCS3,” says the team on social media<\/a>. “We will start banning those who do so 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.”<\/p>\n

A “pull request” is a proposal to merge code changes into an open-source project, while “vibe coding” refers to prompting a large language model (LLM) to generate code.<\/p>\n

Shortly after posting the message, the RPCS3 social media account confirmed<\/a> that its guidelines had been updated.<\/p>\n

Our guidelines for submitting AI-generated code are now up in our repository!<\/p>\n

As for all the AI bros seething on our socials, we’re simply blocking you.<\/p>\n

Learn how to debug, code, and leave behind something useful to humanity when you’re gone, instead of peddling slop. https:\/\/t.co\/yMtczjXQN1<\/a><\/p>\n

\u2014 RPCS3 (@rpcs3) May 11, 2026<\/a><\/p>\n

The updated guidelines read as follows<\/a>:<\/p>\n

“Use of AI tools for research and reverse engineering purposes is permitted. However, contributors are expected to fully own and understand all code they submit. Any communication with the team \u2014 including code, code comments, and GitHub comments \u2014 must come from the human contributor, not an AI agent acting autonomously.<\/p>\n

We have unfortunately seen a rise in untested and unverified AI-generated slop being submitted to this project. This wastes maintainer time and, in worse cases, such changes get merged and break functionality for all users. Repeated violations will result in a ban from the repository. Please be respectful of everyone’s time.<\/p>\n

Pull requests opened by AI agents or automated tools must include a disclosure in the PR description stating the scope of AI involvement \u2014 which parts were AI-generated and what human testing or review was performed prior to submission. PRs that omit this disclosure may be closed without review.”<\/p>\n

As you can imagine, the statement has triggered some negative reaction from vibe-coders.<\/p>\n

“As for all the AI bros seething on our socials, we’re simply blocking you,” the RPCS3 team added on social media<\/a>. “Learn how to debug, code, and leave behind something useful to humanity when you’re gone, instead of peddling slop.”<\/p>\n

\"Previous<\/a><\/p>\n

Prev<\/a><\/p>\n

\"Next<\/a><\/p>\n

Next <\/a><\/p>\n

\"Damien<\/p>\n

Damien has been writing professionally about tech and video games since 2007 and oversees all of Hookshot Media’s sites from an editorial perspective. He’s also the editor of Time Extension<\/a>, the network’s newest site, which \u2013 paradoxically \u2013 is all about gaming’s past glories.<\/p>\n