The editorial argues idTech quietly became Bethesda's shared shooter engine, powering Wolfenstein, Indiana Jones and the Great Circle, and Redfall's hybrid stack. Losing the maintainers doesn't kill any shipped game but kills the compounding leverage that a small senior engine team produces — invoking Carmack's line that a great engine is a great tools problem.
The editorial frames this as the second time in three years Microsoft has cut engineers responsible for tech other Microsoft studios depend on, following the 2023 Tango Gameworks cut and the closure of Arkane Austin. The pattern shows internal tech groups and mid-size studios getting squeezed while flagship franchises are shielded from cuts.
Surfaced the GameFromScratch report, which cites ex-id engineers on social media confirming the core group behind the renderer, tooling, and platform layer — the team responsible for the Vulkan renderer and early mesh shader support — was gutted, not merely trimmed. The 602 points and 535 comments signal broad developer agreement that this was a substantive loss.
As part of the latest round of Xbox/Microsoft Gaming layoffs, the internal engine team at id Software — the people who actually maintain idTech — was gutted. Reporting from GameFromScratch and corroborating posts from ex-id engineers on social media indicate the cuts weren't a token trim: this was the core group responsible for the renderer, tooling, and platform layer that ships every Doom and every Wolfenstein.
id Software isn't dead. Bethesda's studios still exist on paper, and Doom: The Dark Ages already shipped earlier this year on the current idTech branch. But the group that would carry idTech to the next generation — the one that made the Vulkan renderer sing, that landed mesh shaders before most AAA engines had a plan for them, that maintained the notoriously fast content pipeline — is now scattered.
This is the second time in three years Microsoft has laid off engineers responsible for shipping technology that other Microsoft studios depend on, following the 2023 Tango Gameworks cut (later reversed via a sale to Krafton) and the closure of Arkane Austin. The pattern is consistent: internal tech and mid-size studios get squeezed while the marquee franchises are protected.
idTech is not just "id's engine." Over the last decade it quietly became Bethesda's shared shooter engine. MachineGames used it for the modern Wolfenstein games. It powered *Indiana Jones and the Great Circle* in 2024 — a MachineGames title with almost no id staff on it, riding entirely on the engine team's work. Arkane's *Redfall*, whatever you thought of it, was on a Void/idTech hybrid. Losing the maintainers doesn't kill any one shipped game; it kills the compounding.
Game engines are one of the few remaining places in software where a small, senior team produces disproportionate leverage. Carmack's original observation that "a great engine is a great tools problem" is exactly why gutting the team is worse than it looks on the org chart — the shipped binaries are fine, but the tribal knowledge about *why* the streaming system tolerates a 30GB texture budget on console, or *how* the BVH build got fast enough to enable hardware RT at 60fps in *The Dark Ages*, walks out the door with the people.
The community reaction on Hacker News (602 points at time of writing) leans heavily on one thread: this is Unreal's win by default. Every studio that was quietly hoping Bethesda would open-license idTech, or that MachineGames' next project would push the renderer further, now has to plan on Unreal 5 or an in-house engine. Given how much of the industry has already collapsed onto UE5's Nanite/Lumen defaults, another mid-size proprietary engine falling out of active development is a real reduction in technical diversity.
There's also the licensing angle. id has a long history — going back to the original Quake engine — of eventually open-sourcing older idTech versions under GPL. The current codebase (idTech 7/8) is proprietary and Microsoft-owned, and there is no version of this layoff that makes an open-source release *more* likely. If you were hoping to learn from a modern, shipping AAA renderer in the same way a generation of engine programmers learned from the Quake source drop, that door is closing, not opening.
If you build on a licensed engine — Unreal, Unity, Godot, or a proprietary internal one — the concrete lesson here is about engine team headcount as infrastructure. When leadership treats the engine group as overhead rather than as the substrate every product line depends on, you get exactly this: shipped games that look fine for one more cycle, and a technical trajectory that flatlines the cycle after. The signal to watch inside your own org is whether engine work is scoped to titles ("we need this for Game X") or to platform ("we need this for the next five years"). The first framing is how engine teams die.
For practitioners specifically:
- If you're a graphics/engine engineer at a large publisher: the market just got tighter on the supply side and looser on the demand side. ex-id engine folks are elite, they will land, and they will compete for the same handful of remaining engine roles at Epic, Valve, Rockstar, and Sony first-party. If you're one of them, network now. - If you're on a small studio evaluating engines in 2026: the practical universe just shrank a bit further toward UE5 and Godot. idTech was never a licensing option for you anyway, but the psychological reassurance that "proprietary mid-tier engines can still thrive" took a hit. - If you're an indie or modder on the Doom/Quake ecosystem: the modding community around GZDoom and the classic engines is independent of this and fine. The modern idTech modding scene, which was already thin, is effectively frozen.
There's a broader read for anyone who ships developer tooling internally at a large company: owning the tools that other teams depend on is a political liability, not a moat, when the org optimizes for headline revenue per employee. id's engine team shipped one of the best-performing renderers in the industry and it wasn't enough. If your internal platform team is justifying itself by "we save the product teams N engineer-years," get that number in front of finance now, not at the next reorg.
The near-term is predictable: id's next Doom or Quake will ship on whatever branch of idTech was frozen the week the team was cut, with a skeleton crew doing bug fixes and platform ports. The medium-term is where it gets interesting — does Microsoft eventually consolidate its shooter studios onto Unreal (the Halo Studios path), or does it try to keep idTech on life support with a rebuilt team? History says the second option almost never works: engine teams are rebuilt from scratch or not at all, because the specific humans who understood the specific renderer are the engine. Bet on Unreal.
Top 10 dev stories every morning at 8am UTC. AI-curated. Retro terminal HTML email.