Unicorn Overlord Recruitment Guide: Conditions by Type

Yes, a set of recruits can be missed, and no captured source disputes that. The third-party guide table published on 2024-03-11 says more than 20 characters can be missed, marks those rows in its own table, and states in the same passage that a player can beat the game without recruiting everyone. A community thread about one recruit decision agrees that the game can still be finished.

What no source settles is the list. The table marks some rows that community commenters say are automatic, and leaves unmarked some rows that commenters say can be missed. Read the material this way: treat every condition that happens inside a battle, or in the conversation right before it, as a one-time window, and treat plain quest completions as recoverable.

The conditions below are organised by the kind of action they demand, not by character name, because the action is what costs you the recruit. Work through them in this order each time you move into a new region.

1. 1

   List the region's recruits first

   Take the roster page's region grouping and write down which characters are listed for the region you are entering, so you know who to watch for.

2. 2

   Separate quest completions from on-the-spot actions

   Most rows are quest completions. The rows that name a battle, a unit or a conversation are the ones you have to handle live.

3. 3

   Deploy the named unit and actually fight with it

   Where a condition names a unit (Melisandre and Colm via Alain's unit, Hilda via Primm's unit, Nina via Mille's unit), put that unit on the field and use it in combat rather than letting another squad carry the map.

4. 4

   Take the pre-battle conversation

   Answer the conversation that runs before the battle. The table's row for Gilbert asks for the option to agree to speak with him, and community reports describe Melisandre challenging you first.

5. 5

   Check the map again after the battle

   Hilda's condition continues on the overworld map, where a further conversation is required after the battle has been won.

6. 6

   Spare the target where the sources say to

   Several rows ask you to spare an enemy rather than defeat them, and the Gammel to Mandrin chain makes the first spare decision the one that gates the second recruit.

This is the largest category in the captured table, and it catches players who rush a map with a single strong squad. In each case the named unit has to take part in the battle, not merely sit in your army. A user-provided video transcript captured on 2026-09-26 (video weGffA6UTRQ, captions unverified) describes the same shape and confirms the condition is checked during the battle, not afterwards.

• Melisandre and Colm (Cornia; Swordfighter and Fighter). The table's condition is to use Alain's unit in battles during the mission it names, and Colm joins when Melisandre does. The Melisandre page covers how many fights that is reported to take.
• Hilda (Drakenhold; Wyvern Knight). Talk to her using Primm's unit during The Champion of Order, then speak with her again on the overworld map. The table and the video transcript agree on the two-step shape.
• Nina (Cornia; Warrior). Talk to her with Mille's unit before fighting her in Uprooting the Rock Rat. Both sources put the action before the fight, not after.
• Aramis (Drakenhold; Swordfighter). The table's row asks you to talk to him using Primm's unit during The General in Black. A community comment claims an alternate route involving Leah; the poster who was asked about it did not receive an answer, so it stays a claim.
• Ithilion (Elheim; Elven Fencer). Talk to him with Rosalinde's unit during The Elven Knight. One table row.
• Berengaria (Drakenhold; Dark Marquess). The table marks her as possible to miss and asks for an in-battle conversation with Alain's unit. A community comment says she joins automatically after the mission and that the conversation is not required, and adds that she becomes temporarily unavailable after one story event and rejoins later. No missable tag is applied here.
• Umerus (Albion; Feathersword). The table asks you to talk to her with Scarlett's unit during A Faded Flower without killing her, while a community comment calls her automatic. The conservative reading is to do the talk and leave her alive.

These conditions are decided before the first turn, and the captured table omits some of them entirely, which is why community reports matter here. The reliable habit is to read the conversation before a battle in full rather than skipping it.

• Gilbert (Drakenhold; Prince). The table's condition is to choose the option to agree to speak with him in the conversation that occurs before the battle in Heir to the Dragonlands, after recruiting Aramis. Whether a missed Gilbert can join later is disputed, and that question is handled on the Gilbert page rather than settled here.
• Melisandre. The table mentions only Alain's unit in battle, but community reports and the captured video transcript both describe her issuing a challenge before the fighting starts that has to be answered.
• Berenice (Cornia; Sellsword) and Monica (Cornia; Radiant Knight). The table describes each as joining when you accept her request during the named side mission, one table row apiece.

Some rows invert the usual instinct: the recruit requires the enemy to survive. Others extend past the victory screen onto the overworld map.

• Gammel and Mandrin (listed as Cornia and Cornia/Elheim). The table has Gammel set free during A Solitary Resistance and Mandrin set free during The Winged Knight, with a later Elheim mission completing each chain. A community thread states plainly that without Gammel you cannot recruit Mandrin, so the first spare decision is the one that matters.
• Mordon (Cornia; Warrior), Auch (Cornia; Wizard) and Jeremy (Drakenhold; Sellsword). Each row asks you to spare him during a named battle. These are single-source rows.
• Bertrand and Govil (Bastorias). The table says to start To Resist or To Yield from the centre so that both are fought. Single-source row.
• Hilda's second step is the map follow-up described above; it is the only clear after-battle action in the captured conditions.

The remaining shapes are repeatable or semi-repeatable activities, which makes them the least stressful conditions in the material - with one disputed exception.

• Ochlys (Cornia; Feathersword). The table lists completing The Winged Knight, starting An Angel's Request and exchanging 30 Divine Shards; the video transcript describes spending 30 Divine Shards in her shop. Two community-level sources carry the figure.
• Selvie (Cornia; Shaman). The sources disagree on how much is required: the table names one specific Sigil trial and a location, a community correction says she joins after agreeing to help at any sigil rather than that one, and the video transcript describes her joining after a conversation that unlocks repeatable sigil quests. Agree to help at the first sigil you meet and the condition appears satisfied in all three readings.
• Renault (Drakenhold; Great Knight). The table says four Liberation quests on any continent after a named story mission; a community correction says Elheim's liberation quests do not count and names a checkpoint fight that also does not count. Plan for four.
• Bryce (Bastorias; Legionnaire). The table says complete The Battle of Solvaquad after recruiting Nina in Cornia, while a community comment denies that simply having Nina in the party is the trigger. Recruit Nina first; whether she must be deployed is unresolved.

Five entries are documented disagreements rather than unclear wording, and they are the reason this page avoids a definitive missable list.

• Berengaria: marked missable by the table, called automatic by a community comment, and described by the video transcript as not requiring an in-battle conversation.
• Umerus: the table asks for an in-battle conversation and no kill; a community comment calls her automatic. The table's row is the only one that describes a method, so it stays the safe path.
• Gloucester: the table treats him as a plain quest completion and does not mark him; a community correction says he is missable and ties him to having Aramis in the party, then narrows that to only Aramis. The correction was posted, questioned and edited inside one thread.
• Sharon and Ochlys: the table does not mark either as missable; a community correction says both should be marked.
• The total: the table says more than 20 characters can be missed, while the corrections both add and remove names. No revised list was ever compiled into a single source.

Success looks the same in every captured account: the character appears in your roster once the battle resolves, and for conditions with a map step a new conversation option appears on the overworld. If the battle ends and neither happens, treat the window as closed for that character.

If you have already cleared the region, the material is split. The table says most characters come from quests you can return for, but for conditions that happen inside a battle the capture contains no consistent account of a second attempt. Plan on the possibility that the character is unavailable in this playthrough. Missing recruits does not block the ending: the table says the game can be finished without every recruit, and the community threads that discuss a missed character do not describe an ending penalty.

These gaps are why every condition above is labelled rather than stated flatly.

• No official recruitment conditions exist in the captured material; every row is guide-site or community reporting.
• The final version of the missable list, after the community corrections that were not merged into one source.
• A searched-for guide page, a community unique-characters page, a message-board thread and a guide-site character archive were all listed as retrieval gaps, so their titles were not used as evidence.
• The exact quests and locations for the claimed alternate routes to Aramis and Mandrin; the question was asked in the thread and left unanswered.
• Whether v1.05 (2024-05-27) changed any recruitment condition, and which version each platform is actually running.