In a significant move poised to influence the landscape of game development, RocketWerkz, the studio behind titles such as Kitten Space Agency and Icarus, and game platform operator Ahwoo – both established by the renowned DayZ creator Dean Hall – have jointly announced the open-source release of their proprietary game development framework, "BRUTAL." This C#-based framework offers a compelling alternative to established third-party game engines like Unity, Unreal Engine, and even the increasingly popular open-source contender, Godot, signaling a potential shift towards greater developer independence and custom tooling.
The announcement comes at a pivotal moment for the video game industry, which has recently grappled with a series of high-profile controversies surrounding major engine providers. These incidents have sparked widespread concern among developers regarding the stability, longevity, and economic viability of their chosen technology stacks. BRUTAL, combining the robust capabilities of C# and .NET with high-performance C++ libraries and direct low-level graphics access, is designed to serve as a foundational layer. It empowers developers to construct and maintain their own bespoke development tools and, ultimately, their unique game engines from the ground up, moving away from the "one-size-fits-all" approach of commercial engines.
The Genesis of BRUTAL: Dean Hall’s Vision for Independence
Dean Hall, a veteran figure known for his pioneering work on DayZ, has long been a vocal proponent of developer autonomy and a critic of over-reliance on external tools. His philosophy, deeply ingrained in the ethos of both RocketWerkz and Ahwoo, stems from a belief that true creative freedom and long-term project stability are best achieved when developers control their core technology. This conviction led to the internal development of BRUTAL, initially conceived as a solution for RocketWerkz’s own ambitious projects, including Kitten Space Agency.
Hall’s journey in the industry has been marked by a relentless pursuit of efficient and robust development practices. After the monumental success of DayZ, which began as a mod for ARMA 2, he founded RocketWerkz in New Zealand. The studio quickly became known for its innovative approach to survival games and its technical prowess. Ahwoo, launched subsequently, aimed to provide a more developer-friendly platform for game distribution and interaction. The creation of BRUTAL is a natural evolution of this ethos, born from a desire to sidestep the limitations and potential pitfalls associated with relying solely on third-party commercial engines.
A Response to Industry Shifts: The Call for Alternative Tech Stacks
The timing of BRUTAL’s open-source release is no coincidence, arriving amidst a period of significant turbulence and introspection within the game development community. The year leading up to this announcement witnessed several events that severely tested developer trust in established engine providers, fostering an environment ripe for alternatives.
Foremost among these was the infamous Unity Runtime Fee debacle. In September 2023, Unity Technologies announced a new "runtime fee" policy that would charge developers per game installation after certain revenue and installation thresholds were met. The announcement, perceived by many as an abrupt and retroactive change to terms of service, ignited a furious backlash across the industry. Developers expressed outrage over the lack of transparency, the potential for unforeseen financial burdens, and the existential threat it posed to smaller studios and free-to-play titles. While Unity eventually walked back many of the most controversial aspects of the policy, the incident left a lasting scar on its relationship with a significant portion of its user base. Thousands of developers publicly voiced their distrust, with many actively exploring migrations to alternative engines like Godot or even contemplating custom solutions.
Concurrently, Epic Games, the proprietor of Unreal Engine, also introduced changes that caused unease. The company’s announcement regarding the deprecation of Unreal’s visual scripting system, Blueprints, in favor of more C++ centric development paths for future iterations like Unreal Engine 6, raised concerns for developers heavily invested in Blueprint-driven workflows. While C++ has always been central to Unreal, the shift implied a higher barrier to entry for those less comfortable with traditional coding, potentially disrupting established development pipelines and requiring significant re-skilling or refactoring efforts.
These incidents collectively amplified a long-simmering desire among developers for greater control over their technological destinies. The prospect of an open-source framework, free from the whims of corporate policy changes or unexpected technical shifts, became significantly more attractive. BRUTAL steps into this vacuum, offering a path towards self-sufficiency for those willing to embrace a more hands-on approach to engine development.
Technical Deep Dive into BRUTAL: Architecture and Philosophy
At its core, BRUTAL is not a ready-to-use game engine but a robust programming framework. This distinction is crucial for understanding its intended use and target audience. Unlike Unity or Unreal, which provide comprehensive integrated development environments (IDEs) with visual editors, asset pipelines, and pre-built functionalities, BRUTAL offers the fundamental building blocks.
The framework leverages the strengths of C# and the .NET ecosystem for its high-level logic, offering modern language features, strong type safety, and a vast library of tools. This is complemented by the integration of C++ libraries, providing the critical performance and low-level control often required for demanding game operations such as rendering, physics, and memory management. Crucially, BRUTAL provides direct access to low-level graphics APIs, implying support for modern rendering interfaces like Vulkan or DirectX, enabling developers to optimize graphics pipelines for specific hardware and achieve maximum performance.
This architectural choice reflects a philosophy of empowering developers with granular control. Instead of abstracting away the complexities of the underlying hardware and software, BRUTAL provides the tools to engage with them directly. This approach is particularly appealing to studios that require highly optimized performance, unique rendering capabilities, or complete customization of their engine’s behavior – needs that can be challenging to meet within the confines of a pre-packaged commercial engine.
The RimWorld Precedent: A Powerful Case Study for BRUTAL’s Efficacy
While RocketWerkz has been actively utilizing BRUTAL in the development of Kitten Space Agency, perhaps the most compelling external validation for the framework’s capabilities comes from Ludeon Studios, the creators of the critically acclaimed colony simulation game, RimWorld. In a significant announcement made last week, Ludeon Studios revealed that they had successfully ported RimWorld off Unity and onto a new, custom game engine dubbed "Waylith," which is powered by BRUTAL.
The decision to migrate RimWorld, a game with a massive codebase and intricate systems built over many years on Unity, serves as a powerful testament to BRUTAL’s maturity and flexibility. Ludeon Studios cited tangible benefits from this extensive undertaking, reporting that the new Waylith engine offers players "better performance" and "a faster start-up time" compared to previous Unity-based versions. This real-world application demonstrates that BRUTAL is not merely a theoretical exercise but a practical solution capable of underpinning complex, large-scale commercial titles. The successful porting of RimWorld provides concrete evidence that a framework-based approach can yield significant technical improvements, directly benefiting the end-user experience. It also underscores the growing willingness of established studios to invest in custom solutions to overcome perceived limitations or risks associated with their existing tech stacks.

