Abstract
Problem: How should a game director make decisions when their entire team disagrees with them — and what happens when they cave?
Approach: Tim Cain recounts the story of Arcanum's "one-point fiasco," where he overrode his own judgment under unanimous team pressure, and contextualizes it with earlier lessons from Fallout's development.
Findings: Switching Arcanum's escalating point costs to a flat one-point system broke the game's balance irreparably. The same people who pushed for the change later denied responsibility. Leadership means absorbing blame for bad outcomes regardless of who advocated for them.
Key insight: Directors must ultimately trust their gut, informed by experience — because when things go wrong, no one else will share the blame, and when things go right, everyone will claim the credit.
Context: Lessons from Fallout
Tim frames the story with two formative experiences from Fallout's development that shaped his decision-making psychology:
The ending: Tim wanted a happy party ending where you're celebrated for saving the vault. Leonard Boyarsky suggested instead that the Overseer kicks you out. The team went with Boyarsky's idea, players loved it, and Tim realized his original instinct would have been the wrong call.
The water chip timer: Tim hated the time limit for finding the water chip. About half the team liked it. They shipped with it. Players hated it — it made the game feel rushed and discouraged side quests. They patched it out. Tim wished he'd gone with his gut.
These two contradictory lessons — "your instinct was wrong" and "your instinct was right" — created the mental state that made the Arcanum disaster possible.
The One-Point Fiasco
How Arcanum's Point System Originally Worked
Everything in Arcanum — attributes, skills, spells, tech degrees — originally cost an escalating number of points. Spells within a college cost 1, 3, 5, 7, and 9 points respectively, meaning a full college required 25 points. Since you earned roughly 5 points per level, specializing deeply required real commitment and trade-offs.
The Mutiny
QA and the entire 14-person Troika team (all 13 besides Tim) wanted to switch everything to cost one point each. Players felt uncomfortable having leftover points they couldn't spend, and disliked saving up across multiple levels.
Tim argued against it: with flat costs, prerequisites couldn't meaningfully gate progression. Skills and attributes were trivially cheap, and level requirements were merely a matter of time. Players would inevitably become specialists in multiple colleges, destroying the character-building tension.
The Collapse
Against his judgment, Tim made the change. He scrambled to add minimum attribute, skill, and level prerequisites to compensate — but this was happening in the final months before ship, competing against crash bugs, save corruption, broken quests, and animation issues. The balance pass on spells (including the notoriously overpowered Harm spell) never happened. There literally wasn't a minute to spare during their seven-day work weeks of 14-hour days.
Arcanum shipped with a broken character system.
The Aftermath
A couple months after launch, one of the very people who had pushed hardest for the change looked Tim in the eye and said: "You never should have switched everything to one point."
Tim's reaction: "You hypocrite — you were one of the people who convinced me."
Success Has Many Fathers, Failure Is an Orphan
This is the core leadership lesson Tim draws from the experience:
- Good ideas: You're expected to spread credit around, and people get angry if you don't.
- Bad ideas: You absorb the blame alone. The people who pushed for the change will never step up.
- Pressure from above: Publishers and executives can demand features (like unskippable tutorials), but they will never take responsibility when those features are criticized.
- Refusing orders: If you push back, you either lose your authority quietly or publishers stop funding you as "not a team player."
The "Quiet Powerhouses"
Tim reflects on the brilliant senior developers who deliberately never took lead or director roles. They avoided fame but also avoided blame, and had genuinely happy careers. He sometimes thinks they had the right idea all along.
Advice to Directors
Tim was asked by a new director how to make decisions. His answer, informed by 25 years of sitting on the Arcanum regret:
- Delegate authority to leads and seniors
- Gather their opinions and weigh them against your experience
- Draw on experience beyond games — tabletop, theme parks, anything with design principles
- But ultimately, go with your gut
The painful truth: Tim doesn't think he could have looked at 13 colleagues he'd worked with for four years and told them they were all wrong. Even though every fiber of his experience was screaming it was a bad decision, there was that nagging voice: "Remember when you wanted the party ending for Fallout?"
His honest conclusion: there may not have been another choice he could have made. But the lesson stands — trust your gut, because you're the one who'll answer for it either way.