Chapter 3 Npc Persona Squad Pipeline

---
title: "6.3 NPC Persona and Squad — From a Mannequin Museum to a Small Society"
part: 6
chapter: 3
status: v3
written: 2026-05-24
author: 이민수
ip_check: done
version: v3
---

# 6.3 NPC Persona and Squad — From a Mannequin Museum to a Small Society

> Primary readers: MMORPG designers who own NPC and hunting-ground content (mid-size teams of 10–50)
> Scaled-down version for solo/hobbyist readers: §6.3.10 "If You're Solo, Just This Much"

I remember the day I used the 6.2 generator to mass-produce five NPCs for one hunting ground and put them in the game. Names, appearances, short backstories — all filled in. I placed them by dropping coordinates. But when I actually walked through that hunting ground, it felt strangely dead. Five people shared the same space and never once mentioned each other. Two of them stood overlapping on the same rock. Someone needed to play the merchant, but all five were scholars. Doren and Mira were each perfectly fine NPCs on their own; bundled together, they were a collection of mannequins.

This is the mannequin-museum state. Every individual NPC is built, but the group is not alive. This chapter covers the pipeline that binds those five into a small society. The core decomposition is Persona and Squad. To use an office analogy: a Persona is an employee's business card, and a Squad is one team's org chart. Stack fifty business cards with no org chart and the company does not run. And the spine of this chapter is the final stage — running one full cycle with the AI to verify that the bundled group talks and moves like people who actually know each other.

> **Author's Operating Note**
> The Squad pipeline in this chapter is an anonymized version of the NPC Persona/Squad tool I run in my company's R&D folder. The yaml structure, the checks, and the voice_lint thresholds faithfully mirror the real tool; the city and NPC names are swapped for the book, the same as in 6.2. The output text is reconstructed from real sessions.

---

## 6.3.1 Persona Is the Business Card, Squad Is the Org Chart

A Persona is an individual NPC's identity. It holds the name, appearance, voice_profile, and role. What the 6.2 generator produces is Personas. Doren Vale and Mira Kost are each one Persona.

A Squad is the unit that binds those Personas into a group. It defines how five people are distributed across roles in one hunting ground, how they relate to each other, and how they move.

| Unit | What it holds | Who makes it |
|---|---|---|
| Persona | name, appearance, voice_profile, role | generator (6.2) |
| Squad | role distribution, relationships, movement | Squad pipeline (this chapter) |

If you do not separate the two, you get blocked in two ways at once. Mass-produce only Personas and you get a mannequin museum; try to build Squads first and you have no Personas to fill them with. Separating them keeps each unit simple to operate. Separation is not severance, though. The point is to lay reuse and verification paths between the two units, and that is the main business of this chapter.

This Persona→Squad decomposition is not mere housekeeping; it opens a longer road. Only when NPC groups are formalized into roles, relationships, and numbers can you later reach dynamic reactivity — where world state (accumulated player behavior) perturbs NPC values and those values become quest trigger conditions. This chapter only points at the entrance to that progressive application; what it covers head-on stops at conservative mass production gated by human review.

---

## 6.3.2 Input — One Page of Squad Metadata

The Squad skeleton starts from one page of metadata per hunting ground. Same philosophy as the city metadata in 6.2: a human pins down only the role distribution and the intended relationships, and the rulebook and the AI do the filling.