Open Source, Not Open Season: Licensing and Attribution
BRUTAL is released under an open-source license, making it freely available for use in commercial games without any royalty requirements. This generous licensing model is a direct contrast to the revenue-sharing or subscription models of major commercial engines, offering significant financial advantages, particularly for independent developers and startups operating on tight budgets.
However, the open-source license does come with specific conditions. Developers utilizing BRUTAL are required to provide attribution and display a designated logo before gameplay when players load their game. This standard practice in the open-source community ensures proper credit to the original creators while allowing for widespread adoption and modification. This balance of freedom and acknowledgment aligns with the collaborative spirit of open-source development, encouraging contributions and community engagement while protecting the intellectual property of the framework’s originators.
The Role of AI in Modern Development: Supercharging C# and Vulkan
One of the most intriguing aspects of BRUTAL’s development and its potential for future users lies in the innovative application of Large Language Models (LLMs). In 2025, Dean Hall and Kerbal Space Program creator Felipe Falanghe shared insights with Game Developer, explaining how LLMs significantly streamlined their work with BRUTAL. They found that AI tools proved invaluable for querying C# libraries and Vulkan documentation, both of which are characterized by their "highly structured, with very clear syntax."
Hall elaborated on this synergy: "An LLM is essentially tokenizing language, then putting masses of vectors around that to build linkages between those tokens. What could be better than a highly-structured, in fact brutally structured language?" This perspective highlights how LLMs, when applied to well-defined and rigorously documented programming languages and APIs, can act as powerful assistants, accelerating the learning curve and problem-solving process. They can quickly retrieve relevant information, explain complex concepts, and even suggest code snippets, reducing the time developers spend sifting through extensive documentation.
The pair emphasized that this process is distinct from "vibe-coding," a more speculative approach where AI automatically generates entire blocks of code based on vague user prompts. Instead, their use of LLMs with BRUTAL focused on leveraging AI for precise information retrieval and contextual understanding within structured programming environments, augmenting human development rather than replacing it. This nuanced application of AI suggests a future where intelligent tools enhance developer productivity in complex frameworks without compromising on control or understanding.
The Drive for Developer Independence: A Broader Industry Trend
Dean Hall’s steadfast belief that "You are only as independent as your tools are" resonates deeply within an industry increasingly wary of external dependencies. His past criticisms of Unity, including an incident in 2025 where he publicly called out the company for allegedly threatening RocketWerkz’s license over what he claimed were false accusations, underscore his commitment to this principle. While he acknowledges that "not every developer should have to make their own game engine," he firmly believes that "every developer should have the option to do so."
This sentiment reflects a broader trend among developers seeking greater autonomy. The shift is evident in other notable migrations, such as Mega Crit, the studio behind the highly successful Slay the Spire. Mega Crit famously switched from Unity to Godot during development, reportedly losing minimal development time in the process. Such examples illustrate a growing willingness to embrace open-source or custom solutions, even mid-project, when concerns about a primary engine provider become too significant. The cost savings, transparency, and control offered by open-source alternatives are proving increasingly attractive, particularly for studios that prioritize long-term stability and creative freedom over the immediate convenience of a fully integrated commercial solution.
Challenges and Considerations for Adoption: Not a Simple Switch
While BRUTAL presents an exciting opportunity, it is crucial for prospective adopters to understand that integrating it into their workflow is not akin to picking up a user-friendly open-source engine like Godot. Godot, like Unity and Unreal, aims to be a complete engine, offering an accessible editor, a rich feature set, and extensive community support for common game development tasks.
BRUTAL, by contrast, is a programming framework. This means it provides the underlying structure and libraries, but developers are responsible for building their own tools, editors, and higher-level functionalities on top of it. This approach demands a much deeper understanding of programming languages, particularly C#, and a willingness to engage with the "nuts and bolts" of engine development. It represents a more challenging feat, requiring significant technical expertise, a dedicated engineering team, and a long-term commitment to maintaining a custom tech stack. For many smaller teams or individual developers, this steep learning curve and the increased development overhead might be prohibitive.
Dean Hall himself acknowledges this distinction. In a conversation with Game Developer last year, he expressed a preference for other developers creating their "simpler" frameworks following a similar approach, rather than attempting to transform BRUTAL into an industry-standard, all-encompassing engine. He clarified that "BRUTAL was made to deliver a very specific, kind of hard-to-make game where you need to sit down and ask a whole bunch of questions [about how it works]." This implies that BRUTAL is best suited for projects with unique technical requirements, extreme performance demands, or developers who fundamentally desire complete control over every aspect of their engine. This targeted approach ensures that while some developers will undoubtedly embrace the challenge and the freedom BRUTAL offers, others will understandably find the task daunting and opt for more conventional engine solutions.
Broader Industry Implications: A Future of Diverse Tooling
The open-source release of BRUTAL, coupled with the ongoing shifts in the game engine market, points towards a future characterized by a more diverse and fragmented tooling landscape. While Unity and Unreal Engine will undoubtedly continue to dominate a significant portion of the market, particularly for studios seeking out-of-the-box solutions and extensive marketplaces, the rise of frameworks like BRUTAL and the increasing adoption of open-source engines like Godot suggest a growing appetite for alternatives.
This diversification could foster greater innovation, as developers are no longer constrained by the specific design philosophies or technical limitations of a single engine. It could also lead to healthier competition among tool providers, potentially driving better terms, more stable policies, and improved features across the board. For the industry as a whole, the movement towards custom frameworks signifies a maturation, where developers are increasingly empowered to tailor their tools to their creative visions, rather than adapting their visions to pre-existing tools.
The long-term impact of BRUTAL’s release will depend on its community adoption, the quality of its ongoing development, and the willingness of studios to invest in custom engine solutions. However, by providing a robust, C#-based foundation rooted in a philosophy of independence, Dean Hall and his teams have certainly offered a compelling new path for those daring enough to forge their own tools in the dynamic world of game development.
