This chapter is for the builder/GM: the text character sheet template used for NPCs, how to generate one fast, and how to check it against what already exists so your world doesn't grow three identical C-rank Rangers.
The sheet template (light + combat)
NPCs don't need a full PC's bookkeeping. They need identity, numbers you can roll from, and a hook. The template:
===============================================
NAME RANK: _
"Epithet/one-liner" LEVEL: _ (Class) / _ (Job)
===============================================
IDENTITY
Archetype: _ → Class: _ (Assn. / other)
Secondary archetype: _ (or "unranked — pre-C")
Job: _
System: Lyte / Full / none
Path: (Full only — one line of desire)
Affiliation: guild / free company / Association / independent
ATTRIBUTES (only what the scene needs — roll-under targets)
STR _ AGI _ VIT _ INT _ SEN _ SPR _
POOLS & TARGETS
HP _ CP _ MP _ SP _
Attack _ Defense _ Cast _ Resolve _
Pain Threshold _ Armor _ (penalty if any)
COMBAT SIGNATURE (3-4 lines max)
Weapon: _ (damage, skill tier)
[A] signature active(s): _ (cost)
[P] signature passive(s): _
Summons: pocket contents + SP spent (if any)
HOOK / VOICE
What they want, what they'd never do, one detail
===============================================
Rules of thumb:
- Attributes are the sheet. Everything derived (pools, targets, thresholds) can be recomputed, but write the four targets and the pools down — you'll use those live.
- Three or four skills, not twenty. An NPC is their signature: one active that defines their fighting, one passive that defines their build, maybe one more each. If the fight demands more, invent inline — the System would.
- Pools can be honest lies. NPC HP/CP/MP exist to pace a fight. Set them where the drama wants the fight to end, and let the fiction explain the rest.
- The hook line is the most important field. For a Full System NPC, the Path line is the lever the whole setting pulls — write it as a sentence, not a word.
Generating an NPC (GM quick guide)
- Decide the rank first. Rank sets everything: attribute ranges, pool scale, what threatens them.
- E: 30s attributes, HP ~80s. Scrappers, side characters, casualties.
- D: 40s, HP ~100s. Working hunters, party members.
- C: 50s, HP ~120s. Professionals — secondary archetype chosen, party-play tier.
- B: 50s–60s, HP ~150s. Named locals, rising stars.
- A: 70s, HP ~180s. Regional powers, raid leads, celebrity hunters.
- S: 80s+, HP 200+. National assets and secret-war claimants.
- National/Monarch: don't stat the throne. Stat the person, 80s–90s, and note the Bastion and pocket separately.
- Assign the six attributes to the concept, not the optimum. A dumb powerhouse, a frail scholar, a wall of VIT — concept first, and the sheet gets interesting.
- Pick archetype → Association class → secondary archetype from Classes and Archetypes. Non-standard training (foreign, monster-taught, pre-Assn) is allowed and flavorful — note it.
- Give a Job, even a low-level one. Jobs make NPCs feel like people with lives.
- Choose Lyte or Full. Full System NPCs are rare, campaign-important, and should be created deliberately, never as filler. Monarch-track NPCs doubly so.
- Write the hook last — after the numbers, you'll know who they are.
Check before you write: the roster rule
Before creating any new hunter NPC, check the existing roster — the project's Characters/NPCs files, or wherever this campaign keeps its sheets — for two failure modes:
- Duplicates. Same name, same epithet, or same person under a renamed file. Search the project for the name before writing.
- Same-rank-similar-hunter crowding. A new NPC whose rank, class, and role match an existing one. The world should not contain four C-rank Ranged DPS Rangers with a Fisherman Job. If the concept collides, either differentiate hard (different class, rank, or role) or ask whether the existing NPC can carry the new scene instead — reusing a face is almost always richer than adding one.
A quick audit habit: skim existing NPC sheets at the target rank before generating. If the rank already has a resident archetype/class/role, the new NPC should be a contrast — the rival, the opposite build, the embarrassment — not a sibling.
Rank and class ecology matters too: most hunters cluster D–C, A-ranks are countable per region, S-ranks are national and few. If your roster has more S-ranks than B-ranks, the world is broken.
This campaign's S-rank exception. Korea's old national ceiling was nine S-ranks. It now stands at sixteen, plus visiting National-levels — and the growth is deliberate, not bloat: the System has been quietly making S-ranks (impossible risers like Nam Kyungmin, D-to-S in four years; "promotions" like Woo Jinchul's), so the census discrepancy is itself a campaign clue. Keep the count at sixteen and treat every new S-rank as the System's fingerprint. The day a seventeenth appears, someone in the story should notice.
Keeping NPC files
Store each NPC as its own sheet file so the roster rule stays checkable: one file per hunter, name in the filename, folder per region or affiliation if the campaign grows. The sheet above is the whole format — it's deliberately plain text so it can live in any note field without a special type.