What does a franchise owe the genre it made famous? StarCraft's 2026 answer appears to be: very little. The series that taught a generation to count minerals and micro their marines returns in 2030 as an open-world shooter, directed by a veteran of the Far Cry games. The argument arrived on schedule, and everyone shouting in it shares one assumption, that a genre is a kind of promise. It never was. Genre began as a set of constraints a few young programmers found convenient, then lucrative, then permanent mostly by accident. Which makes the useful text for this moment the story of the people who bolted the first-person shooter together out of borrowed hardware and stubbornness, in a rented lake house in Shreveport, on a schedule nobody sane would have signed.
Coverage of the announcement has mostly been a loyalty hearing. Does dropping real-time strategy betray what made StarCraft matter? Prosecution and defense both treat the genre as a fixed object with a birth certificate somewhere on file. Almost nobody goes back to ask who drew the category's boundaries, and under what conditions. The answer is unglamorous. Tiny teams solved technical problems fast, named the result afterward, and then discovered the name had become a market with expectations attached. Put that on the table and a strategy series waking up as a shooter looks like the industry doing what it has always done, now with a bigger budget and a press release.
David Kushner's Masters of Doom follows John Carmack and John Romero from bedroom experiments to the founding of id Software, and it keeps both men in proportion. Carmack is the engineer interested in what the hardware could be made to do and almost nothing else. Romero is the designer and showman, the one who grasped that a game is also a performance, and that someone has to stand up and sell the noise. The partnership worked because those instincts were incompatible in a productive way. Kushner writes 1990s development at floor level, in stolen hours on machines that belonged to somebody else.
The technical detail is specific enough to follow: Carmack's code could push a view through space faster than anyone else's, so design followed the math. The first-person shooter was a consequence that acquired a name later. Doom and Quake then set the technical and creative terms that later studios had to answer, whether they liked those terms or not. It is also a business story, and a slightly alarming one. A handful of people scaled into an industry force in a few years without acquiring any of the management habits that kind of growth usually demands.
Shareware distribution turned a small operation into a revenue machine while the founders were still arguing about level design in the next room. The same appetite that produced the work eventually pulled them apart, which Kushner narrates with sympathy and without pretending anyone behaved well throughout. My friction is with the shape. Kushner frames id as a two-man duel, and that framing buys momentum at a price. Tom Hall and Adrian Carmack get comparatively thin treatment, along with the people who shipped and supported the products, which flatters the myth that genres are invented by geniuses instead of assembled by teams under pressure.
The crunch reads as romance more often than as damage. With two more decades of evidence about what those schedules do to people, the chapters about sleeping at the office would land colder now. The central argument survives the complaint. Conventions that fans now defend as sacred were improvised by exhausted twenty-somethings who would have thrown them out the following month if the code had suggested something better. Carry that into any conversation about franchise reinvention and the conversation changes temperature.
So what does a franchise owe the genre it made famous? Probably nothing, and that is the uncomfortable part. The categories we defend were working conditions before anyone thought to call them traditions, and the paperwork came last. Kushner's book is worth your evening if you want that process in close-up, deadlines and estrangement intact. It will not settle whether an open-world StarCraft is a good idea. It will make the question feel like the thing this industry has been doing, loudly, since two Johns figured out how to move a wall.