Believable Reactivity

Abstract

Problem: How do you make NPCs react to player choices without them appearing omniscient β€” knowing things they couldn't logically know?

Approach: Tim Cain breaks down five distinct methods for NPC reactivity, drawn from decades of RPG development on Fallout, Arcanum, and The Outer Worlds.

Findings: NPCs should react to the results of player actions, not the actions themselves. Five escalating methods β€” from verbal announcements to fourth-wall breaking β€” provide a complete toolkit for believable reactivity.

Key insight: Most players don't need NPCs to explicitly acknowledge what they did; they just need the world to feel like it noticed. Reacting to effects is often more satisfying than reacting to causes.

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

The Core Principle

NPCs should react to the results of player actions, not to the player actions themselves. This single rule prevents the "omniscient NPC" problem where characters magically know things they shouldn't.

Tim notes this is a "fish and water" problem β€” he did it instinctively for years without thinking about it, only becoming conscious of the pattern when working with larger teams whose designers would make NPCs omniscient by default.

Five Methods of Believable Reactivity

Verbal Announcements

The simplest case: the player explicitly tells NPCs what they did. If you return to the king's audience hall and announce "I killed the bandits" in front of a crowd, everyone present now knows. Quest turn-ins are the most common form.

Tim dismisses the idea of simulating information spread over time (knowing in one hour locally, a few days in distant towns) as excessive work most players won't notice β€” and points out it's "adorable" to assume the player who can fast-travel is the only one in the world capable of moving quickly.

Rule: If the player publicly announces something, any NPC anywhere can react to it.

Nonverbal Announcements

Things the player expresses to those around them without saying a word. The prime example: a bandit leader wears distinctive armor. You walk into town wearing that armor. Everyone can reasonably conclude what happened.

Other examples:

  • Returning alive from a known suicide mission
  • Showing up after wanted posters were circulated
  • Simply being present when you were expected to be dead

Logical Discovery

NPCs who could plausibly know or find out through in-world mechanisms:

  • Companions who travel with you and gossip at inns
  • Detectives or police investigating crimes
  • Newspapers (as in Arcanum, where killings made the paper)
  • Magic β€” seers, divination, gods who tell their priests
  • Omniscient entities β€” gods in fantasy settings, AIs in sci-fi (System Shock's SHODAN watched you through cameras everywhere)

A few key NPCs with plausible knowledge can explain how many others learn what you did.

Reacting to Effects

The most powerful and underused method. NPCs don't react to what you did β€” they react to what changed.

You kill the king? NPCs run around shouting "The king is dead!" β€” not "You killed the king!" You wipe out the bandits without telling anyone? Merchants comment that caravans are safe again and the bandits seem to have left. The player's ego is stroked without any NPC needing impossible knowledge.

Tim notes that many players will actually misinterpret effect-based reactions as the NPCs knowing what they did β€” which is the best outcome. The player feels acknowledged without any logical inconsistency.

Fourth-Wall Breaking

Surprisingly, Tim has used this since Fallout and no one has ever called him out on it. The end slides are the clearest example β€” the game tells you the consequences of your actions on towns and characters in ways no in-world entity could fully know.

This is the same technique as Deadpool breaking the fourth wall, but presented through game structure (narration, end sequences) rather than dialogue. As long as it's done carefully, players accept it completely.

References