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.

Many developers leave GZDoom due to leader conflicts and fork it into UZDoom

By -
Last updated: 17 Oct 2025 at 11:15 am UTC

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.
20 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.
29 comments Subscribe
Page: 2/2
  Go to:

Liam Dawe 3 days ago
User Avatar
not involved into gzdoom in any way
Well, just maybe all the people who are involved and did the nuclear option of forking an established thing know a bit more than you do?
Chee_Koala 3 days ago
  • New User
I get that you think it's a shame, but at least in FOSS communities, instead of a bunch of firings and a big nose deciding they're gonna 'stay the course' anyway, you get a new fork with new rules/guidelines and the public can decide for themselves what path they like more.

Seeing it in context of how capitalist enterprises normally handle these situations, it no longer feels like a shame to me, it feels like a triumph. FOSStastic!
R Daneel Olivaw 3 days ago
User Avatar
This whole thing reminds me of the openoffice/libreoffice split all those years ago. I remember at the time going "whoa, this is a huge deal" and not being sure how it would all work out.

Now, a bunch of years later, libreoffice is THE defacto gold standard, it's used and liked (mostly lol) everywhere, and I haven't even heard of openoffice in an eternity. I did just now look it up, but it looks like abandonware. Apparently Apache runs it? But it hasn't been updated in two years.
Klaas 3 days ago
I've seen some of the drama over the years (well decades), and that unfinished sentence seems like a fitting end to the latest events. I'm sure that the other developers' reactions can only look harsh from the outside.

I want to highlight Kinsie's comment on GitHub as I think it is very accurate:
The recent progress under the more collaborative, team-based practices of late has been magnificent. It'd be a pity to see that get undermined.


Last edited by Klaas on 16 Oct 2025 at 4:42 pm UTC
Creak 3 days ago
  • Supporter Plus
Love the UZDoom repo desription 🤣

UZDoom is a feature centric port for all Doom engine games, based on ZDoom, adding an advanced renderer, powerful scripting capabilities, and forked under a
Technopeasant 2 days ago
Is anyone forking Raze?
DrMcCoy a day ago
I'm waiting for DrMcCoy to comment on this and see what he thinks. ^^

Yeah, sorry, I'm a bit late :P. Life has been busy recently, and I haven't followed GoL that closely lately

As for Graf Zahl... Never had any contact with him, so I can't really comment.

(Only that Graf Zahl is the official German name for the Sesame Street character Count von Count. Do with that information what you will :P)

Except that I also really hate the recent push by people to cram "AI" into everything. Especially for code, it's pretty awful. At work, we're constantly prodded to try all the terrible Copilot stuff, because my company is paying for those licenses and the higher-ups are getting hard hallucinating about all the bonuses they could get with the productivity increases. Increases that are of course completely made-up, as what Copilot spits out is without fail bullshit.

You can even see it in the code he commited, to check for "dark mode" on Linux... which, first of all, merely checks if the theme has the word "dark" in it, which is laughable in its own right, and then doesn't even compile. If that account were satirical fiction, everyone would call it out for being too on the nose.
14 4 hours ago
User Avatar
  • Supporter Plus
What is the only universal definition of a leader? Someone who has followers.

A bad leader is better than chaos, so I hope the vision of "collaboration" this group has understands how to make decisions when not 100% of people involved agree with everything all the time. And, pure democratic (popular vote) decisions are unfair to minority opinions. All these things need to be handled somehow. Why does someone stick around when their ideas aren't included? It's because they know they were listened to and considered. It's because there was enough discussion that they can understand the reasoning behind the decision they didn't choose. It's because they have hope future ideas will be treated with the same consideration. You can't always attach that feeling to a whole group of collaborators. In my anecdotal experience, you can get that feeling from a final decision-maker leader or from a small group, but not really from a large (more than 5 'core' people) group.
tuubi 4 hours ago
User Avatar
A bad leader is better than chaos
These are the only two options? emoji

And, pure democratic (popular vote) decisions are unfair to minority opinions.
Whereas a bad leader is fair to no one.

An open source project needs competent leadership to flourish, but that leadership needs to be trusted and respected by the developers. In an open source (volunteer) project, as in a representative democracy, it's up to the leaders to keep that trust by serving that community and proving their worth for the project. This one didn't. We've all heard of "benevolent dictators", but in that phrase only the "dictator" part is optional.
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