Sixty-plus playable characters. Five factions. One continent. And somehow, you can tell where almost any character in Unicorn Overlord is from before you read their backstory — just by their name. Alain and Berenice are from Cornia. Hati and Hodrick are from Drakenhold. Ochlys and Yahna are from Elheim. The naming system does worldbuilding work so efficiently that the game rarely needs to explain it.
That's the design achievement worth understanding before you start naming custom units or building original characters in this setting.
Five Factions, Five Phonetic Registers
Vanillaware borrowed from real-world linguistic traditions rather than inventing from scratch. Each faction's names map to a recognizable European naming lineage — which is why they feel coherent without being generic fantasy noise.
French / Romance medieval — vowel-rich, soft consonants, courtly elegance
- Alain
- Berenice
- Scarlett
- Gael
- Cornelia
Norse / Germanic — hard stops, compound elements, battlefield-ready
- Hati
- Hodrick
- Astrid
- Gunnar
- Ragnhild
Elvish / ethereal Romance — flowing, musical, diacritics and liquid endings
- Chloe
- Yahna
- Ochlys
- Celael
- Lirindë
Albion names carry the rougher texture of Celtic and Arthurian tradition — digraphs, silent letters, the sound of Welsh and Irish filtered through fantasy. Bastorias names are the shortest and most direct, reflecting a warrior culture that values clarity over elegance.
What the Game Does With Naming Consistency
The payoff for a consistent naming system is that exceptions become meaningful. When a character has a name that doesn't fit their faction's register, it's a signal — about mixed heritage, displacement, an assumed identity, or a deliberate break from their origins. Dark elves in Elheim carry a slightly harder phonetic register than their court counterparts; it marks them as outsiders within their own nation.
Fan fiction and custom campaign building benefit from this same logic. A Cornian name that sounds vaguely Norse raises a question that needs answering. A Bastorias fighter with an Elheim name has a history. The naming system creates implicit questions that stories can answer.
Naming by Unit Class: Register Within a Faction
Faction membership isn't the only variable. Unit class shifts the register within a faction's naming tradition. Commanders and nobles use the most formal version — particles, bloodline markers, full heraldic names. A Cornian commander is Alain de Cornia, not just Alain. A Drakenhold jarl carries a patronymic or clan suffix.
Scouts and rogues go the other direction. Shorter names, nicknames, single elements. An Albion warden who goes by "Niel" rather than "Niall Caradoc of the Greenwood" is making a statement about their relationship to formal identity — or they've been operating alone long enough that nobody uses the full name anymore.
The Dark Elf Exception and What It Teaches
Ochlys — the dark elf in the game's roster — has a name that follows Elheim's basic phonetic logic but breaks from its softness. The hard K-sound and the -ys ending signal "elvish but different" without requiring explanation. Players with good ears for naming patterns pick this up intuitively.
This is the most useful lesson the game's naming system teaches: differentiation within a faction is as important as differentiation between factions. If every Elheim character sounds identical, the culture feels flat. If dark elves sound like a completely different language, the narrative distance becomes too great. Ochlys lands in the middle — recognizably Elheim, distinctly marked as other.
- Match phonetics to faction: Soft vowels for Cornia and Elheim, hard stops for Drakenhold and Bastorias, digraphs for Albion.
- Scale formality to class: Commanders get full heraldic names; scouts get nicknames or shortened forms.
- Use cultural particles: "de/du" for Cornian nobles, "-son/-dóttir" for Drakenhold, clan names for Bastorias.
- Let exceptions signal backstory: A name that doesn't fit its faction's register is a story hook.
- Generic fantasy names: "Darkblade" or "Shadowmere" don't belong to any of Fevrith's five naming traditions.
- Wrong phonetics for the faction: A Drakenhold character named Élodie reads as Cornian — the soft vowel register signals the wrong culture.
- Identical length for all classes: Nobles have longer names than scouts. Same length across all classes misses the register shift.
- Modern names: "Jake" or "Alex" break the setting's temporal register entirely, regardless of faction.
Building a Custom Liberation Army
Unicorn Overlord's campaign fantasy — rebuilding Alain's army unit by unit — is the exact context where naming decisions accumulate into something that feels like a world. By the time you have a full roster, the names are telling a story about where this army came from, who answered the call, and what kind of coalition you've built.
A liberation army that's pure Cornian sounds like a kingdom reclaiming what's theirs. One that mixes Drakenhold warriors with Albion rangers and Elheim mages reads as a genuinely pan-Fevrith resistance — which is a different story, with different stakes. The names do that work.
For original stories or fan campaigns, use the faction registers consistently within any given community, then deliberately break the pattern for characters who've crossed cultural lines. The naming system rewards readers who pay attention — and the payoff is that backstory can live in a name rather than requiring exposition.
Common Questions
Do Bastorias characters have last names or family names?
In the game's canon, Bastorias characters are identified by clan rather than family name in the traditional sense. The format is [personal name] of Clan [clan name], where the clan name often references an animal or terrain feature (Ironpaw, Sunmane, Stoneback). This is more of a tribal affiliation than a hereditary surname — characters who leave their clan might drop the clan designation entirely, or carry it as a reminder of where they came from. For custom characters who've been displaced from their clan, a bare single-element name with no designation is its own kind of statement.
Can a character have a name from one faction but belong to another faction's unit?
Yes, and the game uses this deliberately. A Cornian knight who defected to Drakenhold still has a Cornian name — their origin is written into them regardless of where they're fighting now. For custom characters, this is a rich source of tension: a character with an Elheim name leading a Cornian cavalry unit is carrying a history that someone, eventually, is going to ask about. The name doesn't change when the allegiance does.
How do I name a half-faction character — someone with mixed heritage?
The most elegant approach is a name that sits on the border between two registers — Cornian soft vowels combined with a Drakenhold compound element, or an Albion base name with an Elheim suffix. "Gwenael" sits between Welsh Albion (Gwen-) and Elheim (-ael). "Sigcolette" is absurd, but "Sigara" blends Norse Sig- with a softer ending that could read as Cornian. The goal is a name that prompts the question — and gives the character room to answer it in the story.