Id Software deepens MachineGames engine ties after cutting half its engineering staff

Marty Stratton and Hugo Martin held id Software's first briefing since July's layoffs. The cuts removed about half the studio, including most of the id Tech engine team. Stratton said the studio restructured deliberately to stay viable across game and tech development. Engine work now splits more closely between id Software and MachineGames than before.

Stratton frames the cuts as a deliberate restructuring across disciplines
About half of id Software's staff exited in the July layoffs, Stratton confirmed.
He split the studio's response into separate game development and technology development tracks.
"There was a very deliberate effort to make sure that we were incredibly viable coming out of that across everything we do." - Marty Stratton, id Software

MachineGames absorbs more id Tech engine work after the Xbox reset
Most of id Software's id Tech engine team was cut in the July layoffs.
That forced tighter engine collaboration with MachineGames, which also builds on id Tech.
Stratton said the shift began before the cuts, as part of an Xbox reset.
"We're working more closely with MachineGames than ever." - Marty Stratton, id Software

Studio points to Slaughter Mode as proof of retained capability
Slaughter Mode and its cinematic trailer were built entirely in-house, Stratton said.
Most studios would outsource that cinematic work to an outside agency, he added.
"There was noise around the studio and commentary about our capabilities." - Marty Stratton, id Software

Martin's historical parallel exposes unresolved uncertainty about future scope
Hugo Martin, a 26-year id veteran, compared the cuts to John Carmack's 2013 departure.
Carmack took his engine team to Meta then, a past precedent for technical upheaval.
Stratton gave no timeline for the next major project or a multiplayer mode.
"It's an evolution... It changes the way we work. But we continue on." - Hugo Martin, id Software
What this means
For Service Vendors: Pitch engine-maintenance and tools-engineering capacity to Microsoft first-party studios sharing proprietary tech.
For Investors & VC: Add engine-team retention and cross-studio engine dependency to diligence on proprietary-tech studios.
For Publishers & Developers: Budget dedicated engine-support headcount before greenlighting projects on a sister studio's proprietary engine.