Have you ever been running a published adventure, had the PCs encounter an NPC, and discovered that the NPC’s description was eight paragraphs of undifferentiated text? You remember reading through this stuff two days ago when you were reviewing the adventure, but how are you going to fish out all the little details from that wall of text? (And three scenes later, of course, you realize that everything has spun completely out of control because you forgot that the NPC was supposed to tell the PCs about the properties of the Starstone, but that was hidden away as a single sentence in the fourth paragraph. Whoops.)
Or have you been prepping your own material and found yourself wasting a lot of time writing up lengthy descriptions of your NPCs that never seem to have any real impact at the table? Are you trying to figure out a better way of organizing your NPCs so that you can just focus on the important stuff? (And so that, when your players decide to spontaneously visit the guy they met twelve sessions ago, you’ll be able to quickly pick that NPC up and start playing him again.)
Or maybe you’re really good at juggling all those little details, but you struggle when it comes to really getting into character or making each of your NPCs a unique, distinct, and memorable individual.
And maybe, as you’ve tried to find a solution for these problems, you’ve found various tools or techniques online or in How to GM books that are designed to give you richer and more evocative NPCs… but they all involve spending 5x longer prepping them.
Well, that’s what this Universal NPC Roleplaying Template is all about.
I’ve been using it for more than a decade now, slowly refining it through actual play. Generally speaking, it doesn’t take any extra effort compared to the traditional “wall of text” presentations, but it structures the NPC’s description into utilitarian categories that (a) focus your prep and (b) make it incredibly easy to use during actual play. I’ve found that I can design NPCs with this technique, lay them aside for months at a time, and then pick them back up again smoothly in the middle of play without any review: Instead of trying to parse several paragraphs of dense text, the template will guide you directly to the information that you need.
USING THE TEMPLATE
Name: Self-explanatory. (Or, at least, I hope it is.)
Appearance: Essentially a boxed text description that you can use when the PCs meet the the NPC for the first time. Get it pithy. 1-2 sentences is the sweet spot. Three sentences is pretty much the maximum length you should use unless there is something truly and outrageously unusual about the character. Remember that you don’t need to describe every single thing about them: Pick out their most interesting and unique features and let your players’ imaginations paint in the rest.
Quote: I don’t always use this entry, but a properly crafted quote can be a very effective way to quickly capture the NPC’s unique voice. Generally speaking, though, all you want is a single sentence. You should be able to basically glance at it and grok the voice. (Special exception if the character’s voice is “rambling old man”.)
Roleplaying: This is the heart of the template, but it should also be the shortest section. Two or three brief bullet points at most. You’re looking to identify the essential elements which will “unlock” the character for you.
There are no firm rules here, but I will always try to include at least one simple, physical action that you can perform while playing the character at the table. For example, maybe they tap their ear. Or are constantly wearing a creepy smile. Or they arch their eyebrow. Or they speak with a particular accent or affectation. Or they clap their hands and rub them together. Or snap their fingers and point at the person they’re talking to. Or make a point of taking a slow sip from their drink before responding to questions.
You don’t have to make a big deal of it and it usually won’t be something that you do constantly (that gets annoying), but this mannerism is your hook: You’ll find that you can quickly get back into the character by simply performing the mannerism. It will make your players remember the NPC as a distinct individual. And it can even make playing scenes with multiple NPCs easier to run (because you can use the mannerisms to clearly distinguish the characters you’re swapping between).
You’ll generally only need one mannerism. Maybe two. More than that and you lose the simple utility of the mannerism in unnecessary complexity. It’s not that the character’s entire personality is this one thing; it’s that the rest of the character’s personality will flow out of you whenever you hit that touchstone.
Round this out with personality traits and general attitude. Are they friendly? Hostile? Greedy? Ruthless? Is there a particular negotiating tactic they like? Will they always offer you a drink? Will they fly into a rage if insulted? But, again, keep it simple and to the point. You want to be able to glance at this section, process the information almost instantaneously, and start playing the character. You don’t need a full-blown psychological profile and, in fact, that would be counterproductive.
Background: This section is narrative in nature. You can let it breathe a bit more than the other sections if you’d like, but a little will still go a long way. I tend to think of this in terms of essential context and interesting anecdotes. Is it something that will directly influence the decisions they make? Is it information that the PCs are likely to discover about them? Is it an interesting story that the NPC might tell about themselves or (better yet) use as context for explaining something? Great. If it’s just a short story about some random person’s life that you’re writing for an audience of one, refocus your attention on prepping material that’s relevant to the players.
Key Info: In bullet point format, lay out the essential interaction or information that the PCs are supposed to get from the NPC. The nature of this section will vary depending on the scenario and the NPC’s role in it, but the most obvious example is a mystery scenario in which the NPC has a clue. Rather than burying that clue in the narrative of the NPC’s background, you’re yanking it and placing it in a list to make sure you don’t lose track of it during play. (The Three Clue Rule applies, of course, so just because something appears in this section it doesn’t mean that the PCs are automatically going to get it.)
You could also use this section to lay out the terms of employment being offered by the Mysterious Man in the Tavern. Or to list the discounts offered by a shopkeeper. It’s a flexible tool. In some cases, it might get quite long. But try to keep it well-organized (using the bullet points will help with that). If it just becomes a giant wall of text, its purpose has been lost.
Stat Block: If you need stats for the NPC, put ’em at the bottom of the briefing sheet in whatever format makes sense for the system you’re running.
DESIGN NOTES
Way back in 2001, Atlas Games published In the Belly of the Beast, a D20 adventure by Mike Mearls. This was a roleplaying-intense adventure featuring multiple factions trapped inside the belly of an immense demon. In and of itself, it’s a pretty awesome adventure. But it’s had a particularly enduring legacy for me because it contained the seeds of this NPC roleplaying template. Mearls broke his NPC information down into six sections: Key Information (which, in his version, was bullet points summarizing the character’s background), Quote, Background, Appearance, Roleplaying Notes, and Goals. The disadvantage of Mearls’ version is that it requires more prep work than the traditional method of prepping a character, but the basic idea of structuring the description of the NPC into utilitarian categories that were designed to be used at the gaming table was incredibly useful. (Like most good ideas, it seems simple enough… it’s just that nobody had done it before.)
I promptly absconded with it.
Over the years, I’ve refined the format and tightened its focus, developing it into a streamlined, universal template which I’ve found doesn’t take any extra effort to use, but which still brings all the benefits of the utilitarian structure. In that time I’ve used it in a wide variety of campaigns, and it’s proven itself to be a useful and flexible tool with a lot of different applications. (For example, check out the Muse to Your Left structure for Eclipse Phase games.)
EXAMPLE: BHALTAIR MCCLELLAN
Bhaltair McClellan is an NPC from Paradiso Countdown, an introductory adventure for the Infinity roleplaying game that you can currently snag if you’re a backer of the game’s kickstarter.
Appearance: A boisterous, round-bellied man with thick red hair that tumbles down into a beard that threatens (but does not quite succumb to) unruly excess.
Quote: “You should take a load off, mate. And have a drink. It won’t bring him back, but it’ll keep us all sane.”
Roleplaying:
- A loud and hearty laugh that comes easily.
- Somehow finds a way to use elaborate metaphors featuring Ariadnan ales regardless of the actual topic of conversation.
- Likes to slap people on the back. (If it stings, you know he likes you. If it is hard enough to make you lose your balance, you know he does not.)
Background: Bhaltair is Ariadnan of Caledonian stock. When he was just a young kid, his father went off to fight in a bloody frontier conflict between Caledonia and Rodina. He never came back. Bhaltair made a pledge that he would work to never see his homeworld torn apart by such senseless violence again. He became a politician and quickly discovered how difficult the dream of peace can be. When the Human Sphere returned to Ariadna, he was at first overjoyed at how it unified the planet…and then watched in horror as the Commercial Conflicts ripped his planet apart again. He lost himself in drink for a time and then, concluding that the only way to bring true peace to Ariadna was to solve the off-planet problems that were manifesting themselves there, he became a diplomat. He did not participate in the negotiation of the Tohaa Contact Treaty, but he has recently arrived to take part in the Alliance Summit.
Key Info:
- Although he is a fresh arrival on the EveningStar, Bhaltair had worked with Alinari a few years back when they were both stationed on Shentang together.
- Alinari roped him into working with a Tohaa named Sareelia Mogaal. They all work on the Technology Exchange Commission together and Alinari wanted to open up an “alternative channel of negotiation”.
- Alinari has been having an affair with Gudrun Vastag.
EXAMPLE: SYR ARION
Syr Arion appears in City Supplement 1: Dweredell.
Appearance: Arion is still a man in the flush of youth: Short-cropped, jet black hair sets off his piercing blue eyes. His frame is only lightly muscled, but toned and trained. The weight of his office, however, has brought bags beneath his eyes. And the late hours his sense of responsibility brings often causes his shoulders to stoop with exhaustion. But when the Syr gathers his strength, the image of a great man remains.
Quote: “Just give me time to think. There must be a way.”
Roleplaying:
- A passionate man, but — increasingly — a weary one.
- In desperate need of friends, but years of experience and loss have taught him not to trust lightly.
- Rests his chin heavily into the palm of his hand.
Background: Arion’s mother died in childbirth, and he was reared as the last child of the Erradons by his father, a man whose faculties were already deserting him when Arion was born. Arion’s father believed that his brother had been killed by the Guild, and the one edict he never wavered from was that Arion should be strictly sequestered. As a result, the only true friend Arion had while growing up was Celadon, the Captain of the Prince’s Guard – a man thirty years his senior.
Despite this, or perhaps because of it, Arion dedicated himself to rigorous self-perfection: When he was not learning swordplay from Celadon, he was spending hours pouring over the musty tomes of his father’s library. He saw that his father was a poor ruler, and believed it was his place to restore the honor of the Erradons by restoring the glory of Dweredell.
EXAMPLE: DEVOLA THE NAGAINA
Devola is a character from The Devil’s Spine, a campaign for Monte Cook’s Numenera. I adapted her into this format when I was running the campaign. My local players should skip this section, since I’m hoping to run this campaign again in the future.
Appearance: A massive serpent, 50 to 70 feet long. Her mouth is surrounded by tentacles 15 feet long, most of which have been adapted so that they end in cybernetic or bioengineered tools, syringes, or weapons.
Roleplaying:
- Extremely confident, intelligent, and cunning.
- Alien in thought.
- Considers non-nagaina inferior, almost inconsequential beings — useful as tools or test subjects, nothing else.
- Hoarse voice that sounds like the feeling of a slimy tendril against the back of your neck.
- Weave from the neck and shoulders. Cock head at odd angles.
Background: Devola is a scientist of sorts, specializing in surgical experimentation and evolutionary biology. She is far more learned in her chosen areas of expertise and far more intelligent than the vast majority of Ninth World humans.
Key Info:
- Does not speak to Lily. Lily does not speak in her presence. Never recognizes that Lily is even present.
- Immediately recognizes hosts of her offspring. Talks only to them if present.
- The Insidious Choir: Devola’s primary concern. She considers it a pre-eminent, excessionary threat. (See separate briefing notes.)
- Curing the Devil’s Spine: Devola will agree to remove the defender parasite from an infected character, but only if they agree to destroy the Insidious Choir’s Spinneret. In addition, she will need an impossible blade and gharolan (see next page for details.)
ADDITIONAL READING
Advanced NPC Roleplaying Templates
Quick NPC Roleplaying Template
Spell Component Roleplaying
Anselm’s ontological argument, which appears in his Proslogion, is frequently misunderstood. For reference, the argument basically breaks down like this:
