The Quake Fan who built the map editor everybody uses
Discover the incredible 15-year journey of TrenchBroom, the Quake map editor that redefined mapping despite its creator never making a single map with it. This deep dive into its development, technical challenges, and community impact resonates with HN's appreciation for dedicated open-source development and niche technical excellence. It highlights how a passionate individual's pursuit to scratch a personal itch can revitalize an entire retro gaming scene.
The Lowdown
Kristian Duske, a Mac user in 2010, simply wanted to make Quake maps again. Unsatisfied with existing tools, he embarked on building his own, leading to the creation of TrenchBroom, an editor that has since become the de-facto standard for Quake mapping and a catalyst for the game's modern renaissance.
- Humble Beginnings: Started as a personal project to fill a gap in macOS-compatible Quake editors, initially written in Objective-C and C, later rewritten in C++ for cross-platform support.
- Community Cornerstone: TrenchBroom's 3D-centric workflow and features like linked groups have empowered mappers to create stunning, complex levels, influencing modern retro shooters and integrating with tools like Godot.
- The Irony of Creation: Duske, despite building the most popular editor, has never actually completed a map using TrenchBroom himself.
- Technical Trials: The project has seen multiple rewrites, a significant migration from wxWidgets to Qt, and battles with complex algorithms like CSG subtraction, which proved 'untrackable' for ideal output.
- Maintaining Momentum: Duske balances the project with a full-time job and family, driven by seeing the community's creativity. He has recently leveraged AI tools to improve the codebase and build system, making maintenance more manageable.
- Vision & Openness: Guided by principles of simplicity and user-friendliness, Duske emphasizes making the tool accessible and enjoyable. While primarily focused on Quake, its open-source nature allows others to adapt it for different engines and needs.
Duske's unwavering dedication, spanning over a decade, showcases the power of a developer's personal drive to create a tool that not only solves their own problem but also profoundly impacts and energizes a passionate community.
The Gossip
TrenchBroom's Terrific Talent
The overwhelming sentiment among commenters is effusive praise for TrenchBroom. Many consider it among the best software they've ever used, citing its superior workflow compared to older editors like Valve's Hammer. Users highlight its versatility, noting its use for blocking out levels in modern game development, integrating with Godot via `func_godot`, and even for creating maps in niche projects like a 13kb Quake demake.
Brush-based Battles: Additive vs. Subtractive
A notable discussion point revolves around the core design philosophy of map editors, specifically the additive brush-based approach of TrenchBroom versus the subtractive methods found in editors like the original Unreal Editor. Some argue that creating every room with multiple additive brushes is less efficient for enclosed spaces, preferring the direct room creation of subtractive models. Others defend the brush-based approach, acknowledging its ties to the Quake engine's capabilities, while also noting that engine limitations often dictate editor design. The conversation also touches on the lineage of editors like Hammer and its successors.
Quake's Continuing Creativity
Commenters celebrate the enduring vitality of the Quake mapping community, often crediting TrenchBroom with contributing to its resurgence. They point to impressive modern map packs and mods like 'Arcane Dimensions' and the 'Brutalist Jams' as prime examples of how the editor enables extraordinary creativity within a decades-old game engine. The discussion underscores the passionate and active nature of retro gaming communities.
Qt's Consistent Contribution
One comment specifically echoes the author's positive experience with Qt, the UI framework TrenchBroom migrated to. The commenter notes Qt's reliability and its ability to 'just chug along,' allowing developers to focus on their primary application logic rather than wrestling with UI framework complexities or platform-specific workarounds. This highlights the value of robust, cross-platform UI toolkits for long-term hobby projects.