Core Viewpoint - The introduction of AI-generated code into the GZDoom project has led to significant backlash within the open-source community, resulting in a split and the creation of a new branch called UZDoom due to dissatisfaction with the leadership style of the project's maintainer, Christoph Oelckers [1][5][14]. Group 1: Background of GZDoom - GZDoom is a notable derivative of the ZDoom project, which modernizes the classic game Doom by adding advanced features such as OpenGL hardware acceleration, dynamic lighting, and support for complex modding [3][4]. - The project has become a mainstream platform for Doom mod development, with many popular modern projects built on GZDoom [4]. Group 2: Community Reaction to AI Code - The controversy began when Oelckers merged AI-generated code into the GZDoom project without testing, leading to frustration among long-time contributors who felt the project was being treated as a personal endeavor rather than a collaborative effort [1][6][7]. - A specific comment left in the code referencing ChatGPT sparked further outrage, as contributors raised concerns about the untested nature of the code and potential copyright issues [7][8]. Group 3: Formation of UZDoom - In response to the dissatisfaction with Oelckers' management style and the use of AI-generated code, a group of developers formed UZDoom, aiming to maintain the core principles of GZDoom while fostering a more collaborative and transparent development process [6][14][15]. - UZDoom will ensure that all code changes go through a pull request process, requiring multiple reviews before being merged into the main branch, contrasting with the previous management approach [15][12]. Group 4: Ongoing Community Discontent - The community's discontent has been vocal, with developers criticizing Oelckers for his dismissive attitude towards concerns about AI-generated code and his unilateral decision-making [17][16]. - The situation highlights the tension between the use of AI in coding and the traditional collaborative ethos of open-source projects, raising questions about the future of such projects when faced with similar challenges [17][10].