The team behind RPCS3, the well-known open-source PlayStation 3 emulator, has updated its rules for code submissions after dealing with too many AI-generated pull requests that created extra work for maintainers.
In open-source projects, a pull request is a proposed change that someone wants merged into the main codebase. In this case, the concern is not normal help from contributors, but code produced through so-called vibe coding, where a person asks a large language model to generate code and then submits the result.
RPCS3’s team said it had seen a rise in untested and unchecked AI-made code being sent to the project. That kind of submission can slow down maintainers, because someone still has to review, debug, and verify what was handed in.
The bigger risk is that poor changes can slip through and be merged. If that happens, the emulator may break for users, which is a serious problem for a project that depends on accuracy, testing, and careful reverse engineering.
What The New Rules Allow
The updated guidance does not fully ban AI tools. Contributors may still use them for research and reverse engineering work. The line is drawn at responsibility: anyone submitting code must understand it, own it, and be able to stand behind it.
RPCS3 also made clear that communication with the team must come from the human contributor. That includes code, comments inside the code, and GitHub discussion. The project does not want an AI agent speaking for the person making the submission.
The team warned that repeated violations can lead to a repository ban. In plain terms, using AI as a helper is one thing; sending in unverified code that the contributor cannot explain is another.
The message brought some pushback from people who support vibe coding. RPCS3’s social account responded firmly, saying it would block hostile replies and urging people to learn debugging and coding instead of leaving behind low-value generated work.
Z-retro’s view is that the rule is a practical one: AI can be useful around old hardware research, but emulator projects still need human care, testing, and accountability to keep the work reliable for everyone.
