Unicorn Overlord Best Formations: How to Build a Unit

Read across the captured threads and the same shape keeps appearing: one character who is meant to be hit, and everyone else standing behind them doing something useful. In a thread asking for formations through the game, the most-referenced reply reduces it to picking one proper tank in the front row, one healer in the back row, and filling the rest of the back row with damage. A later squad thread for Drakenhold adds the qualifier that in four-slot squads there is rarely a reason for more than one dedicated defender up front while three characters are protected behind.

The less visible half of a strong squad is that it has a story about how it wins. A reply in a thread from a player preparing to enter Albion puts the whole exercise into two questions per squad: how it deals damage, and how it stays alive. That player's conclusion was that the squads behaving reliably were the ones with some logic to how they work.

• Soak: a guard-type tank or an evasion tank, chosen against what you expect to fight.
• Sustain: one healer or another heal source in the back row.
• Damage: one or two attackers, at least one of which handles the enemy class that keeps stalling you.
• Tactics: each attacker's targets set by condition instead of left on default.

The captured advice is more useful as a checklist than as a list of squads. These are the checks that recur across threads and guide-site pages.

• Can you say, out loud, how each squad deals damage and how it survives? If either half is missing, that is the squad to rebuild.
• Does your front row hold up against what it actually meets? Guard tanks and evasion tanks fail in opposite directions: one reply points out that a shield-type tank is weak to magic, so it should not be walked into a witch squad, and the evasion option should be used instead.
• Does the squad have sustain? Several replies converge on some form of healing in every squad, whether from a dedicated healer or another source.
• Does your damage come back around? Comments single out classes that recover action points on a kill, naming warriors, cavalry and mercenaries, and argue you need only one such class in a squad rather than stacking them.
• Are your squads too alike? The same thread recommends deliberate variety: one squad built around magic, one around archers, one that tanks by evasion, so that some squad is already the answer to whatever the map fields.
• Are you spreading yourself thin? A reply in another captured thread suggests unlocking deployment slots in a squad you already own before unlocking extra squads.

1. 1

   Count squads and slots first

   Look at how many squads you field and how many slots each one has. Decide whether your next unlock goes into a new squad or into a slot in an existing one; the captured advice leans toward the existing squad.

2. 2

   Pick the character who is meant to be hit

   Guard-type units in the Hoplite mould and evasion units in the Thief mould both appear as front-row answers. Hoplite-type units are described as weak to magic, so choose the evasion option when the map is caster-heavy.

3. 3

   Put a heal source behind them

   One healer in the back row is the common pattern. Replies also accept a character with a partial heal, or a soldier-type supported by healing items, for squads you cannot staff fully.

4. 4

   Fill the remaining back slots with damage that has a name

   Say what each attacker is for: a caster such as Yahna for armoured targets, an archer for flying and evasive targets, a housecarl or cavalry type that attacks again after a kill.

5. 5

   Set the targeting conditions

   One reply describes setting a main attack several times with different priorities: mages first, then fliers, then a low-HP fallback so the attacker still strikes. Others use lowest-HP conditions so a squad finishes one enemy instead of spreading damage.

6. 6

   Repeat for the squads that look like copies

   Make one squad the anti-armour answer, one the anti-flying answer and one the evasion soak. If you want a ready-made reference, watch how enemy squads on the map place their units.

The pattern is stable because the weaknesses are complementary. A guard tank that shrugs off physical hits folds to magic; an evasion tank that dodges physical hits is undone by accuracy and true-strike effects. Running both types in one army, instead of trying to make a single squad immune to everything, is how the captured threads handle that trade.

The rest is economy. Action points and passive points are limited, which is why kill-triggered recovery appears as a suggestion to spread one such class per squad, why a cavalry row that buffs itself is described in its own right as a unit, and why fielding too many squads is blamed for slow leveling: experience and the AP and PP items are divided across everything you deploy.

It also explains the specialisation advice. A squad built to do one thing, such as take a garrison or hunt fliers, can be good at that job with ordinary characters, while four squads that all do the same average thing leave holes. One reply adds a mechanical footnote worth knowing: shield units with cover skills can be used from the back row instead of the front, and pursuit attacks are described as the counter to cover.

• You can state, in one sentence, how each squad hurts the enemy and how it survives.
• An enemy type that used to stall you, such as pure armour, a flying group or a debuff line, now has a squad you send instead of improvising.
• Losing your main attacker does not end the fight, because the squad still has a second damage source and a heal.
• Your squads look different from each other: an archer squad, a caster squad, an evasion squad, a cavalry row.

The troubleshooting notes in the captured threads all map a symptom to a missing job.

• Armoured units do not go down: the squad has no magic or armour-breaking damage.
• Flying or evasive enemies stall you: no archer or true-strike answer.
• The back row keeps dying: the front slot is not a soak, or someone who should be behind is standing in front. Warriors and housecarl-type characters are called out for this more than once.
• Action points run dry after a turn or two: no attacker that recovers AP on a kill, and no gear decisions supporting one.
• Levels crawl and gear runs thin: too many squads, with experience and AP and PP items split between them.

Copied layouts are a starting point, not a verdict. The clearest example in the capture is the guide site that anchors this topic: its sample rosters and the description text beside them do not agree, with the prose naming characters that are not in the roster shown, so only the rosters are usable and the prose should be ignored. A separate guide site's team-combination page states outright that its list is not a ranking and explains only why particular pairs work together.

Players also copy a layout and then get stuck with it. One reply in the main formations thread warns that long-term picks are not really available early, because squads only become what they are once units can be upgraded and five slots open up. Nothing in the capture marks which examples are reachable at which point in the story, so an example that names characters you have not met is not an answer for your current map.

The most practical adaptation habit in the capture comes from a reply in the same thread: walk the map, fight the NPC groups that show sword icons in their speech bubbles, and read their squads before the fight. Those formations are built by the game rather than by a player, and the reply suggests taking inspiration from how they mix units.

The latest patch that can be confirmed from the captured material 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. No official source in the capture gives a formation ranking, and no captured source for this page carries a version label, so read everything here as community and guide-site practice gathered between launch and 2026 rather than as a current-version ruleset.

Two gaps stay open. An official patch note recorded elsewhere on this site as touching squad-related and equipment changes dates from 2024-04-25, but its text was not retrieved, so whether it moved any of the advice above is unverified. Separately, the example squads rarely say where their characters come from, so no layout here is tagged with a region or a story point.

One more limit is worth stating plainly: the capture contains no systematic rule for which of the front or back positions a character should occupy. A single reply describes a personal habit of leaving two characters in the outer front positions with three behind, which is one player's shorthand rather than a rule you have to follow.