They knew what was coming before they even logged on
In the digital agora of a Reddit AMA, the developers of Kingdom Come: Deliverance 2 found themselves answering not for their art, but for their humanity. Warhorse Studios, already braced for the confrontation, spent the session reassuring a skeptical community that real people still make their games — a defense that would have seemed absurd a decade ago and now feels like a necessary rite of passage. The moment reveals something larger: that the relationship between creators and their audience has been quietly rewritten by the fear of automation, and that trust, once eroded by industry-wide layoffs and algorithmic encroachment, does not return simply because a studio says the right words.
- Fans arrived at the AMA not to celebrate a game they love, but to interrogate the conditions under which it was made — a sign of how deeply labor anxiety has taken root in gaming communities.
- Accusations that Warhorse had fired human workers and replaced them with AI systems forced the developers into a posture of repeated, almost pleading denial.
- The studio had already debated internally whether to hold the AMA at all, revealing that even the developers understood they were walking into a minefield of their industry's own making.
- Every reassurance the team offered — we employ real people, we haven't replaced our staff — had to be delivered again and again, because the community had learned not to trust the first answer.
- The incident signals a new normal: major game releases may no longer be able to conduct promotional events without first passing through a gauntlet of questions about AI and labor.
The developers at Warhorse Studios knew what they were walking into. Before opening their Reddit AMA for Kingdom Come: Deliverance 2, the team had already debated internally whether to show up at all — artificial intelligence had become volatile enough inside their own offices that facing the community felt like a genuine risk.
They went ahead anyway. What followed was a session consumed almost entirely by one subject. Fans came with pointed questions about AI use in development, about whether workers had been let go and replaced with algorithms to cut costs. The accusations were specific and the skepticism was earned — players have watched studios announce layoffs dressed up as "optimization" and have learned to read between the lines.
The developers responded by insisting, repeatedly, that real humans make their games. The message required constant reinforcement because the community wasn't prepared to accept it on faith. In an industry where layoffs have become routine and AI tools are spreading faster than anyone can regulate them, a single assurance carries little weight.
What made the moment matter wasn't the back-and-forth itself, but what it represented. A promotional AMA for a major release had been overtaken by questions about labor — whether the people who built the game still had jobs, whether creative work was being quietly automated away. The technology question had become impossible to sidestep.
Warhorse found itself caught between a community increasingly attuned to how games get made and an industry actively experimenting with tools that could reshape that process entirely. Whether other studios face the same pressure — and how they choose to respond — will likely determine whether this kind of confrontation becomes a standard feature of game development in the years ahead.
The developers of Kingdom Come: Deliverance 2 knew what was coming. Before they opened the doors to a Reddit Ask Me Anything session, the team at Warhorse Studios had already wrestled with the decision internally. Artificial intelligence had become a live wire in their offices—a topic contentious enough that they debated whether to even show up and face the community at all.
They decided to go ahead. What followed was an AMA that became, almost entirely, about AI.
The questions came in waves. Fans wanted to know about the studio's use of artificial intelligence in development. They wanted assurances that workers hadn't been displaced. They wanted clarity on whether the company had fired developers and replaced them with algorithms to cut costs. The accusations were direct and specific: that Warhorse had chosen the cheaper path, that human workers had been sacrificed on the altar of efficiency.
The developers responded by repeating, again and again, that they employ actual people. Real humans. Not AI systems standing in for artists, programmers, and designers. The message had to be hammered home because the community wasn't taking it on faith. In an industry where layoffs have become routine and where AI tools are proliferating faster than anyone quite knows how to regulate them, players have learned to be skeptical. They've watched studios announce "optimization" and "streamlining" and seen what those words actually mean on the ground.
Warhorse's position was defensive by necessity. The studio acknowledged the sensitivity around the technology—that internal debate about whether to hold the AMA at all was itself an admission that they understood the minefield they were walking into. But they also seemed to believe they had nothing to hide, or at least nothing they couldn't explain away with repeated assurances about their hiring practices.
What made the moment significant wasn't the specific accusations or the studio's responses. It was the fact that this conversation had become unavoidable. A Reddit AMA for a major game release couldn't proceed as a normal promotional event. The technology question had metastasized into something that couldn't be ignored or deflected. Fans weren't asking about gameplay mechanics or story details or release dates. They were asking about labor, about whether the people who made the game still had jobs, about whether the industry was quietly automating away entire categories of creative work.
The incident sits at the intersection of two colliding forces: a gaming community increasingly attuned to how games get made and by whom, and an industry experimenting with tools that could fundamentally reshape that process. Warhorse Studios found itself caught between them, forced to defend practices that, in their view, were entirely reasonable but that the community had already decided to scrutinize with an intensity usually reserved for far more serious matters.
What happens next will likely depend on whether other studios face similar pressure, and whether they respond with the same defensive posture or try a different approach. The question of how AI fits into game development isn't going away. If anything, it's only going to get louder.
Citações Notáveis
It was a really hot topic in our offices whether to do this AMA— Warhorse Studios developers
The studio repeatedly stated it employs actual humans rather than replacing staff with AI— Warhorse Studios developers during AMA
A Conversa do Hearth Outra perspectiva sobre a história
Why did the developers even decide to hold the AMA if they knew AI was going to dominate the conversation?
Because not showing up would have been worse. Silence reads as guilt in these situations. They probably thought they could explain their position and move on. They underestimated how much the community had already made up its mind.
But they were telling the truth, weren't they? They do employ actual people.
Likely yes. But the truth isn't really what was being debated. The question underneath was whether the industry as a whole is using AI to justify layoffs and cost-cutting. Warhorse became a symbol for something bigger than their own hiring practices.
So the fans weren't really asking about Kingdom Come at all.
They were asking about Kingdom Come, but through the lens of a much larger anxiety. Every game studio is experimenting with AI tools right now. Players are trying to figure out what that means for the people who make games, and whether they should feel guilty buying a product made with those tools.
Is that a fair thing to worry about?
It's a real thing to worry about. Whether it's fair depends on what actually happened at Warhorse and what's happening across the industry. The AMA didn't really settle that question.