By ByteBot
Microsoft fired roughly 95 engineers at id Software on July 7, 2026 — the same afternoon DOOM: The Dark Ages shipped its “Revelations” expansion — gutting the team behind the idTech engine and effectively ending 30 years of bespoke game engine development. Xbox CEO Asha Sharma called it “the most significant restructure in XBOX history,” eliminating 1,600 roles immediately with another 1,600 to follow across FY27. Scott Miller, the Apogee/3D Realms founder, confirmed that most if not all of id Software’s coders were gone and called them “literally the best of the best coders in the industry.” George Broussard, co-creator of Duke Nukem 3D, was blunter: “id Software is essentially dead.”
What idTech Was — and Why Developers Cared
The idTech engine lineage runs from John Carmack’s original 1992 Wolfenstein 3D code through idTech 8 in DOOM: The Dark Ages. PC Gamer ranked it among the most important game engines ever created. Its technical achievement was singular: exceptionally optimized rendering on constrained hardware. Doom Eternal ran at a locked 60fps on the Nintendo Switch — the kind of result that makes rendering engineers stop and take notes. That performance was not accidental; idTech 7 rewrote its entire rendering pipeline from scratch, including geometry, materials, and lighting, to push GPU efficiency beyond what any default engine configuration achieves.
However, what made idTech genuinely irreplaceable was not the code itself but the people who understood it at a systems level. Michael Maynard, a 20+ year id Software veteran, posted his departure on LinkedIn alongside dozens of other engineers. That institutional knowledge — how to tune a renderer for a specific console’s memory bandwidth, how to eliminate traversal stutter before it ships — does not transfer to a new engine. You hire it back at twice the cost, and you usually can’t.
The Corporate Logic — and Why Developers Reject It
Microsoft’s rationale is defensible on paper. After acquiring Bethesda and Activision Blizzard, Xbox found itself maintaining three separate FPS-era engines simultaneously: idTech for Doom and Quake, Slipspace for Halo, and IW8 for Call of Duty. Consolidating to Unreal Engine 5 reduces tooling overhead, standardizes pipelines across studios, and cuts the cost of maintaining proprietary engine teams. The same playbook is playing out across the industry — The Witcher 4, Cyberpunk 2, and the Halo “Campaign Evolved” remake are all moving to UE5.
The developer community on Hacker News (265 points, 266 comments) found this logic unconvincing. The sharpest counterargument: Microsoft should have open-sourced idTech rather than killing it. “idTech is an incredible bespoke engine in an era where Unreal and Unity slop flood the market,” one commenter wrote. Others suggested donating the engine to the Blender Foundation — a move that would have preserved the technology, earned goodwill, and potentially seeded a genuine UE5 competitor. Instead, the engine’s future appears to be internal documentation and a graceful unmaintained exit.
Related: Microsoft Frontier Company: What Developers Must Ask
The UE5 Problem This Accelerates
The idTech team’s departure is not just a studio story — it is a symptom of an industry trend that developers are already naming. “UE slop” is the shorthand for games built on Unreal Engine 5’s default Nanite geometry and Lumen lighting without the studio-specific customization that distinguishes one AAA game from another. Common indicators include traversal stutter in open-world environments, soft-shadowed foliage with a recognizable look, and physics behaviors that feel borrowed rather than authored. According to XDA Developers, when studios don’t have the resources or expertise to deviate from Epic’s defaults, the output converges into a recognizable sameness.
idTech games didn’t converge. Doom Eternal looked and felt like Doom Eternal because id’s engineers spent years making it that way. Whether future Doom titles built on UE5 retain that identity is an open question — but the track record of engine migrations is not encouraging. The Halo series traded Slipspace’s technical character for UE5’s genericism, and the community noticed.
What This Means for Developers Evaluating Game Studios
There is a pattern here worth naming directly. Microsoft has now acquired and substantially restructured Rare, Mojang, Bethesda, and Activision Blizzard. In most cases, the studios survived as brands while the technical cultures that defined them were reorganized away. The id Software layoffs on DLC launch day are a particularly stark version of this — the team shipped product and got fired the same afternoon.
For developers considering offers from large-tech-acquired game studios, this pattern is data. The engineering excellence that made a studio worth acquiring is frequently not what the acquirer values once the deal closes. Consolidation optimizes for cost and organizational efficiency, not for the specific expertise that made idTech render Doom at 60fps on a game console with 4GB of RAM.
Key Takeaways
- Microsoft fired approximately 95 engineers at id Software on July 7, 2026 — Scott Miller confirmed most or all coders are gone, and the idTech engine is effectively dead
- idTech was technically exceptional: Doom Eternal at 60fps on the Nintendo Switch was its defining benchmark, achieved through a completely rewritten rendering pipeline
- The open-source argument is compelling: releasing idTech could have preserved the technology and created a genuine UE5 competitor — Microsoft chose neither outcome
- The “UE slop” problem accelerates as more studios default to Unreal Engine 5 without the expertise to differentiate
- For developers evaluating game studio jobs post-acquisition, the pattern is clear: engineering cultures that made studios valuable are frequently the first casualty of consolidation
