NPCs Don't Need More Detail — They Need Fewer Decisions

I had a realization this week that completely reframed what I've been building.

For months, I've been focused on the simulation engine itself—getting thousands of agents to make believable decisions over centuries of generated history. The trait system (now 17 traits: 3 capacity, 11 behavioral, 3 lifecycle) drives everything: how characters escalate conflict, pursue goals, form loyalties, avoid risk, break under pressure.

And, somehow, I completely missed the obvious.

These traits aren't just useful to the simulation. They solve a real problem at the table.

The Real Problem Game Masters Face

Running NPCs in a tabletop RPG isn't hard because of stats or lore. It's hard because of decision fatigue.

At the table, a GM constantly has to answer:

• Would this NPC escalate or de-escalate?

• Do they lie, stall, threaten, or fold?

• Are they loyal under pressure?

• Do they follow rules, or bend them?

• Will they act now, or wait for backup?

And those decisions have to be:

• Fast (players are waiting)

• Consistent (contradicting yourself breaks immersion)

• Believable (arbitrary behavior feels bad)

• Remembered (next session, next month, next year)

Most TTRPG tools give you more content—backstories, stat blocks, plot hooks. Very few reduce the number of decisions you have to make.

Capacity vs Intent

The breakthrough came when I separated two different questions:

What can this character do? (Capacity)That's what attributes handle. Strength, intelligence, charisma—these describe capability.

What will they tend to do? (Intent)That's what the behavioral traits handle. They don't describe power—they describe patterns.

The trait system now has three layers:

Execution Capacity (Can you?)

• Intellect — Mental capability, problem-solving

• Vigor — Physical capability, combat effectiveness

• Essence — Spiritual/social presence, force of personality

Behavioral Traits (Will you?)

• Curiosity, courage, compassion, ambition, loyalty, discipline, harmony, creativity, productivity, greed, aggression

Lifecycle Traits (How long?)

• Longevity, fertility

The capacity traits matter because wanting to do something isn't enough—you have to be capable of executing it. A schemer with high treachery but low intellect makes obvious, easily caught mistakes. A warrior with high courage but low vigor charges bravely into fights they lose. That gap between aspiration and capability? That's where the stories live.

The behavioral traits are what make NPCs decidable at the table.

Bounded Improvisation

Here's what I mean by decidable. Take this NPC:

Captain Varro

Veteran mercenary commander

Behavioral Profile:

• Discipline: High

• Aggression: Moderate

• Loyalty: High

• Ambition: Low

What this means at the table:

• Follows orders precisely

• Avoids unnecessary fights

• Will not betray his employer

• Will refuse promotions that endanger his unit

The GM doesn't need to roleplay Varro's accent or mannerisms. They just need to know: when the players offer him a bribe, he refuses. When they threaten him, he stays calm but doesn't escalate. When they offer him command of the company, he turns it down because his current squad would be reassigned.

That's not flavor text. That's decision support.

Another example:

Innkeeper Elsha

Dominant Traits:

• Harmony ↑↑

• Discipline ↑

• Curiosity ↓

Behavioral Notes:

• De-escalates arguments immediately

• Follows local rules strictly

• Avoids probing questions about strangers

When the players start a bar fight, she throws them out—no questions, no exceptions, because discipline overrides curiosity. When they try to pump her for information about the suspicious travelers, she deflects, because low curiosity means she doesn't ask and doesn't tell.

Two seconds of reading, and she's playable for the entire session.

This is the same principle behind Table Moments—give the Game Master exactly what they need, when they need it, without forcing them to dig through pages of notes or make everything up on the fly.

Why This Feels Obvious in Hindsight

Because experienced Game Masters already do this mentally.

They carry invisible models:

• "This guard is jumpy"

• "That noble wants leverage"

• "This priest avoids conflict"

But those models get rebuilt constantly, aren't externalized, and break under time pressure.

The traits just make that thinking explicit. Instead of inventing behavior from scratch every time a player does something unexpected, the GM asks:

• Does this NPC value harmony or ambition more?

• Are they disciplined enough to stick to procedure?

• Are they curious enough to investigate?

• Are they aggressive enough to escalate?

Not "what would a generic innkeeper do?" but "what would this specific innkeeper do, given who they are?"

More thinking, less scrambling.

The Trust Formula

This week I also finalized what might be the most useful formula in the system—the trust calculation.

It's not a simple opposed check. It's asymmetric.

The target projects an appearance:

treachery = 1 - loyalty
cunning = min(intellect, treachery)  // Smart traitors hide it
doubt = (clamp(ambition - cunning) + greed + (1 - discipline)) / 3
trustworthiness = ((1 - doubt) + loyalty + cunning) * 0.5

The observer evaluates through their lens:

inquisitiveness = (curiosity + intellect) / 2
naivety = (compassion + harmony + loyalty) / 3
incredulity = ((1 - naivety) + inquisitiveness) / 2
insight = min(treachery, incredulity)  // Can't detect what isn't there

Final trust:

trust = clamp(trustworthiness - insight)

The genius of this (if I can call my own work that) is that cunning traitors appear more trustworthy because they successfully mask their ambition. Meanwhile, naive observers with low incredulity miss obvious betrayal.

You get Grima Wormtongue naturally. High intellect + high treachery = high cunning. Weakened king with low incredulity = falls for it completely. The tragedy writes itself.

No special case. No "evil advisor" template. Just traits + math = emergent court intrigue.

What This Changes

The simulation engine generates massive amounts of data: thousands of NPCs across centuries of history, each making decisions driven by their traits. Factions rise and fall. Agents pursue goals, form alliances, betray each other. Events cascade across the timeline.

That's a great feature — but only if the GM can actually use it.

Table Moments solve the presentation problem: they filter the world down to what's relevant right now based on proximity and context. What's nearby? Who knows what? What's happening here?

Behavioral traits answer the next question: How do they act?

This is where the simulation provides playable context. When the players walk into a tavern with six NPCs, the GM doesn't need to improvise six different personalities from scratch. The traits are already there:

• The cautious merchant (low courage, high greed)

• The curious bard (high curiosity, low discipline)

• The disciplined guard (high discipline, low ambition)

Two seconds of reading. Zero preparation. No performance anxiety.

NPCs that come with expectations you can trust.

No alignment charts. No personality essays. No acting degree required.

Just clear behavioral tendencies that reduce cognitive load and let the GM focus on what matters—responding to players, not scrambling to remember who this guard is supposed to be.

Whether you're running D&D, Pathfinder, or a homebrew system, the problem is the same: too many decisions, not enough time. This is about giving tabletop RPG Game Masters tools that work with their brain, not against it.

That's the direction going forward.

More soon.

Previous: Table Moments: Designing a Tool That Thinks Like a Game Master

Next: Digital Dynasties