In response to questions (and more than a little AI evangelist bellyaching), the devs pointed out that it is not the use of AI code in PRs that is the issue for them, but that it is undisclosed. “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. Hint: programmers that can understand the problem, the solution, and the implementation can write the same code without AI, and tend to use LLMs to automate repetitive code refactoring instead. It is not the case with the AI slop PRs we have seen.”
The final result is a new set of hard-and-fast rules about AI code right there on RPCS3’s GitHub repo: “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.”
Back on X, the team signed off with a final message: “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.”
