Patreon Logo Support us on Patreon to keep GamingOnLinux alive. This ensures all of our main content remains free for everyone. Just good, fresh content! Alternatively, you can donate through PayPal Logo PayPal. You can also buy games using our partner links for GOG and Humble Store.
We use affiliate links to earn us some pennies. Learn more.

Drama in open source land, as a major conflict has caused many developers to leave GZDoom behind to fork it into UZDoom. It seems like going forward most people will end up using UZDoom.

What actually happened? In the official Discord server that covers ZDoom and related projects, an announcement was put up by a moderator noting "Due to a conflict between GZDoom's lead developer/maintainer Graf Zahl, a lot of other developers decided to leave GZDoom and work on a new fork of the engine now known as UZDoom".

They continued to note that "UZDoom is a direct continuation of GZDoom and will inherit all of its features (and add more eventually)" but the point is that it will have "a more stable development structure with healthy collaboration and less power given to individual 'project leads'".


Pictured - Doom Infinite

Looking a bit further into it, a bug report on the GZDoom GitHub page titled "Project management" was opened that gave a little more detail noting issues with the lead of GZDoom pushing untested code, using an LLM to write code and hiding "not insignificant changes in commits, which has people worried that you'll randomly rip out features that they rely on". In reply, the project lead simply said "Feel free to fork the project under a" (yes, that really all they said).

A later comment before the bug report was locked points out the specific change in GZDoom that was made with ChatGPT.

Really a shame when such incredible projects go through issues like this. Hopefully the ZDoom / UZDoom will come out healthier and stronger from this with a more community orientated approach to the code.

Article taken from GamingOnLinux.com.
5 Likes
About the author -
author picture
I am the owner of GamingOnLinux. After discovering Linux back in the days of Mandrake in 2003, I constantly checked on the progress of Linux until Ubuntu appeared on the scene and it helped me to really love it. You can reach me easily by emailing GamingOnLinux directly.
See more from me
All posts need to follow our rules. Please hit the Report Flag icon on any post that breaks the rules or contains illegal / harmful content. Readers can also email us for any issues or concerns.
10 comments Subscribe

eev 3 hours ago
Feel free to fork the project under a

Imagine being so mad you can't even tell them to fork it correctly.
Doktor-Mandrake 3 hours ago
Hopefully retail projects like selaco will move over to this new fork

Really disappointing reading this, gzdoom deserved better
Leahi84 3 hours ago
Graf has a history of being a major dick, and hyper controlling. Though I'm shocked he'd stoop so low as to use llms to write his code. I remember his massive tantrum over the glitched mod Lilith. I hope Rachael abandons him for this project. She's been really great and I'd hate to see her go down with him. I also hope game devs that use gzdoom will switch to this and not give Graf anymore attention.


Last edited by Leahi84 on 15 Oct 2025 at 12:34 pm UTC
Doktor-Mandrake 2 hours ago
Using llms and then when people raise concerns he just says "Feel free to fork the project under a"

Couldn't even be bothered to give a proper reply, shows how much he cares I suppose.

For me I'm just shocked but suppose I never knew the lead of this engine was such a massive knob-handle
R Daneel Olivaw 2 hours ago
User Avatar
This is wonderful news! I'm glad the team decided to make positive moves and get away from the ai-garbage-slop and a dickhead team lead.

The regular zdoom page still tells people to go download gzdoom, but I'm hopeful over time they'll change that recommendation or at least add uzdoom.
Hopefully the new fork will have a sane build script now; because currently the thing that builds GZDoom is an odd concoction of shell scripts & CMake recipes.
pb 2 hours ago
User Avatar
This whole AI conundrum is not going to end well for humanity. emoji
1xok 1 hour ago
User Avatar
  • Supporter Plus
Off Topic: Recently, Selaco caused my Steam Deck to crash so badly that it simply shut down and then starts with the Boot Loader menu.

Of course, I initially thought it was a hardware defect, and I still do. On the other hand, I have used the Deck frequently with other games since then and have not experienced any further issues. Has anyone experienced this issue with Selanco?
scaine 1 hour ago
User Avatar
  • Contributing Editor
  • Mega Supporter
I wrote a piece on my blog about the (lack of) ethics in AI, but this piece about coding standards stands out in the context of Graf espousing AI code generation. Maybe it'll improve... but right now, all it does is slow you down.

https://metr.org/blog/2025-07-10-early-2025-ai-experienced-os-dev-study/ [External Link]
emphy 6 minutes ago
I wrote a piece on my blog about the (lack of) ethics in AI, but this piece about coding standards stands out in the context of Graf espousing AI code generation. Maybe it'll improve... but right now, all it does is slow you down.

[External Link]

That was early 2025. By now, ai should have improved the slowdown to 25%.
While you're here, please consider supporting GamingOnLinux on:

Reward Tiers: Patreon Logo Patreon. Plain Donations: PayPal Logo PayPal.

This ensures all of our main content remains totally free for everyone! Patreon supporters can also remove all adverts and sponsors! Supporting us helps bring good, fresh content. Without your continued support, we simply could not continue!

You can find even more ways to support us on this dedicated page any time. If you already are, thank you!
Login / Register