Ultima IX: Ascension · PC · 1999 · Impact: Routinely cited as a franchise-ending release
A storyline bug made Ultima IX impossible to finish without cheating, saves corrupted, and it ran properly only on 3Dfx cards in the year 3Dfx collapsed. EA had set a ship-or-kill deadline for Thanksgiving 1999.
Ultima IX's failures were not really bugs so much as the visible symptoms of a development history that had been dismantled twice over. Partway through production, EA and Origin moved most of the Ultima IX team onto Ultima Online after its beta succeeded, effectively halting the game. When the team eventually returned, the work they had done was dated and many of the people who had done it were gone; two key designers departed for John Romero's Ion Storm, one of them after a personality conflict with Richard Garriott. Then EA imposed a ship-or-kill deadline for Thanksgiving 1999, and large portions of the game were cut or drastically shortened to hit it. What shipped was extraordinary in its brokenness. Saves corrupted; the game crashed while saving; it crashed to the desktop with no error at all; memory leaks degraded performance the longer it ran. A storyline bug made the adventure impossible to complete without cheating — the final entry in a fourteen-year series could not be finished. And the compatibility situation was almost comically unlucky: the game really only worked on 3Dfx hardware, apparently because there had been no time to test the less popular APIs, in the exact year 3Dfx's market position collapsed. The audience that could run Ultima IX properly was evaporating as it shipped. GameSpot named it 1999's Most Disappointing Game.
The decision that broke Ultima IX was made years before release and had nothing to do with programming. Ultima Online's beta was a success, and EA and Origin responded rationally by moving people to it — Ultima Online was the future, the money was there, and Ultima IX could wait. What that reasoning missed is that a game in development is not a file sitting on a server; it is a shared understanding held in the heads of the people building it, and it decays when they leave.
By the time the team reassembled, the work was technically dated and, worse, the institutional memory had dispersed. Key designers had gone to Ion Storm, one after clashing with Garriott directly. The people who returned inherited a codebase and a design whose reasoning had walked out the door. This is why the eventual bug list reads the way it does — corrupted saves, silent crashes, a storyline that cannot be completed — these are the signature of a project nobody fully understood any more, finished under duress.
Two failures stand out for what they say about the deadline. The first is the storyline bug that made the game impossible to complete without cheating. Ultima IX was the conclusion of a fourteen-year narrative, the entry the entire series had been building toward, and it shipped in a state where reaching the ending required stepping outside the game. No amount of schedule pressure makes that acceptable; it means the critical path was not tested end-to-end, which is the single test a story-driven RPG cannot skip.
The second is the graphics situation, which is where bad decisions met bad luck. There was no time to test the less popular APIs, so the game worked properly only on 3Dfx cards — a defensible gamble in 1997, when 3Dfx dominated. It shipped in 1999, the year 3Dfx's fortunes fell out from under it in one of the sharpest reversals in PC hardware history. The practical effect was that a large share of buyers physically could not run the game well. EA got its Thanksgiving release, and what it purchased for the deadline was a franchise finale that could neither be run by most of its audience nor finished by the ones who could.