NPC generator

What makes an NPC memorable

A tabletop NPC lives in the game master's voice. You can improvise, answer any question and change your mind halfway through a scene. A video game NPC has none of that room. It has a model, a few animations, a handful of lines and a place in the world, and the player meets it on their own terms, often while running past. Whatever makes the character stick has to be visible from across the room or audible in the first second.

That is why this generator leans on things you can see and hear. A tabletop group remembers the innkeeper who lies badly. A player remembers the innkeeper who polishes the same spoon every time they walk in. Both work at the table, but only the second one survives the trip into a game engine without a writer standing behind it.

In both cases the trick is the same: one strong detail beats five vague ones. A character described as grumpy, old, wise and mysterious is four adjectives and no person. A character who keeps the ferry and never leaves the river is already a story.

The five parts of an NPC

Each card answers one question a player or a game master needs answered. The name tells the player what to call the character and hints at the world. The role says what the character does all day, written as an action rather than a job title, so it already implies a place and a routine. The look is one detail an artist can draw and a player can spot from a distance. The quirk is a behaviour the player sees in play: a habit, a way of moving, a reaction. The want is the goal that turns the character from scenery into a quest. The sixth card, the first line, is what the character says when the player walks up.

Well-known NPCs show how little it takes. None of them needs a long backstory; one or two parts carry each of them, and the rest stays simple.

• Solaire of Astora (Dark Souls). Role: a knight searching for something the world may not have. Look: a hand-painted sun on the tabard. Quirk: the arms-raised sun salute. Wants: to find a sun of his own.
• Siegward of Catarina (Dark Souls III). Look: onion-shaped armour you recognise in silhouette. Quirk: dozing off by a fire in the middle of his own quest. Wants: to keep a promise made long ago.
• The merchant (Resident Evil 4). Role: sells weapons in places where nobody should be selling anything. Look: a dark hood and glowing eyes. First line: a three-word greeting players still quote.
• Isabelle (Animal Crossing: New Horizons). Role: makes the island's morning announcements. Look: hair tied up with a bell. Quirk: apologising whenever something goes wrong. Wants: an island the residents are happy on.

Turning a want into a quest

A want becomes a quest once you can answer three questions: what stands in the way, where the player has to go, and what changes when it is done. "To find out who knocked down the old bridge" gives you an obstacle (nobody saw it happen), places to visit (the bridge and the people who used it) and an outcome (someone is named, and the ferry keeper can finally rest).

Keep the first version small: one item to fetch, one conversation that unlocks another, one place that was closed and now opens. In a video game every step has to exist as something the player can do, so a want that needs ten scenes to resolve is a campaign, not a quest. At the table you can stretch it; in a game you build each step, so count them before you commit.

Wants also make good conflicts when they collide. Draw two NPCs in the same setting and give the player a reason to help only one of them.

Writing a first line of dialogue

The first line does three jobs at once: it tells the player what kind of person this is, it hints at the want, and it gives the player something to answer. "You're late. Everyone is, around here." does all three in seven words.

Keep it short enough to fit in one dialogue box without scrolling, and write it in the character's voice rather than as exposition. If the line has to deliver information, hide it inside an opinion: a tired shopkeeper complaining about the bridge says more about the world than a sign explaining it.

Then read it aloud. If it sounds like something any character could say, change one word at a time until it could only come from this one.

Using an NPC in a small game you can build

One well-made NPC is enough to carry a short game. A cozy game can be a single village and one want; a horror game can be one house and one person who should not be there. The NPC gives you the goal, the setting gives you the rooms, and the quirk gives the player something to watch.

To go from character to playable prototype, press “Build it in Oryn” under the cards. The NPC lands in the composer as a prompt, and Oryn builds a playable Godot game around it that runs in the browser. For the whole process from idea to finished game, read how to make a video game.

Need names for the rest of the cast? Use the character name generator. Need a premise first? Start with the game idea generator, and once the idea holds up, write it down with the game design document generator.

How to use it

1. Pick a setting

   Choose cozy, fantasy, sci-fi, modern or horror. Names, roles and wants change with it, and so do some looks and first lines.

2. Draw and pin

   Shuffle until one card catches you, then pin it. The other cards redraw around it, so you can build the character one part at a time.

3. Read the description

   The cards combine into one character description. If two parts pull against each other, that tension is often the most interesting thing about the NPC: keep it, or redraw one card.

4. Use it

   Copy the description for your table, share the link to keep this exact NPC, or press “Build it in Oryn” to turn it into a playable game.

Questions