Gaming
Game Developers Started Taking Their Tools Back This Week
The DayZ creator Dean Hall released the source code for BRUTAL, his studio's C# game development framework, and used the moment to argue that developers have handed too much control to the engine companies their games depend on. The release is free even for commercial games, and it already powers RocketWerkz's Kitten Space Agency and the Waylith engine that RimWorld is moving to. In the same week, the decompilation tracker decomp.dev switched off its public index and leaderboard after AI assisted forks started racing human projects to release half finished PC ports, and 1666 Amsterdam developer Panache Digital confirmed at a preview event that AI generated assets found in its prologue have been scrubbed from the final game. Three different stories, one shared current. The people who make games are taking their tools, their credit, and their craft back into their own hands.
Hall's post on Reddit's game development community, published October 15, pulled about 4,000 points overnight and set the week's tone. Developers, he wrote, have surrendered an unprecedented amount of control over their work to companies whose interests often point a different way than their own. Epic took the direct hit. Hall recalled asking Tim Sweeney at GDC 2025 about performance, stability and accountability to developers, and getting an answer about technology demos and social media showcases. Unity drew fire for its business decisions and account suspensions tied to a mandatory security change. Days earlier Epic had announced a rebuilt Epic Games Launcher that it proudly described as vibe coded, opening with the line that programming is hard so it vibe coded a new launcher instead. Hall's answer to all of it is BRUTAL itself. The framework is free for commercial games, with royalties and revenue share both set to zero, asking only for a copyright notice in the credits, the Brutal logo on startup and a notice in the project files. BRUTAL is a framework rather than a full engine, both Unity and Unreal remain the right choice for many projects, and he frames it as an option rather than a boycott. His line that carries the week is the simplest one. You are only as independent as your tools are.
The decompilation scene lived the same lesson from the other side. Decomp.dev, the tracker launched in 2024 that gamified the painstaking work of rebuilding game source code from binaries, has disabled its public index and closed new submissions. Administrator Encounter put it plainly. The newest models follow complex directions, cross reference debug symbols and write natural code with enough guidance, faster and cheaper than before. What broke the community was what people did with that power. Bad actors forked open projects to finish them with AI against the original teams' wishes, then raced to release half finished PC ports while the years of foundational work stayed credited to the hobbyists who did it. The progress percentages that once celebrated real human effort became, in Encounter's words, a hollow numbers game for people who just want to burn tokens to make number go up. The site stays online, and existing projects keep their pages and historical data. The public leaderboard is gone and new projects cannot be added. AI can expedite decompilation in a significant way with the right guidance and code reviews. The community around it needs new rules for credit, and the old scoreboard was getting in the way.
Panache Digital faced the same question inside its own pipeline. Players spotted visual oddities in the playable prologue for 1666 Amsterdam earlier this year, in game paintings and marketing images that carried the fingerprints of generative AI, and the studio apologized, promising human made replacements. At a recent preview event in Amsterdam, Patrice Desilets gave the fuller account. The small team had used AI to generate rapid visual variations during early development, grew used to seeing the output, and let some assets slip through with too little retouching. Since then the pipeline has been tightened, the AI derived elements have been removed from the final build, and the Early Access and full release will ship with human made art. Desilets was candid that the studio still uses AI tools in development, describing their presence as dwindling, and framed the correction as a pipeline failure. Panache is drawing a clear line between using AI as a sketching tool in private and shipping AI generated work to players, and it is letting its dozen plus artists have the final word.
Put the three stories side by side and the pattern glows. A veteran developer open sources his framework so studios can own their foundations. A preservation community retires its scoreboard so credit flows to the people who earned it. A studio scrubs its shipping game so players get human craft. None of them are rejecting the new tools. Hall still calls the big engines the right choice for many projects, Encounter still says AI can help tremendously when used correctly, and Panache still sketches with AI behind closed doors. What they share is a refusal to let the tools own them. For the player the payoff is concrete. Games built on foundations their makers control, ports credited to the hands that did the work, and art you can trust came from an artist. That is what independence tastes like from the other side of the screen.
Quick answers
What is this story about?
The DayZ creator Dean Hall released the source code for BRUTAL, his studio's C# game development framework, and used the moment to argue that developers have handed too much control to the engine companies their games depend on. The release is free even for commercial games, and it already powers RocketWerkz's Kitten Space Agency and the Waylith engine that RimWorld is moving to. In the same week, the decompilation tracker decomp.dev switched off its public index and leaderboard after AI assisted forks started racing human projects to release half finished PC ports, and 1666 Amsterdam developer Panache Digital confirmed at a preview event that AI generated assets found in its prologue have been scrubbed from the final game. Three different stories, one shared current. The people who make games are taking their tools, their credit, and their craft back into their own hands.
Why does this story matter?
Put the three stories side by side and the pattern glows. A veteran developer open sources his framework so studios can own their foundations. A preservation community retires its scoreboard so credit flows to the people who earned it. A studio scrubs its shipping game so players get human craft. None of them are rejecting the new tools. Hall still calls the big engines the right choice for many projects, Encounter still says AI can help tremendously when used correctly, and Panache still sketches with AI behind closed doors. What they share is a refusal to let the tools own them. For the player the payoff is concrete. Games built on foundations their makers control, ports credited to the hands that did the work, and art you can trust came from an artist. That is what independence tastes like from the other side of the screen.
Sources
New to crypto? Read the crypto glossary, browse frequent questions, read our story, or explore the story archive.