Unicorn Overlord Cornia Team: Your First Roster

Two worked examples exist. In a Reddit thread about team composition, a player describes clearing all of Cornia before a difficulty step, having built every character into a four-slot squad and pushed them to around level 15, and then noticing they were falling behind. Their squads were grouped by story relationships. In a GameFAQs thread, a player lists six four-slot squads assembled on leaving Cornia, with a caveat that matters: they had also made a detour for a character outside the region, so their roster is not a pure Cornia pool.

Everything else in the capture is commentary on layouts like those: which pairings hold together, which characters should not stand in front, and where support is being wasted.

The first is putting damage characters in the front row. Warriors and housecarl-type characters are described as back-row units, and one commenter adds that even a shielded hybrid attacker is better off behind unless you have nobody else who can hold the slot.

The second is a squad with no damage in it. Reviewing a suggested group of two durable characters and two supporters, a commenter's verdict was that the squad barely has any damage at all. The shape that commenter proposes instead is one tank or hybrid plus two or more damage classes, with support optional.

A third point is quieter: one reply flags guard rate as a big deal at this stage, which is a reminder that the front slot is a numbers question as much as a class question.

A fourth, about a specific character, stays unresolved on purpose. One reply says the front row is where that character reaches their potential because they parry attacks and act again, while other captured layouts put the same character in the back row. Both are player statements, and this page does not pick a winner.

1. 1

   Write down everyone you have, reserves included

   No captured source lists who is available in Cornia, so build the sort from your own roster instead of assuming a fixed set.

2. 2

   Sort by role, not by story

   Cavalry in one pile, fliers in another, ranged and casters in a third, guard tanks and healers in a fourth. The advice captured for this stage is that while squads are small, attackers or mobility types go together: full cavalry or fliers, full ranged, or a durable squad with a tank and a healer.

3. 3

   Give each squad one front-line soak

   Guard-type and evasion-type characters both work, chosen per map. Hybrid characters can hold the front early, but the same replies prefer to move them behind once dedicated options exist.

4. 4

   Add healing to every squad

   Dedicated healers where you have them, a hybrid with a heal or item-based healing elsewhere.

5. 5

   Fill the rest with damage that has a job

   An archer for fliers, a caster or armour-breaking attacker for shielded enemies, cavalry for infantry, and a debuff unit where you need one.

6. 6

   Re-cut squads that duplicate each other

   If two squads are trying to be the same thing, rebuild one into the job your army is missing, then top up levels on repeatable missions or training encounters on the map.

The critiques in the capture are its most concrete material. They are one player's review of another player's squads, not a verdict on the characters themselves.

• Cavalry trio plus a sellsword behind: praised, because the group benefits from the cavalry line bonus and the sellsword adds damage from the back row.
• Fran, Kitra and Miriam: called balanced because each covers a different target type, against cavalry, armour and magic respectively.
• A squad carried by Berengaria with Travis and Bruno: the reviewer's note is that the squad is carried by her.
• Lex and Colm together: both are fighters, which the reviewer calls an extremely narrow class.
• A healer paired with an evasion tank: no synergy, per the same reviewer.
• Lex, Hodrick, Chloe and Yahna: called out as two tanks plus two supporters with barely any damage in the squad.
• Lex on his own: judged weak as a tank, but with a clear job in front of fliers absorbing arrows, which several replies across two threads agree on.
• Auch: suggested as a partner for another caster, such as Yahna or an elf, because of his pursuit behaviour.
• Bruno: advised to pair with a healer, while Chloe is described as better used as support than as a healer.

Two route habits show up in the capture. One reply recommends Drakenhold before Elheim, on the grounds that Elheim is higher level and Drakenhold becomes too easy if done later. Other replies describe short detours into a neighbouring region for a specific character, including entering the elf kingdom only far enough to free a harbour. Both are player habits rather than an official order, and the capture does not show what the detours cost later.

Squad count is the other open choice. One player's answer to slow leveling was fewer, better squads, because experience and the AP and PP items are divided across everything you field.

There is no captured list of which characters belong to Cornia or when each one joins, which is why no squad here is presented as the Cornia team. The GameFAQs roster includes characters obtained by leaving the region; the Reddit squads were built by story pairing and were reviewed by another player as having gaps; and that review is one person's opinion rather than a measurement.

Version scope: the two source threads resolve to a 2025-07-05 date and to a relative age whose two timestamps disagree, and the report itself was compiled from captures taken on 2026-09-26. The latest patch that can be confirmed here is v1.05, in place from 2024-05-27, with PS4 and PS5 served first and Nintendo Switch and Xbox Series X|S awaiting platform review. The official patch note that is recorded elsewhere on this site as touching squads was not retrieved for this page.