Kingdom Come Deliverance 2 developer claims role replaced by AI
Developer claims AI replaced translation role on Kingdom Come Deliverance 2 as Warhorse Studios declines to comment

A developer who worked on Kingdom Come: Deliverance 2 has claimed his role was terminated and replaced with AI.
The claim was made in a Reddit post by Max Hejtmanek, a Czech-to-English translator whose identity was verified by subreddit moderators through his LinkedIn profile.
He stated that he was informed on March 27 2026, that his position was being made “obsolete” as part of a shift towards AI-driven translation processes.
According to Hejtmanek, the decision was communicated during a meeting where he was told the change aimed to “make the company more effective”.
He added, “This came as a huge shock to me, as though the discussion about using AI for translating had frequently come up in the past, something I was always strongly and vocally against, but never to the extent that it might actually cost me my job in the future.”
Hejtmanek said he had worked at Warhorse Studios for several years, contributing to Kingdom Come Deliverance 2, its downloadable content and marketing materials.
He also noted that internal discussions around AI had taken place previously, but did not indicate his role would be removed.
In a follow-up message, he urged readers not to target the studio or its staff, writing, “PLEASE don’t harass anyone from WHS or review bomb their games on Steam, that isn’t my intention at all. All I want is for people to be more informed about what’s going on in the games industry behind closed doors.”
Warhorse Studios responded in a statement, saying, “Warhorse Studios has always been a talent-driven studio, and we deeply value the people who shape our work. Out of respect for the privacy and dignity of both current and former colleagues, we will not discuss individual situations publicly.”


















COMMENTS
Comments are moderated and generally will be posted if they are on-topic and not abusive.
For more information, please see our Comments FAQ