RPCS3 Team Cracks Down on AI-Generated Code: 'Stop Peddling Slop'

The open-source PS3 emulator RPCS3 has become the latest project to push back against the influx of AI-generated code submissions, with its development team explicitly asking contributors to 'stop peddling AI-generated slop.' The project, which has been manually developed since 2011, has recently seen a surge in untested, AI-generated code being submitted as pull requests, prompting a firm response from maintainers.

RPCS3 represents a significant achievement in emulation technology, allowing gamers to play PS3 exclusives on modern PC hardware with nearly the entire PlayStation 3 library supported. The project has required years of dedicated reverse engineering and meticulous coding to achieve this compatibility. However, the team's patience has been tested by what they describe as 'low-effort, AI-generated submissions featuring untested code, largely churned out by large language models and subsequently published by users who don't fully understand coding.'

In a straightforward message posted on X (formerly Twitter), the RPCS3 team made their position clear: 'Please stop submitting AI slop code pull requests to RPCS3. We will start banning those who do so without disclosing it. 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.'

The team quickly updated the project's contribution guidelines to explicitly address the issue. '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,' the guidelines state. 'You can't possibly handwrite the type of sh*t AI slop we have been seeing.'

Despite the strong language, the updated guidelines don't completely prohibit AI assistance. The team clarifies that using AI for research or reverse-engineering isn't out of the question. However, anyone submitting code must understand the ins and outs of every line and take full ownership of it. This includes typing out all communication personally rather than letting AI bots speak for them in comments or pull requests—a practice that clearly got on the RPCS3 team's nerves.

The stance reflects a growing tension in the software development community between AI-assisted coding and traditional, manual development approaches. While AI tools can potentially speed up certain coding tasks, they often produce code that works superficially but contains hidden issues or doesn't fully understand the context of the project it's being added to.

For the RPCS3 team, the issue isn't just about code quality—it's about respect for the project and its contributors. 'As for all the AI bros seething on our socials, we're simply blocking you. Learn how to debug and code, and leave behind something useful to humanity when you're gone instead of peddling slop,' the team wrote.

This approach contrasts with some other open-source projects that have either embraced AI assistance or haven't yet established clear policies. The RPCS3 team's position emphasizes that quality matters more than quantity, and creating something worthwhile requires real critical thinking, effort, and understanding.

For developers looking to contribute to open-source projects, the RPCS3 case serves as a reminder that transparency about AI usage is becoming increasingly important. As AI tools become more prevalent in coding, projects will likely need to establish clear guidelines about how and when AI can be used—balancing potential efficiency gains with the need for maintainable, understandable code.

The RPCS3 project's GitHub repository now includes explicit rules about AI usage, requiring contributors to disclose any AI assistance and take full responsibility for their submissions. This approach may become a model for other projects grappling with similar issues as AI coding tools continue to evolve.

For more information about RPCS3 and its contribution guidelines, you can visit the official RPCS3 GitHub repository.