Encounter and NPC Design: Encounter Functions and NPC Hyperfixation

Part I: The Five Functions of Regular Encounters

Source: Paolino, "An Enemy Appears!" — originally analyzing JRPGs but directly applicable to tabletop encounter design.

Regular encounters (not boss fights, not set-piece confrontations — the wandering monsters and corridor guards you meet dozens of times) are often dismissed as filler. They're not. They serve multiple distinct functions:

1. Source of Rewards

Encounters supply XP, GP, items, and information. At a macro scale, passing from point A to B generates a predictable quantity of rewards (with variance) — a calculation players internalize to decide risk thresholds.

Design question: What is the expected output of an encounter with this enemy type? Is it calibrated to the risk it poses?

2. Test of Power (Soft Gate)

Encounters function as soft level gates: if the party isn't powerful enough to push through this zone, they'll be driven back. This redirects without locked doors — it's the world's logic operating, not a designer's thumb on the scale.

Design question: At what PC strength level does this encounter become trivial? What paths exist for parties not ready to push through?

3. Drain on Resources

The cumulative resource tax of many encounters across a session is the "game" of dungeon crawl — not individual fights. Players must manage HP, spell slots, torches, rations, and time over an extended expedition. Resource exchange limits (you can burn spells to heal, but you need to sleep to recover spells; you can buy rations but only in town) create the pressure that makes individual sessions feel consequential.

Design question: What resources does this encounter tax? Which are scarce vs. recoverable?

4. Exposure of Weaknesses and Strengths

Occasional encounters break reliable strategies — forcing adaptation. An undead enemy vulnerable to healing spells but resistant to weapons reframes the healer as a damage dealer. A stun-inflicting enemy punishes parties that haven't stocked stun resistance.

These encounters force strategic adaptation, not tactical improvisation. The reward for finding the right adaptation is returning to comfortable rhythm.

Design question: What does this encounter ask of players that their dominant strategy doesn't cover?

5. Exploration of Mechanics

Encounters can introduce or require engagement with mechanics otherwise underused: capturing skittish creatures, managing bespoke resource pools, time-limited objectives, bespoke abilities. Each is a "texture encounter" — adding variety without demanding permanent mechanical changes.

Design question: What unique mechanic does this encounter prompt players to engage with?

Part II: Zelda-Style NPC Personalities

Source: todistantlands, "Zelda-Style NPC Personalities."

The trick for memorable minor NPCs is simple: they are extremely on their bullshit. Three properties:

They have something they are very interested in
They have something of interest or value to you
They are not interested in you or your goals

Roll on these tables to generate NPCs in this style:

Hyperfixation (d20)

d20	Hyperfixation
1	Collects something rare but not necessarily valuable
2	A magic item in their possession
3	A magic item not in their possession
4	A legendary monster or hero
5	Craving a specific kind of food
6	Heard an extremely inaccurate rumour
7	A dangerous location or local landmark
8	A location no one else knows about
9	A portent or omen
10	A household malfunction happening right in front of you
11	A pet or species of animal
12	A special trinket or gadget
13	A weird feature of the landscape
14	A local game or custom
15	The latest fad
16	Another NPC's activities
17	Something belonging to one of the PCs
18	A missing belonging
19	Arguing with another NPC about (roll again)
20	Eagerly gossiping with another NPC about (roll again); does not wish to be disturbed

Motive (d12)

d12	Motive
1	To impress their crush
2	To impress their crush (it's you)
3	To become rich
4	To prove someone wrong
5	To get revenge on someone
6	To be left alone
7	To rescue someone or something dear to them
8	Sheer curiosity
9	To expose their rival
10	To clear their name
11	To topple some local authority
12	Misinformed — believes this will help them (roll Hyperfixation again)

Attitude Toward PCs (d12)

d12	Attitude
1	Lackadaisical
2	Baffled
3	Furious
4	Scamming
5	Obsequious
6	Skeptical
7	Desperate
8	Fawning
9	Envious
10	Amused
11	Doesn't seem to notice them
12	Mistakes them for someone else — attitude toward that other person (roll again)

Usage

Roll all three. Add an adventure hook from the current campaign if necessary — but usually the combination implies its own. Example outputs from the source:

Arguing / Gossip / Envious: Two NPCs arguing about who caused a building to burn down. Each is extremely certain they are right. They look at you expectantly as they make their points. One believes it was the goblins in the creek; the other believes it was Brad and his Wand of Fire.
A pet or species of animal / To rescue someone dear / Defiant then pleading: Challenges you to a test of strength. Needs to know she's strong enough to rescue her dog from the kobolds. If you win, she begs you to go instead.
Convinced they are a legendary hero / Saw an omen / Earnest: Wants you to join their adventuring party to retrieve a shooting star from the sacred clearing — it proves their divine lineage.

Design Notes

The Zelda NPC model works because the NPC's indifference to player goals is information density: their concerns hint at the world (there's a dangerous landmark, someone has a rival, a local authority is disliked). Players extract setting context through social interaction that doesn't require exposition dumps.

The Five Functions framework (Part I) maps cleanly to tabletop encounter design: a single encounter can be understood as an encounter that is primarily a resource drain, with secondary weakness-exposure mechanics — this helps referees calibrate encounter frequency, difficulty, and purpose across a session.

Sources

https://www.magnolienne.com/pinkspace/2023/04/21/surprise/
https://todistantlands.github.io/2023/06/13/zelda-npcs.html