Overview
Game names fail when they are random fantasy syllables. The designer names the capital "Valdris," the neighboring city "Kethara," the river "Shaelund," and the mountain "Grimveil." Each name sounds fantasy-appropriate, but they have no linguistic relationship to each other. Valdris has Germanic consonant clusters; Kethara has Greek-style vowel endings; Shaelund has Celtic-style lenition; Grimveil has Anglo-Saxon morphology. The names come from four different real-world language families, placed in a world where everyone supposedly speaks the same language. The player who notices this (and many do) sees a world built from a name generator, not a world with a linguistic history.
The Language & Naming Conventions prompt builds naming systems with three properties: (1) phonological rules — each language in the world has defined phoneme inventory, syllable structure constraints, and stress patterns that determine which sound sequences are valid and which are not, (2) morphological patterns — names are built from meaningful morphemes (roots and affixes) that encode linguistic history (the suffix "-dris" means "fortress" in the old language, so any name ending in "-dris" is a fortified settlement), and (3) etymological chains — place names are derived from historical events, geographic features, or cultural practices through documented etymological chains that the player can discover (the city "Valdris" is named after the valley [val] where the fortress [dris] was built).
What you get: - Phonological rule set per language - Morpheme dictionary with meaning and etymology - Name generation protocol (root + affix + phonological adjustment) - Toponymy system (place names derived from geography, history, or culture) - Character naming conventions (given names, family names, titles) - Cross-language naming interaction (loanwords, translated names, exonyms)
Built for: narrative designers, worldbuilders, and localization teams who need names that feel like they come from a place — not from a syllable scrambler.