Why Troika Games Were So Buggy

tim-cain troika-games game-development bugs rpg arcanum vampire-bloodlines temple-of-elemental-evil postmortem

Abstract

Problem: Troika Games shipped three RPGs — Arcanum, Temple of Elemental Evil, and Vampire: The Masquerade – Bloodlines — all notorious for being extremely buggy. Why did this keep happening?

Approach: Tim Cain, Troika co-founder, explains the compounding factors from his firsthand experience leading the studio through all three titles.

Findings: The bugginess resulted from a perfect storm: a small team with ambitious feature lists, refusal to self-edit, compressed schedules driven by small budgets, buggy tools producing buggy content, and combinatorial feature interactions that multiplied defects exponentially. Troika repeated this pattern three times, each time learning "the wrong lesson."

Key insight: Troika's bug problem wasn't any single failure — it was the compounding effect of too many features, too few people, too little time, and a team that never learned to cut scope.

The Core Problem: Too Many Ideas, Not Enough Restraint

Every time Troika started a new game — whether Arcanum, Temple of Elemental Evil, or Bloodlines — the team was bursting with feature ideas. They wanted to do everything: new systems, novel mechanics, things no one had seen before. And they never edited themselves. Cain describes a team mostly in their late 20s and early 30s who just wanted to cram everything in.

Buggy Features Built on Buggy Tools

The team built features quickly, but even worse, they built the tools to create content for those features just as hastily. So both the runtime systems and the authoring pipeline were fragile. Content creators were working with dull, unreliable instruments from the start.

The Screwdriver Analogy

Cain offers a vivid metaphor: it's bad enough to hand someone a screwdriver when they need a saw. But it's worse when you give them a full toolbox containing a saw, and they use the screwdriver anyway — then complain no one told them the saw existed. At Troika, content was sometimes assembled using low-level individual script commands when higher-level, safer script functions existed. For example, instead of calling a single "transfer item" command (which had built-in validation checks), a scripter might manually remove an item and place it elsewhere — skipping all the safety checks and introducing bugs.

Combinatorial Explosion of Interactions

Having many features doesn't just mean more individual bugs — it means interaction bugs. If a game has lock-picking and pickpocketing as separate systems, combining them creates new edge cases neither system was tested for. The more features Troika added, the more these interaction bugs multiplied in ways that were nearly impossible to catch, especially with limited QA resources.

Compressed Schedules and Small Budgets

Cain candidly admits he "wasn't a very good businessman" and that Troika's budgets were never large. This forced compressed development schedules. The team was trying to build massive, feature-rich RPGs in timeframes that left no room for the thorough testing such complexity demanded.

Learning the Wrong Lesson Three Times

Perhaps the most telling part of Cain's account is how Troika responded to each failure:

  • After Arcanum: "That game was just too expansive, too open-world for us." So they scoped down.
  • After Temple of Elemental Evil: A much more condensed game — just a couple of towns and a dungeon. You'd think they could get it right.
  • Then Vampire Bloodlines: They jumped to 3D, real-time combat, and a brand-new engine (Source) that wasn't finished and that they didn't fully understand.

Each time, they identified a problem but overcorrected in a different direction rather than addressing the fundamental issue: scope discipline.

Not an Excuse, an Explanation

Cain is careful to frame this as explanation, not excuse. These were choices the team made. They chose the features, the schedules, and the team size. He also notes Troika wasn't alone — buggy RPGs were (and remain) common across the industry, and he believes the genre is inherently more bug-prone than most.

The "Flawed Masterpieces" Legacy

The result of all these compounding factors was games that players came to call "flawed masterpieces" — a label Cain acknowledges sounds considerably better than "really buggy games." The ambition that made Troika's titles memorable is inseparable from the chaos that made them broken at launch.

Source: Tim Cain — "Why Troika Games Were So Buggy"

References