Psychology In Video Game Design

tim-cain game-design psychology ux-design player-experience fallout

Abstract

Problem: Game designers often over-rely on math and spreadsheets, neglecting how players actually think and feel when interacting with their systems.

Approach: Tim Cain draws on his psychology minor and decades of design experience to present three case studies where player psychology trumped mathematical correctness.

Findings: Identical mechanics feel radically different depending on framing (penalty vs. bonus), presentation order matters for usability, and players selectively notice flaws based on their overall opinion of a game.

Key insight: You can make the best design in the world, but if it goes against how players think and feel, it will fail — presentation and framing matter as much as the underlying math.

Source: https://www.youtube.com/watch?v=CvILSkc20vo

1. Background: Why a Game Designer Studied Psychology

Tim Cain minored in psychology at the University of Virginia — not out of idle curiosity, but as a strategic path to AI. In the 1980s, UVA's computer science department had no AI courses; the only AI class was a graduate program in psychology. His plan: minor in psych, get into grad school early, and talk his way into that AI class. It worked — he was accepted at UC Irvine, and the psychology professor let him take the graduate AI course as a full participant.

Beyond the AI angle, the psychology coursework turned out to be one of the most practically useful parts of his education for game design. As Tim puts it: "A good designer thinks about how people think."

2. Case 1: The Fallout Character Creation Screen

Tim revisits a talk he gave nearly a decade ago about Fallout's character creation screen. The screen presents everything at once — attributes with up/down buttons, traits with selection toggles, and skills you "tag" rather than assign points to. The problem: it's not immediately obvious what you're supposed to do.

2.1. What Went Wrong

  • New players found the screen daunting — too many different interaction types presented simultaneously
  • Even experienced players forgot to change things like their age or name (they had to add a popup: "Are you sure you want your name to be 'Name'?")
  • The tagging mechanic for skills wasn't intuitive — players assumed they were assigning points

2.2. What Would Have Been Better

A guided walkthrough that highlights each section in order: name → age → gender → attributes → traits → skills. At the end, everything opens up for free adjustment. This serves both audiences:

  • Casual players learn what each system does as they encounter it
  • Experienced players click through quickly and then tweak freely

Tim used the analogy of a mountain vista: the view is just as beautiful whether you rock-climb up or drive. Making the path easier doesn't diminish the destination. But interestingly, some players pushed back — they felt that making it easier would ruin their experience, even though the functionality was identical. That reaction itself proves the point about psychology mattering.

3. Case 2: The Sleep Penalty vs. Sleep Bonus

In a popular MMO (unnamed, but widely recognizable), players' characters received an XP penalty if they didn't sleep 8 hours every 24 in-game hours. Players hated it, despite inns and beds being readily available everywhere.

3.1. The Reframe

The developers changed the penalty into a bonus. Behind the scenes, they simply shifted the XP curve down — the math was identical:

  • Before: Base XP with penalty for not sleeping = reduced XP
  • After: Reduced base XP with bonus for sleeping = same XP as the old base

The numbers were the same. The experience was radically different. Players loved the bonus version.

3.2. Why It Matters

Tim found it fascinating to watch rational players argue passionately about a change that was purely cosmetic mathematically. Their feelings about the framing — punishment vs. reward — completely overrode the numerical reality. This is textbook loss aversion: people hate losing something more than they enjoy gaining the equivalent.

4. Case 3: NPC Collision and Selective Criticism

Two games released weeks apart in 2025. Both had the same issue: NPCs in towns blocked player movement, forcing you to navigate around them.

  • The poorly-reviewed game: Players and reviewers frequently complained about NPC collision blocking
  • The well-reviewed game: Not a single review or forum post mentioned the identical problem

Tim draws a parallel to Diablo's release, where obvious foot-sliding animations went completely unnoticed by reviewers and players alike.

4.1. The Principle

When players like a game, they ignore or forgive small issues. When they don't like a game, those same issues become focal points for criticism. This isn't hypocrisy — it's psychology. The experience is subjective, and perception of flaws is filtered through overall sentiment.

5. Tim's Takeaway for Designers

Tim is candid that he can't offer a neat formula. Psychology isn't math — that's the whole point. But his advice:

  1. Don't design purely with spreadsheets. Weapon damage curves and stat scaling matter, but they're not sufficient.
  2. Think about framing. The same mechanic presented as a penalty vs. a bonus creates wildly different player reactions.
  3. Guide your players. Don't assume they'll figure out complex interfaces — walk them through, then let them loose.
  4. Accept subjectivity. There's no such thing as an objectively good or bad game — only good or bad for a particular player. Flaws that sink one game are invisible in another.
  5. Watch people play. Observing real players reveals gaps between designer intent and player experience that no spreadsheet can capture.

6. References