The Evolution Of Flaws

1. D&D: Low Stats Create Memorable Characters

Tim's earliest inspiration came from high school D&D in the 1980s. Two stories stood out:

The 3-Intelligence Fighter. A player rolled a 3 and dumped it into Intelligence. Tim imposed a restriction: the character could only speak in single-syllable words. This forced the player to think carefully about every sentence, and the constraint made the character genuinely memorable. This concept later evolved into Fallout's "dumb dialogue" system over a decade later.

Joel's Low-Dexterity Cleric. Tim's friend Joel put a 5 in Dexterity and played the resulting clumsy cleric for years. His entire campaign arc revolved around finding Gauntlets of Dexterity. A fun rules quirk emerged: in original D&D, high AC is worse, so when Joel's cleric was surprised (losing his Dex adjustment), his AC actually improved — he was too clumsy to stumble into a sword. The character's weakness became its defining feature.

The takeaway: Players loved characters with unique constraints. Overcoming a challenge specific to their character was a source of joy, not frustration. Low stats weren't regretted — they were fun.

2. GURPS: Formalized Disadvantages

In the late 1980s, Tim discovered GURPS — his first skill-based tabletop RPG. GURPS introduced a formal disadvantage system: you get 100 points to build a character, but you can take disadvantages worth negative points (up to -40) to get more points to spend elsewhere.

Tim's immediate impulse was to grab every disadvantage available ("one leg, one arm, one eye, stuttering, asthma...") to build a 140-point character. The system had to cap disadvantages to prevent unplayable builds.

He loved the system but one thing always bugged him: you had to pick all your disadvantages before the game started. He wanted to reserve some points and discover disadvantages during play — to decide mid-game that his character was afraid of monsters or magic. GURPS had no mechanism for this. It stuck in his head.

3. Temple of Elemental Evil: The Ego Page (2003)

When Tim worked on Temple of Elemental Evil, he created the "ego page" — a stats screen tracking things like most damage dealt, most monsters killed, most powerful spell cast. It was a record of what your character had done.

Players loved it, but not just as a vanity screen. What resonated was the feeling that the game was watching them. Reviews and online comments confirmed it: people liked that the game was reactive, tracking and acknowledging their actions. This was hard evidence that players enjoyed being observed.

4. The Achievement Era (Early 2000s)

Around the same time, the broader industry started implementing achievements — notifications that you'd done something notable. "You fell more than 100 feet." "You killed 10 monsters." Often there was no reward; you were simply told you'd accomplished something.

Two things struck Tim:

1. Being acknowledged was intrinsically rewarding. Players didn't need a reward — just knowing the game noticed was enough. "Wow, the game knows I fell 100 feet and survived!"
2. Tracking required infrastructure. Building an achievement system meant creating a systematic method for tracking player behavior at any point in the code. This infrastructure would prove essential later.

5. The Outer Worlds: Flaws (2016)

When Tim began designing The Outer Worlds' early system mechanics, he wanted something players had never seen before. Flaws were the convergence of everything he'd learned:

• From D&D: Low stats and constraints make characters memorable and fun
• From GURPS: Disadvantages as a formal system, but with the frustration of pre-game-only selection removed
• From the Ego Page: Players enjoy being watched and tracked
• From achievements: The infrastructure for behavioral tracking, plus the insight that acknowledgment itself is rewarding

The flaw system worked like this: the game tracks your behavior (falling a lot, getting hit by robots, etc.) and proposes a flaw — a permanent penalty. If you accept it, you get a perk point. You don't choose the flaw; the game observes and suggests it. It's a GURPS disadvantage that you "buy" mid-game, triggered by an achievement-style tracking system, creating the kind of memorable character moments Tim first saw in D&D.

5.1. The Original Vision Was Bigger

Tim's original design was more ambitious: every flaw would have five associated perks to choose from. For example, robophobia might let you pick between increased damage against robots (adrenaline), higher movement speed near robots, or enhanced perception (treating it as +2) when robots are nearby. They ran out of time and had to simplify, but the core concept survived.

6. The Moral: Ideas Need Decades, Not Minutes

Tim's central point: the idea itself was never the hard part. He had the seed of the flaw system at age ~15. It took 37 years and multiple games to figure out:

• How to express it in code
• How to make it fun for the player
• How to make it something players would want to engage with

The flaw system wasn't invented — it was assembled from a lifetime of observations about what players enjoy. Nearly every feature Tim has shipped followed this pattern: the idea came years or decades earlier, germinated across multiple projects, and only crystallized when the right combination of experience, infrastructure, and context came together.

As he puts it: "If you saw something in a game of mine that you liked, I probably had the idea much earlier. It took me a while to figure out how to do it. That's the hard part."

7. References

• Tim Cain. YouTube video. https://www.youtube.com/watch?v=S2-q_kswvwU