Abstract
Problem: Tim Cain addresses viewer comments claiming he always portrays himself as the hero in his stories. Can he tell stories where he's clearly the bad guy?
Approach: He shares three stories from Arcanum development at Troika — all 20+ years old — deliberately withholding his own context and internal justifications to let the "villain" framing stand.
Findings: Telling stories from a villain perspective is genuinely difficult. Providing your own thoughts and feelings automatically makes you the more empathetic character. The hero/villain lens is a reductive way to view game development stories.
Key insight: Everyone in game development has good and bad moments. Casting people as heroes or villains misses the bigger points about industry trends, team dynamics, and what development is actually like.
1. The Problem With Perspective
Tim opens by acknowledging comments saying he always comes across as the hero. He notes this is inherently difficult to avoid — when you tell a story from your point of view, you naturally include your thoughts and feelings, which makes you the empathetic character. He challenges critics: "When was the last time you publicly talked about being a bad person?"
He references previous stories where he didn't look good — the "game developer caution" story about a programmer's large estimate that devolved into debates about whether Tim should have fired the guy or was a terrible manager, and the story about firing someone at Carbine on his boss's orders. In both cases, providing his internal context made him seem more sympathetic, which a memoir reviewer explicitly pointed out.
2. Story One: The Tech Schematics
Tim has previously shared his love for Arcanum's tech schematics — he made a little book of them, loved the artwork and interface. But the reason he had nothing to do with their design is that the team held design meetings secretly, without inviting him.
Why? Because Tim was told he dominated design meetings, pushed his own designs aggressively, and when he critiqued others' ideas, he made people feel dumb and discouraged from contributing. The tech schematics — one of Arcanum's beloved features — existed specifically because Tim was excluded from the process. When the design was finished, Tim refused to code it, and Mark Harrison had to step up instead.
3. Story Two: Talking Behind Leonard's Back
Tim was overheard saying to another employee: "Leonard would never figure that out — it's way too complicated." The person who overheard went back to Leonard Boyarsky and told him. Leonard confronted Tim.
Tim admitted to saying that statement, and "a number of other statements too." Leonard was upset. The person who overheard was upset. Tim wouldn't apologize. This caused months of tension at Troika.
4. Story Three: Killing the Arcanum Fan Contest
Sierra wanted to run a PR contest during Arcanum's development where fans would write character backgrounds, with the winner's entry included in the shipping game. Tim raised questions about judging criteria: Should they judge just the idea, or also the writing quality? Would they rewrite poorly written entries (risking the winner not recognizing their own work)? Would they reject good ideas with bad execution?
The discussion devolved into arguments. People got angry. "Really awful things were said." Sierra, who was on a phone call during the meeting, ended the call. The contest never happened and never came up again. Tim was told by several people that he was at fault because he was "very argumentative" during the meeting.
5. On Writing Memoirs
Tim connects these stories to broader challenges with his 558-page memoir. A reviewer suggested he contact everyone he tells stories about to get their side. Tim raises practical objections: What if they refuse? Should the story be cut? And if every story includes both sides, the book doubles in size — at what point does an autobiography become a history book?
His rule for the memoir: only describe what people said and did (things he witnessed or has notes on), never guess at their thoughts or feelings. He draws the line at secondhand stories — if he wasn't there, it's not his story to tell.
6. The Bigger Point
Tim's meta-argument is that the hero/villain framing is reductive and causes viewers to miss the actual lessons in his videos. Every person he discusses — including himself — had good moments and bad moments. People said he pushed his ideas too hard, wouldn't listen, coded too fast with too many features at the cost of code quality. "A lot of my games are known for being buggy — and Outer Worlds wasn't."
His videos are meant as a window into game development — industry trends, team dynamics, the reality of making games. Reducing them to moral judgments about individuals misses the point entirely.
7. References
- Tim Cain. YouTube video. https://www.youtube.com/watch?v=SyPyhXFAbt8