Saber Interactive has recently updated the Steam listing for its title Rideshare Simulator to include a clear disclaimer about the use of artificial intelligence in the game's development. This move comes after a heated debate sparked by accusations that the studio had terminated a writer working on the project and substituted her contributions with text generated by AI tools. The full text of the newly added notice reads as follows: "This update follows comments from Saber CEO Matt Karch regarding writer Stella Sacco, who worked at Saber from July 2023 to July 2024, and stated she was removed from Rideshare midway through development and replaced with ChatGPT, while alleging other then-unannounced use of AI in the game's development." In the original controversy, former staff member Stella Sacco claimed that she was dismissed from the Rideshare Simulator team part‑way through the production cycle and that her responsibilities were taken over by ChatGPT, a large language model.
She also suggested that additional, undisclosed AI tools had been employed throughout the creation of the game, raising questions about transparency, authorship, and the ethical treatment of creative talent. Matt Karch, the chief executive of Saber Interactive, responded publicly to these allegations.
He said that Sacco had "been replaced by someone more talented and terminated for a variety of reasons a few months later," and added that, looking back, he "would have been happy to replace her with AI." Karch's remarks were intended to clarify the studio's stance but ended up intensifying the backlash, as many observers felt the comments downplayed the contribution of a human writer and suggested a cavalier attitude toward AI substitution. During an interview with the podcast This Week In Videogames, Karch further elaborated, "Stella who?
I had to ask Claude because I have never spoken to her or seen her. We have already said we are using AI for certain parts of the game and will update the Steam page once we have finalised the feature set." He framed the use of AI as a consumer benefit, stating, "We look at our use of AI in this particular game, which will be a lower priced title, as a plus for consumers." The controversy escalated when Sacco posted on the social platform BlueSky over the weekend, noting that Karch had "apologised unreservedly for the awful way he spoke about me in the press." She wrote, "I've been firm from the beginning that I was telling the truth; I think we can all now agree that it's been borne out. Matt expressed a desire to make it right with me; at this time I don't really know what that looks like for me, and I'll have to take some time to sit with it, but I do at least accept his apology." Karch later issued a separate statement on LinkedIn, acknowledging his own emotional reaction to the unfolding drama. "I unfortunately got triggered by certain later comments (for reasons I won't get into) and shot first and thought second about how to respond," he admitted.
"It happens and I am a human being. I have done what I can to rectify." The incident highlights several broader issues that are currently shaping the video game industry.
First, the integration of AI tools such as ChatGPT, Claude, and other large language models into creative pipelines is accelerating. Developers are leveraging these systems to generate dialogue, quest descriptions, marketing copy, and even code snippets.
While AI can dramatically reduce production time and costs, it also raises concerns about the displacement of skilled writers, designers, and other creative professionals. Second, the episode underscores the importance of transparency.
Gamers and industry observers increasingly demand clear disclosures about how AI is used in games they purchase. In response, platforms like Steam have begun to require developers to label AI‑generated content, and some studios are voluntarily adding notices to avoid accusations of misleading consumers.
Third, the situation illustrates the delicate nature of public communication in the digital age. A single off‑hand remark from a CEO can quickly become a flashpoint, especially when it touches on employment practices and emerging technology. Karch's admission that he "shot first and thought second" reflects a common pitfall: reacting impulsively on social media without fully considering the ramifications for both the individuals involved and the company's reputation. From a legal standpoint, the alleged replacement of a human writer with AI could intersect with employment law, intellectual property rights, and contractual obligations.
If a writer's contract stipulates that their contributions will be used in the final product, substituting AI-generated text without proper consent might constitute a breach. Conversely, studios may argue that AI tools are simply another resource in the toolbox, akin to using a graphics engine or sound library, provided they respect any existing agreements.
For the broader creative community, the case serves as a cautionary tale. Writers, artists, and developers are urged to negotiate clear terms regarding the potential use of AI in their work, ensuring they retain credit, compensation, and the ability to opt out if they are uncomfortable with automated replacements. Looking ahead, Saber Interactive's decision to add the AI disclaimer may help mitigate some of the reputational damage, but the company will likely need to take additional steps to rebuild trust.
This could include establishing a formal AI policy, offering restitution or acknowledgment to former staff like Sacco, and engaging in open dialogue with the gaming community about how AI will shape future titles. In summary, the controversy surrounding Rideshare Simulator illustrates the growing pains of an industry at the crossroads of technology and creativity. While AI promises efficiency and new possibilities, it also forces studios to confront ethical questions about authorship, transparency, and fair treatment of human talent.
Saber Interactive's recent actions—adding a Steam disclaimer and issuing an apology—represent an early attempt to navigate these challenges, but the conversation is far from over, and the outcomes will likely influence how other developers approach AI integration in the years to come.