Open-source development teams are increasingly grappling with the influx of AI-generated contributions, a phenomenon that has gained momentum since the advent of large language model (LLM) technology. Earlier this year, we reported on the challenges faced by the free and open-source game engine Godot, which struggled under the weight of AI-generated pull requests (PRs). Now, the popular PlayStation 3 emulator RPCS3 finds itself in a similar predicament.
RPCS3 Takes a Stand
As highlighted by GamingOnLinux, the RPCS3 development team has publicly addressed the surge of LLM-generated PRs flooding their project. In a candid post on X, the developers urged contributors to cease submitting what they referred to as “AI slop code.” They issued a stern warning: “We will start banning those who do without disclosing.” The team emphasized the importance of understanding the code being contributed, suggesting that there are ample resources available for learning how to debug and code effectively.
In further discussions, the RPCS3 team noted a particularly alarming trend: an increasing number of AI-generated PRs targeting their macOS build. Most of the team members do not utilize macOS, with only one member responsible for testing the emulator on Apple systems. This has led to several instances where poorly constructed PRs caused significant regressions, prompting the team to revert changes. “Enough is enough,” they stated, expressing their frustration with the situation.
In response to inquiries and some pushback from AI advocates, the developers clarified that their concern lies not in the use of AI code per se, but rather in the lack of disclosure. They stated, “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 pointed out that skilled programmers who understand the intricacies of problem-solving and implementation can write code without relying solely on AI, often using LLMs to streamline repetitive tasks instead.
To address these challenges, RPCS3 has established a new set of guidelines regarding AI contributions, which are now available on their GitHub repository. The rules stipulate that while the use of AI tools for research and reverse engineering is allowed, contributors must fully comprehend and take ownership of all code they submit. Furthermore, all communication with the team—including code comments and GitHub interactions—must originate from the human contributor, not an AI acting independently.
In closing their message on X, the RPCS3 team reiterated their commitment to quality contributions: “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.”
Popular PlayStation emulator clamps down on AI submissions: ‘Leave behind something useful to humanity when you’re gone, instead of peddling slop’
Open-source development teams are increasingly grappling with the influx of AI-generated contributions, a phenomenon that has gained momentum since the advent of large language model (LLM) technology. Earlier this year, we reported on the challenges faced by the free and open-source game engine Godot, which struggled under the weight of AI-generated pull requests (PRs). Now, the popular PlayStation 3 emulator RPCS3 finds itself in a similar predicament.
RPCS3 Takes a Stand
As highlighted by GamingOnLinux, the RPCS3 development team has publicly addressed the surge of LLM-generated PRs flooding their project. In a candid post on X, the developers urged contributors to cease submitting what they referred to as “AI slop code.” They issued a stern warning: “We will start banning those who do without disclosing.” The team emphasized the importance of understanding the code being contributed, suggesting that there are ample resources available for learning how to debug and code effectively.
In further discussions, the RPCS3 team noted a particularly alarming trend: an increasing number of AI-generated PRs targeting their macOS build. Most of the team members do not utilize macOS, with only one member responsible for testing the emulator on Apple systems. This has led to several instances where poorly constructed PRs caused significant regressions, prompting the team to revert changes. “Enough is enough,” they stated, expressing their frustration with the situation.
In response to inquiries and some pushback from AI advocates, the developers clarified that their concern lies not in the use of AI code per se, but rather in the lack of disclosure. They stated, “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 pointed out that skilled programmers who understand the intricacies of problem-solving and implementation can write code without relying solely on AI, often using LLMs to streamline repetitive tasks instead.
To address these challenges, RPCS3 has established a new set of guidelines regarding AI contributions, which are now available on their GitHub repository. The rules stipulate that while the use of AI tools for research and reverse engineering is allowed, contributors must fully comprehend and take ownership of all code they submit. Furthermore, all communication with the team—including code comments and GitHub interactions—must originate from the human contributor, not an AI acting independently.
In closing their message on X, the RPCS3 team reiterated their commitment to quality contributions: “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.”