Non-Player Character Meaning: The Complete NPC Glossary

A non-player character is any entity in a game world that the player does not control. The term covers shopkeepers, quest givers, hostile mobs, ambient crowd members, and scripted bosses. In the Neta Studio 3D game builder, every NPC you place is a real object in the Three.js scene with a behaviour component attached, so the meaning is not abstract: you can open the stack, read the state machine, and walk into it.

This page is a glossary, not an essay. Each term is defined in plain language, then tied to something you can inspect in a playable world. Where spelling variants confuse people, the page says which form to use. Where a term is routinely misread, the page names the misreading and corrects it.

Quick Answer: What Non-Player Character Means

A non-player character is a character in a game that is not controlled by the player. It is driven by a script, a state machine, or an AI system, and it exists to populate the world, give quests, sell items, block paths, or fight.

Non-playing character, non player character and non-player character all refer to the same idea. The hyphen is a style choice, not a different concept. The abbreviation NPC is the form most people use after the first mention.

The distinction that matters in practice is control, not hostility. An NPC can be friendly, neutral, or hostile. What makes it an NPC is that the player does not drive it. In the 3D game builder, that maps to a behaviour component: if the object has one and the player does not, it is an NPC.

The NPC Glossary, A to Z

These are the terms you will meet when reading about NPCs, writing design docs, or inspecting a world. The plain meaning column is the one to quote in a design review.

Several of these terms overlap. A quest giver is a background NPC until the player interacts with it. A vendor is a quest giver that also opens a trade panel. The category describes a role, not a separate engine feature.

How the Spelling Variants Relate

Non-player character, NPC, NPCs, NPC's and non playing character are the same referent in different written forms. The hyphen in non-player is a compound-modifier rule, not a technical distinction. Non playing character is the same compound without the hyphen and with the participle written open; it appears in casual writing and in some older docs.

Use the full form in a title, a definition, or the first mention in a document. Use NPC after that. The plural is NPCs, no apostrophe. The apostrophe belongs only to the possessive: the NPC's dialogue, the NPC's patrol route.

In running text, the safe pattern is: spell out non-player character once, then write NPC and NPCs. Avoid NPC's as a plural. It reads as a possessive to most editors and will be flagged in review. If a style guide forces nonplaying as one word, follow the guide internally, but keep the hyphenated form in public-facing copy because that is what people search for.

The same rule applies to the adjective form. Write NPC behaviour, not NPC's behaviour, unless you mean the behaviour belonging to one specific NPC.

Common Misreadings

Three misreadings account for most confusion around the term. Each one is easy to correct once you look at the object in a running world.

A bot is an automated player that occupies a player slot. An NPC is world content. The distinction matters in multiplayer: a bot can be kicked, scored and reported like a player, while an NPC cannot. In Mini World, the training dummies are NPCs; they never take a player slot and never appear in the scoreboard.

Hostile mobs are NPCs, but so are shopkeepers and quest givers. In The Cyclops' Island, the cyclops is an enemy NPC and the dock trader is a vendor NPC. Both have behaviour components. Only one has an aggro branch.

A background NPC may have no dialogue component at all. It has an idle behaviour and a patrol path. Adding a dialogue trigger to every crowd member is a common cause of interaction spam in dense scenes. Gate dialogue on distance and on a cooldown.

Behaviour Terms You Will Meet

Behaviour is where most NPC work happens. These four terms describe how the decision layer is built. They are not mutually exclusive; a single NPC can use a state machine at the top level and a behaviour tree inside one state.

A state machine is a fixed set of states with explicit transitions. An NPC might have idle, patrol, chase, attack and dead. Each transition has a condition, such as distance under 8 units. State machines are easy to debug because the current state is a single value you can print. They become unwieldy when states multiply and transitions overlap.

A behaviour tree is a hierarchy of nodes that returns success, failure or running each tick. Selectors try children in order; sequences run children until one fails. Behaviour trees scale better than flat state machines because shared subtrees can be reused across NPC types. The cost is that a failing branch can be hard to trace without a visual debugger.

Goal-oriented action planning searches for a sequence of actions that satisfies a goal given the current world state. Instead of hand-writing transitions, you declare preconditions and effects, and the planner finds a path. GOAP handles emergent combinations well and is harder to predict in review. Small worlds rarely need it.

Utility AI scores each possible action with a curve and picks the highest score. It produces smooth, blended behaviour and avoids the visible state flips of a state machine. The tuning cost is in the curves, and a badly shaped curve can make an NPC oscillate between two actions each tick.

AI NPC and Language-Model Terms

The AI NPC label is used loosely. In this glossary it means an NPC whose decisions or dialogue come from a model rather than from a fixed script. That can be a small local classifier or a hosted language model. The important distinction is what the model is allowed to control.

A dialogue model generates or selects the NPC's lines. A memory store keeps facts the NPC has learned about the player, such as a name or a completed quest. Intent is the structured action the model wants to take, for example offer_quest or open_trade. In a working system, the model produces intent; the game code validates it and performs the action.

That split is where language models fit and where they do not. A model is good at choosing among known intents and phrasing a line. It is not a place to put collision, pathfinding, or combat timing. Those belong in the behaviour layer, which runs every frame at a fixed tick. A model call has latency and variable output; a chase branch cannot wait on it.

Start Here: The NPC Guide Index

This page defines terms. The rest of the cluster answers the questions people ask next. Use the index by question, not by page order.

If you want to see the terms in motion, open Mini World in the 3D game builder and inspect a vendor and an enemy side by side. The behaviour components are visible, and editing one updates the running scene.

Walk into the world it belongs to

A sprite is a character with nowhere to stand. The last step is the one nobody else offers: take the sheet you just built and put it in a world someone can walk around in — a small island, a planet, a rainy street corner. Every world on this site was made from one written description and published as a page you can play.

FAQ