RPCS3 says no to AI slop code with new code guidelines
RPCS3 posts strict AI guidelines to combat “AI slop code”
The team behind RPCS3, the PlayStation 3 emulator, has taken action against “AI slop code” due to its impact on the emulator’s development. The team has reported that it has had to revert many “slop PRs” (pull requests) that caused major regressions within the PS3 emulator. RPCS3 now has official AI guidelines that set clear limits on AI utilisation. AI is not banned, but users are expected to disclose their AI use and to “fully own and understand all the code they submit.
With these new guidelines, RPCS3 calls for AI code submissions to be disclosed. Furthermore, details on the “human testing” conducted need to be disclosed. This is to battle the “rise in untested and unverified AI-generated slop being submitted”. Pull Requests that do not disclose their use of AI may be closed without review.
AI isn’t banned, but code submissions need to own their use of AI
For RPCS3 to be maintained and improved, people need to understand its codebase. As such, all communications with the RPCS3 team must be handled by a human contributor. Additionally, contributors must understand the code they are submitting. Even if the code works, it must be known why it works.
The RPCS3 team has started banning “AI bros” on social media who are displeased by the implementation of these guidelines. Honestly, the RPCS3 team’s guidelines are fair and reasonable. AI tools are not banned. The RPCS3 team just wants code submissions to be understood by their contributors and for their time to be wasted less on analysing “AI Slop code”.
Our guidelines for submitting AI-generated code are now up in our repository!
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. https://t.co/yMtczjXQN1
— RPCS3 (@rpcs3) May 11, 2026
Below are RPCS3’s full AI guidelines. These guidelines should help the RPCS3 team handle more legitimate pull requests and prevent bad AI code from entering RPCS3’s codebase.
AI Use
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.
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.
**Pull requests opened by AI agents or automated tools must include a disclosure in the PR description** stating the scope of AI involvement — 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.
If you are unsure about your work, open a discussion issue to talk it through with the team, or reach out to a maintainer on [Discord](https://discord.gg/RPCS3).
2026 has already seen the RPCS3 team deliver major progress. Right now, 73.93% of all PlayStation 3 games are playable using RPCS3. Note that at the start of this year, RPCS3 had passed the 70% playability threshold. That’s fast progress.
If you want to use AI tools to help improve RPCS3, there’s nothing to stop you from doing so. However, this AI code must be documented as such, and you must understand the code you are submitting. Furthermore, your code is expected to be tested.
Overall, RPCS3’s new AI guidelines are fair and reasonable. The RPCS3 team shouldn’t have to review untested AI-generated slop code. Contributors should respect RPCS3 and the team behind it, and ensure their code is well understood, fully documented, and tested.
You can join the discussion on RPCS3’s AI guidelines on the OC3D Forums.
