Unicorn Overlord Characters: What the Sources Confirm

The official game site says Unicorn Overlord features over 60 unique characters, and this wiki uses 60+ as the working figure. That figure is a floor rather than a headcount: nothing in the captured material shows a number-by-number official list, and three candidate lists that might have supplied one were identified in search results but not retrieved, so their titles and search snippets were not treated as evidence.

What the capture does contain is one structured roster: a third-party guide table published on 2024-03-11. It states that 70 characters can be recruited and lists each by name, class, region and recruitment condition. Those groupings belong to that table, not to the game, and community commenters have corrected several entries since publication. It does not contradict the official sentence, because over 60 sets a lower bound, but this page will not state a total of 70 for the game.

Two gaps shape this page. There is no official roster, and the roster that is in the capture is single-source for most of its columns. The honest version of this page is therefore a short, labelled list rather than a table of every recruit with a role beside each name.

• The community wiki's Characters page was captured as an empty body: zero readable characters and no title, on 2026-09-26.
• A wiki list of characters, a guide-site character archive and a community unique-characters page were all recorded as retrieval gaps rather than used as sources.
• The user-provided video on this page covers Cornia in full but only the early recruits of Drakenhold, Elheim and Bastorias; Albion, the finale and the epilogue batch fall outside its scope.
• The third-party table's own author, writing in a companion community thread, described the available information as fragmented and contradictory depending on where you look.

Both the third-party table and the user-provided video organise recruits by region, and both run in the same order: Cornia first, then Drakenhold, Elheim, Bastorias and Albion, followed by a batch tied to late-game and post-game story content. The table's Region column holds 29 Cornia entries, 13 Drakenhold, 8 Elheim, 7 Bastorias and 5 Albion, with 8 rows left blank. Those counts describe the table's rows, not an official grouping.

The order matters because it tells you when a character can be picked up: Cornia's roster covers the starting cast, Drakenhold's arrives with the second region, and so on through Bastorias and Albion. Region also predicts where the risky conditions sit, because the conditions that can be failed in the captured material are attached to characters who appear in specific battles rather than to the game as a whole.

Most rows in the captured table rest on one source. A smaller set is corroborated by two or more of the captured sources, usually because a community discussion or the user-provided video names the same class independently. These are the rows this wiki is prepared to print.

Treat the single-source rows as provisional. Community commenters flagged class errors in that table, one of them writing that Elgor's class is Dark Marquess rather than the Soldier entry the table carries, and the same thread listed name typos alongside it. Where a spelling in the table looked like a typo and no second source existed, the row was left out of this table rather than guessed at.

Recruitment conditions in the captured material fall into a handful of shapes, and knowing the shape tells you how much attention a given character needs. The shapes below are the ones the sources actually describe; the per-character detail sits on the recruitment guide.

• Quest completion only. The table describes this as the majority case: finish the associated main or optional quest and the character joins, and the table adds that players can return to areas they have left.
• Win with a named unit. Melisandre and Colm are the clearest example, with the table's condition being to use Alain's unit in battles during the mission it names.
• Talk during the battle with a named unit. The table describes Hilda this way with Primm's unit and Nina with Mille's unit, and Hilda needs a second conversation on the overworld map afterwards.
• A choice in the pre-battle conversation. The table's row for Gilbert asks for a specific option in the conversation that runs before the battle, and community reports describe Melisandre issuing a challenge that has to be answered first.
• Spare instead of defeat. The table attaches this shape to several characters, and the community treats the Gammel to Mandrin chain as the clearest example.
• A side activity or an exchange. Ochlys is described as joining after a Divine Shard exchange, and one table row states that Amalia joins after winning the coliseum fights.

Some characters can be missed, and that part is consistent across the captured material. The third-party table states that more than 20 characters can be missed, marks them in its own table, and says in the same passage that a player can beat the game without recruiting everyone.

The list is what is contested. Community commenters added names the table did not mark and removed others that it did. Berengaria is the clearest example: the table marks her, while two independent community sources say she joins automatically after her mission. Berengaria, Umerus, Gloucester, Sharon and Ochlys are the five disagreements the captured material documents. Because of that, this page carries no missable column at all, and the per-character conditions live on the recruitment guide with their source labels attached.

This page is the roster overview. Three sibling pages carry the rest of the chain.

• One character's full chain, failure case or use case: the character pages for Virginia, Melisandre and Gilbert.
• Who joins where, what could be missed and which window is on the spot: the recruitment guide.
• What a class does mechanically: the classes page.
• How players rank classes against each other: the tier list page, which publishes criteria rather than a ranking of its own.

The following gaps are recorded rather than papered over, because they decide how much weight the roster above deserves.

• A complete official roster, or any official per-character list.
• An exact total: the official wording is over 60, and the 70 named entries belong to one third-party table.
• Levels, growth, skills and rewards for the roster. The only per-character numeric material in the capture is a video transcript whose captions are unverified.
• Albion, finale and epilogue characters, which in this capture only the third-party table covers.
• Whether v1.05 changed any character's availability or class; no captured source addresses that.