- Gnome Stew - http://www.gnomestew.com -

Prep-Lite: Wireframes And Skins

A few months ago I started down a path of reducing my prep for games that I run. I named my path of enlightenment: Prep-Lite [1]. In my continuing quest to reach Prep-Lite nirvana, I decided to tackle another time sink in my prep: NPC (or Monster) creation. Along the way I learned some important lessons about NPC’s, and the difference between what players experience, and what GM’s see behind the screen, which ultimately lead to a way to make NPC’s quickly.

The Issue:  NPC Creation Is Not Always Easy

Depending on the game, NPC creation (read: creating the stats) can be labor intensive. On the easy side there is cutting and pasting the stat block of a generic Kobold from the Monster Manual all the way through the creation of a 12/14/6 Bard/Fighter/Rogue, Half-Fiend, Halfling [2] with full magic items, spells, etc.

Over the years, I have played different games that have handled NPC creation differently, from the very complex (D&D 3.x…damn you PrC, templates, etc.), to incredibly simple (Icons). If you are lucky the game you are running makes NPC creation a snap, but if you are running a game that does not have an easy way to stat NPC’s, this activity can become a serious time sink in your game prep.

The Experience Is Not About The Numbers

Being both a GM and a player gave me a 360-degree view on this issue. As I was thinking about the importance of NPC stats as a GM and how the NPC is experienced as a player, I came to a realization, which I think I always knew, but never quite put into words.  It goes something like this…

Players experience an NPC through what they do in the session, and not how they are represented on paper.

In the heat of combat, no one but the GM sees the stats for an NPC. The players experience the NPC based on the GM’s descriptions of it, and it’s actions. When a PC has been hit, the player does not know if the attack bonus is +15 or +30; they only know that they have been hit. Likewise, when a PC takes 20 points of damage, they don’t know if that is from 3d6+2 or 10d10.

What matters to the players is how the GM presents the NPC, and how they make it exciting through their descriptions. So if stat blocks are not the key factor for a cool NPC, then why kill ourselves on the work to create complex or detailed stats? Is there a way we can short cut the stats and focus on the description?  And if so, would that not save us time in prep?

First Enlightenment: Going Green

When I ran my Iron Heroes campaign a few years ago, creating stats for NPC’s, especially Human NPC’s, took a long time. For this one session, I had this NPC that I created for a ship-to-ship fight and the NPC gave the PC’s a real run for their money. Being pressed for time planning a later session, I took that stat block, changed around a few numbers, gave it a different weapon and description, and re-used it. My players never knew. I did that three more times with that same stat block.

So if you are going to take the time to create a complex NPC, don’t make it a one time use.  Be green, and recycle that block. Make a few small changes to the block, like:

  • Change up the weapon…players always remember weapons they are attacked with
  • Change up the special move the NPC uses
  • Change the gender
  • Change the general description

Second Enlightenment: Wireframes and Skins

The recycling idea was not new. People have done it for years, and it was an ok time saver, but I wanted to go further. That got me thinking about video games, especially first person shooters. Video game designers build characters in two parts. The first part is the Wireframe.  This is just the shape of the character: tall, short, muscular, masculine, etc. The second part is the Skin. The skin covers the wireframe, and it becomes the clothes, face, skin, hair, etc. More than one character can have the same wireframe, because the skin differentiates one character from another.

Now porting that into RPG’s, the Wireframe becomes the stat block and the Skin becomes the GM’s description of the NPC. The same stat block could be used over and over, and made into different NPC’s, by altering the description. Some games do this already by providing some general stat blocks for different classes of monsters and allowing the GM to skin them.  Silvervine [3] has tables of stat blocks for different types of opponents, which the GM then can skin to their needs.

Third Enlightenment: Simplify

In order to take this concept to the Prep-Lite level, I pushed this idea one step further. Having tables of stats is nice, but if stats are not key to a good NPC, then how much mechanical detail is needed for an NPC, especially one that is not unique or novel in the game world?  In other words: For a generic guard in a keep, is it important to know that this NPC has a 12 Intelligence and a 14 Charisma, and that he has a +5 Rope Use, and a +6 Craft?

The answer is: It depends on what the guard is doing.  If you are making the NPC from scratch and don’t list Rope Use as a skill, and the guard has to tie someone up, now you have to pull a number from the air during the session (which isn’t the end of the world, but can throw you off your rhythm). Or you can spend more time than you may need, figuring out every skill for this guard. I wanted something where I got the best of both worlds. After some thought, I then decided on a premise:

An NPC is good at the things that his role requires, and less adept at everything else.

Back to the guard at the keep. What does a guard need to be good at, in order to be a good guard?:  perception/listening, to see people sneaking around; a fighting skills, in order to defend something; and fitness, so that he can chase people, etc. Any other stat and skill he has can be considered less important to his role.

Using that premise, NPC’s can be reduced to two attributes: Important and Non-Important, and two skills: Important and Non-Important. This makes a wireframe that can be used for anything.  The role of the NPC will determine what attributes and skills fall into the Important and Non-Important groups. So now a single stat block could be used to describe the city guard, the town sage, the court jester, etc.

Take those attribute and skill groupings, add in some basic combat information: attack bonus, AC, weapon damage. Then list any special abilities and now these wireframes become much quicker to create and manage. Finally, add the proper skin, and my NPC is ready for action.

In Our Next Meditation

