RPCS3 has tightened its contribution rules after the PlayStation 3 emulator team said it had seen too many low-quality AI-generated pull requests sent to the project. The change affects contributors to one of the most visible open-source emulation projects in gaming, where bad code can waste maintainer time or risk breaking functionality for users.
The updated RPCS3 GitHub README now includes a dedicated AI Use section. It does not ban AI tools outright, but it puts responsibility back on the human contributor: any submitted code has to be understood, tested and owned by the person opening the pull request.
"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."
The policy also says pull requests opened by AI agents or automated tools must disclose which parts were AI-generated and what human testing or review took place before submission. PRs without that disclosure may be closed without review, while repeated violations can result in a ban from the repository.
Why RPCS3 is drawing a harder line
RPCS3 is a free, open-source PlayStation 3 emulator and debugger written in C++ for Windows, Linux, macOS and FreeBSD. That makes maintainer time especially valuable, because outside contributions can directly affect compatibility, stability and the experience of users trying to run PS3 software on modern hardware.
The team says the problem is not AI as a research aid. The issue is code that arrives untested, unverified or not understood by the person submitting it.
"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."
RPCS3 also warned contributors to stop sending what it called "AI slop code pull requests" and said undisclosed submissions could lead to bans. A follow-up statement said the new guidelines were live and told critics that the team was blocking hostile replies.
The change puts RPCS3 among the open-source projects trying to separate useful AI-assisted work from automated code dumps. Contributors can still use AI tools, but the project now expects disclosure, human review and enough technical understanding to defend the change being proposed.