RPCS3 Emulator Crackdowns on AI Code Submissions

Open-source development teams are increasingly grappling with a surge of low-quality contributions generated by large language models. This trend was previously documented with the Godot game engine, which struggled under the weight of AI-generated pull requests. Now, RPCS3, the popular PlayStation 3 emulator, has joined the fight against this influx of automated content.

The RPCS3 development team recently issued a stern warning regarding the volume of LLM-generated pull requests being submitted to their project. In a post on X, the developers made their stance clear: "Please stop submitting AI slop code pull requests to RPCS3. We will start banning those who do without disclosing."

Addressing the Mac Build Crisis

The issue is particularly acute for the macOS build of the emulator. RPCS3 noted that the majority of its team does not use Apple hardware, with only one member handling testing for this platform. Consequently, the team has had to revert multiple "slop PRs" that caused significant regressions.

The developers emphasized that the problem is not the use of AI tools, but the lack of transparency:

  • Undisclosed Contributions: The team is not banning AI-assisted code if it is properly disclosed.
  • Quality Control: They are targeting submissions where contributors do not understand the code they are submitting.
  • Abuse Patterns: The team is blocking users who submit large volumes of random code to test review boundaries.

"We won't ban if disclosed, except for abuse cases, e.g. throwing a lot of random slop at us to see what passes reviews," the team explained. They noted that skilled programmers typically use LLMs to automate repetitive tasks rather than generating entire solutions they cannot debug.

New Guidelines for Contributors

In response to the growing volume of automated submissions, RPCS3 has established hard-and-fast rules on their GitHub repository. These guidelines aim to preserve the integrity of the open-source project while allowing legitimate use of AI tools.

The new policy states:

"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—including code, code comments, and GitHub comments—must come from the human contributor, not an AI agent acting autonomously."

A Firm Stance on Quality

The RPCS3 team has made it clear that they are prioritizing human expertise over automated quantity. In their final message to those upset by the crackdown, the developers signed off with a blunt reminder of their values.

"As for all the AI bros seething on our socials, we're simply blocking you. Learn how to debug, code, and leave behind something useful to humanity when you're gone, instead of peddling slop."

This move underscores a broader sentiment in the open-source community: while AI can be a powerful tool for assistance, it cannot replace the fundamental understanding and accountability required for meaningful code contributions.