Saber Interactive added a detailed AI disclosure to the Steam page for Rideshare Stimulator on Aug. 14, ending a week of controversy that began when a former employee said she was replaced by ChatGPT. The disclosure confirms the game uses AI for voice generation, localization, and optional free-roam content, while the main campaign remains human-written.
Game developer Stella Sacco posted on Bluesky on Aug. 11 that "Saber replaced me with ChatGPT midway through development." Saber CEO Matthew Karch responded with a scathing comment to This Week In Video Games, insulting Sacco and saying he would have "in retrospect have been happy to replace her with AI." He confirmed AI was used in development but said the studio was waiting for a "finalized feature set" before adding a disclosure on Steam.
Saber's official statement to Game File was more measured: no writers were replaced by generative AI, but the technology was used in the game. The studio then updated the Steam page with a detailed breakdown of where AI appears.
What the disclosure says
"The main Campaign story, characters, and dialogue are written by a team of human writers. AI tools are used for voice generation and some localization," the Steam page now states. "The optional Free Ride mode includes AI-generated passenger missions and localized dialogue."
The disclosure notes that Free Ride mode is separate from the main campaign and can be skipped. Radio stations are also split: some feature human-made music, others AI-generated music, and stations with AI content are labeled in the game.
Sacco also reported on Bluesky that Saber revoked her access to a development build of the game on Steam. She confirmed that Karch privately apologized to her for his comments.
What this means for developers
The controversy highlights a practical problem for studios integrating AI tools: players expect transparency, and studios are still figuring out when and how to disclose. Saber's initial silence, followed by a hostile executive response, turned a routine AI workflow question into a public relations incident.
For developers working with AI for Software Developers tools, the lesson is about process. If your studio uses generative AI for assets, dialogue, or code, the disclosure policy should be settled before launch, not improvised after someone speaks publicly about it. The executive response matters too - dismissing an employee's concern in public can escalate a manageable issue into a story that follows the product.
The case also highlights how AI disclosure is becoming a standard part of shipping software. Players and users are checking for it, and the conversation around AI in Game Development is moving from "whether" to "how much and where."
Why this matters for IT and development professionals
If you're building AI-assisted workflows, the Rideshare Stimulator case shows that the technical implementation is only half the work. The other half is documenting what the AI does, where it's used, and what it replaces. That documentation needs to be ready before release, not after a controversy forces it.
There's also a direct career lesson for developers: the technology is not the only thing that changes when AI enters the pipeline. Roles shift, expectations shift, and the way your employer communicates those shifts matters. If your studio or company is adopting generative AI, the disclosure policy and the treatment of affected staff will be part of the public record - whether you plan for it or not.
Your membership also unlocks:
