Saber Interactive Denies Replacing Writer with ChatGPT on Rideshare Game

Saber Interactive CEO Matthew Karch has publicly stated that neither Saber nor developer Unigine replaced any writers with AI on Rideshare "Stimulator," a driving simulation game announced last month. Former lead writer Stella Sacco contradicts that directly. She posted on Bluesky that she was the lead writer on the project and was replaced by ChatGPT partway through development, adding that all passenger voices are also AI-generated, with none of this disclosed on Steam.

What happened

Saber Interactive CEO Matthew Karch made a public statement denying that any writers were replaced by AI on Rideshare “Stimulator,” a game developed by Unigine and announced last month. The denial came directly in response to claims by Stella Sacco, who identified herself as the former lead writer on the project.

Sacco posted on Bluesky: “I was lead writer on this one. And Saber replaced me with ChatGPT midway through development. All the passenger voices were AI too. Either they changed direction at some point or they’re not disclosing it on Steam.”

That last point is significant. If AI-generated writing and voice work are present in the shipped product and not disclosed to buyers, it raises a consumer transparency question that goes beyond a simple dispute between an employer and a contractor.

Why it matters

This story is a clear example of the gap between corporate messaging and on-the-ground reality when AI tools enter a production workflow. Sacco’s account is specific: she was replaced mid-project, not after a completed contract. She names both the tool (ChatGPT) and the affected assets (writing and passenger voices).

Karch’s denial does not engage with those specifics. He issued a blanket statement covering both Saber and Unigine without addressing whether contractors, rather than full-time employees, may have been let go, or whether AI-generated content was added after a writer’s exit.

For studios and the agencies and brands that commission creative work, this conflict points to a growing pattern: AI tools are being folded into production quietly, and the people whose work they displace often have no contractual protection or disclosure obligation on the studio’s part.

It also matters for anyone tracking AI disclosure standards. Steam currently has no mandatory requirement for publishers to label AI-generated voice or writing, so players have no reliable way to know what they’re buying. This is an area where platform policy is visibly lagging.

Our take

The CEO’s statement was broad where the accusation was precise. That mismatch rarely helps. Sacco did not say Saber replaced a team with a general AI strategy. She said she, personally, was dropped mid-development and replaced with a specific tool, and that the audio was also AI-generated. A denial that doesn’t address those specifics is not a denial of those specifics.

For business owners thinking about where this lands closer to home: the same dynamic plays out in agency and freelance content work every day. If you’re using AI to reduce headcount on creative work, the people affected will eventually say so publicly. The question of whether you disclosed it to your clients or customers is increasingly the reputational exposure point, not the AI use itself.

Studios, brands, and agencies that want to avoid this exact situation should build disclosure into their workflows now, before platform rules force it. We cover the broader question of AI writing transparency regularly in our AI news coverage, and it’s a topic that keeps surfacing in our AI integration work with clients who need clear policies before shipping AI-assisted content.

What to do about it

1. Audit any ongoing creative projects where AI tools have been introduced and identify which deliverables contain AI-generated content.
2. Check your contracts with freelancers and contractors to see whether AI substitution is addressed, and update them if not.
3. Add a disclosure note to any published product that includes AI-generated writing or voice, regardless of whether the platform currently requires it.
4. Watch Steam and other platform policies on AI disclosure closely as this becomes a more visible issue.

Source: The Verge · AI