In my next article,  I will put my money where my mouth is and show you how I took this concept and applied it to my Corporation campaign to create a set of wireframes, based on experience/threat levels, that allow me to create a variety NPC’s, quickly during prep, and even mid-game.

Until our next session, what are your experiences with NPC creation?  What games make it easy? What games are difficult?  What are your techniques to keep NPC creation down to something manageable?

8 Comments (Open | Close)

8 Comments To "Prep-Lite: Wireframes And Skins"

#1 Comment By Roxysteve On February 18, 2011 @ 8:45 am

I’ve recycled the same NPC. The players never notice.

My BRP Call of Cthulhu and D20 Delta Green games generate two distinct but related issues – the occasional need for replacement PCs mid-game and the need for endless crowds of vile cultists/Men in Black for the players to observe, track and usually kill.

Making these human characters was becoming a chore that detracted from the fun of scenario prep (I actually enjoy the involved prep Call of Cthulhu games often demand) so I made an OpenOffice Calc workbook that rolls the stats and generates all the derived information (SAN, luck, skill points and so on) for about a hundred characters at a time.

The D20 version doesn’t do the level-based stat boost and feat allocation part, but since these are usually Bad Gize I just had-wave the stats and grab from a pool of the obvious feats (typically weapon proficiency and rapid shot). I’ve been known not to sweat NPC feat prerequisites either, for Glock-fodder MIBs/Cultist Swine.

I can either read off from my laptop or print a couple of sheets of the results. The printed sheets came in very useful last month when two people wanted in on my Call of Cthulhu game at the last minute. I handed each a sheet of fifty-odd stat lines and said “pick one that has better than 390 occupation skill points and 65 SAN. We need a rich dillitante and a newspaper reporter. Flip a coin if you can’t work it out between you”. Presto! 5 minute character creation from people who had not played before and we could start the game on time.

I used my laptop to grab a stat line from the D20 one on Saturday during the heat of a Delta Green game because I realized that a crucial NPC was not statted-up. I built him to the same level I would have done using the books and dice in about three minutes *while running the game* and the players didn’t notice.

First good idea I’ve had in ages. I recommend the approach to all except Savage Worlds GMs, who don’t need anything except the simple game system working for them when making NPCs.

(If anyone wants a copy to see for themselves you can find it in the file section of the Yahoo Group “The_Call_Of_Cthulhu”. OpenOffice is, of course, free for download. I’m happy to discuss the thing in the Yahoo Group but not here.)

#2 Comment By shadowacid On February 18, 2011 @ 10:05 am

I did something like this with my Shadowrun game. I created a template of generic bad guys with 6 different level of difficulty. The stats for all six of them fit on one page. If I ever need a bad guy on the fly or just doing some prep for someone who isn’t a main villain I can just look at those stats and pretty much get anything that I need, baring some strange critter or spirit power, or a specific rule for a particular spell.

#3 Comment By Bercilac On February 19, 2011 @ 12:56 am

Second session of a campaign tomorrow. I’m grabbing Phil’s idea and shadowacid’s. Four levels (don’t need six), just have to decide for each what value important and unimportant stats are. Very handy. These are rather stripped-down wireframes, resembling the little peg soldiers I made back in summer camp. But they’ll do the job. Gracias!

#4 Pingback By Template stats for FUDGE | usevalue On February 19, 2011 @ 1:11 am

[…] on DNA Phil’s idea of wireframe stats, and the suggestion in comment 2 for a GM cheat sheet, I’m presenting […]

#5 Comment By Bercilac On February 19, 2011 @ 1:13 am

Ended up with 5 levels, 3 stats each (added a specialty, which I find more important in FUDGE).

#6 Comment By Volcarthe On February 19, 2011 @ 1:10 pm

I usually just recycle the stat blocks in established monster books. An orc can become a strong human in a pinch without much prep work.

#7 Comment By Eric Wilde On February 19, 2011 @ 2:56 pm

In the current campaign I’ve got maybe 1 NPC per session fleshed out stat-wise. Sometimes none. Every other NPC has been simply stock with respect to the statistics. It has not detracted from the game in any way.

This has saved a ton of time for me in prep.

#8 Comment By Redcrow On February 24, 2011 @ 10:24 pm

I also recycle existing stat-blocks by taking them from Monster Books or pre-made adventures and just filing off the names and re-skinning.

Its amazing how much mileage you can get by simply replacing the word ‘Orc’ with ‘Bob the Henchman’ on a set of stats.

#9 Comment By Nojo On February 25, 2011 @ 4:51 pm

I love this series, keep it coming. I’m using a modified version of your adventure template for my Rogue Trader games, and it’s worked perfectly so far.

With a single starship having a crew in the tens of thousands, I need NPCs by the gazillion.

I love the idea of having important and unimportant skills base on role.

I’m already thinking of Wireframes and Skins for 40k rpgs. Thanks!

#10 Pingback By More Than One Way to Skin a Monster | intwischa.com On March 16, 2011 @ 9:03 am

[…] the middle of writing this, I read a recent Gnome Stew article on a very similar topic.  Just as DNAphil points out, separating description from mechanics can […]

#11 Pingback By Episode #25 – Adventure Design with Shawn and Phil » Misdirected Mark On August 29, 2012 @ 10:04 pm

[…] Wireframes and Skins article, Never Unprepared, Studio 2, Pandemic, Arkham Horror, Ennies, […]