Open Source GZDoom Community Splinters After Creator Inserts AI-Generated Code (arstechnica.com)
(Thursday October 16, 2025 @05:30PM (BeauHD)
from the fork-in-the-road dept.)
- Reference: 0179809744
- News link: https://games.slashdot.org/story/25/10/16/2041249/open-source-gzdoom-community-splinters-after-creator-inserts-ai-generated-code
- Source link: https://arstechnica.com/gaming/2025/10/civil-war-gzdoom-fan-developers-split-off-over-use-of-chatgpt-generated-code/
An anonymous reader quotes a report from Ars Technica:
> If you've even idly checked in on the robust world of Doom fan development in recent years, you've probably encountered one of the hundreds of gameplay mods, WAD files, or entire commercial games based on GZDoom. The open source Doom port -- which can trace its lineage back to the original launch of ZDoom back in 1998 -- adds modern graphics rendering, quality-of-life additions, and incredibly deep modding features to the original Doom source code that John Carmack released in 1997. Now, though, the community behind GZDoom is publicly fracturing, with a large contingent of developers uniting behind a new fork called UZDoom. The move is in apparent protest of the leadership of GZDoom creator and maintainer Cristoph Oelckers (aka Graf Zahl), who [1]recently admitted to inserting untested AI-generated code into the GZDoom codebase .
>
> "Due to some disagreements -- some recent; some tolerated for close to 2 decades -- with how collaboration should work, we've decided that the best course of action was to fork the project," developer Nash Muhandes [2]wrote on the DoomWorld forums Wednesday. "I don't want to see the GZDoom legacy die, as do most all of us, hence why I think the best thing to do is to continue development through a fork, while introducing a different development model that highly favors transparent collaboration between multiple people." [...] Zahl defended the use of AI-generated snippets for "boilerplate code" that isn't key to underlying game features. "I surely have my reservations about using AI for project specific code," he wrote, "but this here is just superficial checks of system configuration settings that can be found on various websites -- just with 10x the effort required."
>
> But others in the community were adamant that there's no place for AI tools in the workflow of an open source project like this. "If using code slop generated from ChatGPT or any other GenAI/AI chatbots is the future of this project, I'm sorry to say but I'm out," GitHub user Cacodemon345 [3]wrote , summarizing the feelings of many other developers. In a [4]GitHub bug report posted Tuesday, user the-phinet laid out the disagreements over AI-generated code alongside other alleged issues with Zahl's top-down approach to pushing out GZDoom updates.
[1] https://arstechnica.com/gaming/2025/10/civil-war-gzdoom-fan-developers-split-off-over-use-of-chatgpt-generated-code/
[2] https://www.doomworld.com/forum/topic/155567-uzdoom/
[3] https://github.com/ZDoom/gzdoom/commit/584af500736b0317e42824f39285ed3d954fc4e2#r167890520
[4] https://github.com/ZDoom/gzdoom/issues/3395
> If you've even idly checked in on the robust world of Doom fan development in recent years, you've probably encountered one of the hundreds of gameplay mods, WAD files, or entire commercial games based on GZDoom. The open source Doom port -- which can trace its lineage back to the original launch of ZDoom back in 1998 -- adds modern graphics rendering, quality-of-life additions, and incredibly deep modding features to the original Doom source code that John Carmack released in 1997. Now, though, the community behind GZDoom is publicly fracturing, with a large contingent of developers uniting behind a new fork called UZDoom. The move is in apparent protest of the leadership of GZDoom creator and maintainer Cristoph Oelckers (aka Graf Zahl), who [1]recently admitted to inserting untested AI-generated code into the GZDoom codebase .
>
> "Due to some disagreements -- some recent; some tolerated for close to 2 decades -- with how collaboration should work, we've decided that the best course of action was to fork the project," developer Nash Muhandes [2]wrote on the DoomWorld forums Wednesday. "I don't want to see the GZDoom legacy die, as do most all of us, hence why I think the best thing to do is to continue development through a fork, while introducing a different development model that highly favors transparent collaboration between multiple people." [...] Zahl defended the use of AI-generated snippets for "boilerplate code" that isn't key to underlying game features. "I surely have my reservations about using AI for project specific code," he wrote, "but this here is just superficial checks of system configuration settings that can be found on various websites -- just with 10x the effort required."
>
> But others in the community were adamant that there's no place for AI tools in the workflow of an open source project like this. "If using code slop generated from ChatGPT or any other GenAI/AI chatbots is the future of this project, I'm sorry to say but I'm out," GitHub user Cacodemon345 [3]wrote , summarizing the feelings of many other developers. In a [4]GitHub bug report posted Tuesday, user the-phinet laid out the disagreements over AI-generated code alongside other alleged issues with Zahl's top-down approach to pushing out GZDoom updates.
[1] https://arstechnica.com/gaming/2025/10/civil-war-gzdoom-fan-developers-split-off-over-use-of-chatgpt-generated-code/
[2] https://www.doomworld.com/forum/topic/155567-uzdoom/
[3] https://github.com/ZDoom/gzdoom/commit/584af500736b0317e42824f39285ed3d954fc4e2#r167890520
[4] https://github.com/ZDoom/gzdoom/issues/3395
I see a similar divide at work (Score:2)
by ffkom ( 3519199 )
The divide between rapidly brain-atrophied LLM abusers and old men yelling at clouds (because they want high-quality, hand-optimized software development back) seems all too familiar to me, and I don't see a resolution anytime soon. One might argue it should be possible to use LLMs just as yet another tool to help with some things, without being abused for other things. But it seems between vibe-coders and experienced programmers there is no significant middle ground to speak of.
Re: (Score:2)
Like it or hate it, approve of disapprove, if it (ever) works, it will be used.
Standing in the way of progress is a sure fire way to be run over by it.