Name Generation Mechanics Snapshot
Abstract
This page snapshots how naming is generated in currently compiled references. It focuses on mechanics and workflow shape, not proprietary table entries.
Use this page when deciding how much friction to put into naming during onboarding.
Mechanics at a Glance
| Source | Naming scope | Procedure shape | Rolls | Output style |
|---|---|---|---|---|
| Shadowdark RPG | Character names | Direct pick/roll from ancestry-scoped lists | d20 (multiple lists) | Fast, character-ready names |
| Book of Random Tables: Cyberpunk | NPC + org + venue names | Domain-specific table roll, often cross-referenced with encounter/job tables | d100 tables | High-volume urban flavor, fast hooks |
| The Perilous Wilds | Region/place names | Two-stage composition: template then components | d12 + d100 components | Constructed, setting-tuned names |
| Foundational RPG Comparison Scaffold | Meta comparison | Comparative matrix of generator depth by system | n/a | Selection guidance, not direct generation |
Source Pattern Notes
Shadowdark RPG
- Mechanic: compact, player-facing name tables attached to character creation flow.
- Design effect: low-friction naming that keeps momentum during chargen.
- Best use: onboarding steps where naming must take under a minute.
Book of Random Tables: Cyberpunk
- Mechanic: many domain-specific d100 name pools (people, corporations, venues).
- Design effect: broad variety and quick tone-lock for city play.
- Best use: NPC/scene naming in live play; can be paired with encounter/job tables for instant hooks.
The Perilous Wilds
- Mechanic: compositional naming pipeline (template plus components).
- Design effect: coherent place names with stronger world texture.
- Best use: region and landmark creation during map/world setup.
Foundational RPG Comparison Scaffold
- Mechanic: no direct name generation; evaluates where systems have deep vs light naming support.
- Design effect: helps choose a base system/reference before building naming UX.
- Best use: design planning and onboarding policy decisions.
Practical Selection Heuristic
- Need a player character name now: use direct character-name tables (Shadowdark pattern).
- Need lots of NPC/location names in one session: use domain d100 pools (Cyberpunk pattern).
- Need settlement/region names with internal consistency: use template + components (Perilous Wilds pattern).
- Need to decide system defaults for naming UX: use the comparison scaffold.