Unicorn Overlord Best Class Combinations: How Pairs Work

A pairing is a way to cover a weakness. The clearest statement of the idea comes from a guide-site list of team combinations that opens by saying that units all have specific weaknesses and a pair covers them, and that while some pairs are more potent than others, the list is not a ranking. The community material says the same from the other direction: the players who post squads explain each one by the problem it solves, such as arrow cover for flyers, an accuracy effect for a heavy hitter that keeps missing, a debuff in front of a conditional burst, or healing and point supply around an expensive attacker.

No official combination guide appears in the material captured for this page on 2026-09-26, and there is no ranked list of pairs here. What follows are the goals pairings are built around, a build order, and the examples the captured sources give, each labelled with who reported it.

The captured authors treat a combination as a set-up rather than as two classes standing near each other. Build it in this order.

1. 1

   Name the problem

   Write down what the squad cannot do: answer armour, answer evasive units, survive the front row, finish a wounded enemy, or last without a healer.

2. 2

   Pick the goal, not the squad

   Match the problem to one of the goals on this page. The patterns move between rosters; a specific player's squad usually does not.

3. 3

   Decide the front row first

   Front-row duty goes to whichever unit can absorb the damage in question: a blocking or heavily armoured unit, an evasion build, or a flyer that a partner keeps clear of arrows.

4. 4

   Set the conditions

   Conditions are part of the combination: tactic priorities, which abilities may spend points, which unit acts first, which skill needs to be unlocked, and the gear that makes it work.

5. 5

   Test it and keep the receipts

   The captured players validated squads in mock battles or live attempts. When one works, write down who suggested it and what it was built to beat.

6. 6

   Note the slot count

   Some captured squads are written for four members and some for five, and one author adds a member only when the extra slot arrives. A layout copied without its slot count is a different squad.

Six goals cover nearly every example in the capture. The first four appear in more than one source; the last two come from individual players and are reported as such.

• Protecting a fragile damage dealer or caster: a tank holds the front while the caster works from the back row. This shape appears in multiple player posts and is the logic behind the guide site's physical and magic cover pairing.
• Covering an arrow weakness on a flyer: a Fighter-type unit is described as blocking arrows so a Gryphon Knight can attack, and the guide site notes the same logic works with any flying unit.
• Fixing accuracy against evasive targets: a Witch's focus ability is described as giving an ally an effect that connects with evasive enemies, which the guide site pairs with a heavy but inaccurate attacker.
• Amplifying conditional damage with debuffs: a Shaman-style defence debuff is described as setting up a Dark Knight or Dark Marquess burst, and the guide site names a Refresh ability as the counter to that plan.
• Supplying sustain and points around an expensive attacker: healing, PP feeding to fuel parries, and AP returned on kills are the levers the captured authors mention most.
• Buying a second action or a faster charge: individual players describe granting an ally an extra turn or making a charged attack fire immediately with named accessories. These are single-author reports, not a general rule.

This is the layer that travels most easily between rosters, because it names classes rather than characters. It comes from a single guide-site article, not from ATLUS or Vanillaware, and none of the pairs has been tested by this wiki. The article states that it is not a ranking, that some obvious pairs were left out, and that it balances early pairs with late ones. It carries a March 2025 update date and no patch number.

• Housecarl and Knight: a high-initiative attacker lowers defence, then a Knight's kill-recovering lance ability finishes the target.
• Hoplite and Radiant Knight: one covers physical attacks, the other magic, and the article names Warriors and flying units as the ways this wall breaks.
• Witch and Gladiator: the Witch supplies the effect that lets a hard-hitting, low-accuracy attacker land hits; the same article pairs a Witch with a Hunter for related reasons.
• Fighter and Gryphon Knight: the Fighter blocks arrows for the flyer, and the article suggests disabling its other point-spending abilities.
• Swordsman and Cleric: healing keeps a parry-based attacker alive without moving it out of the front row, since parrying feeds its action points.
• Hoplite and Dark Knight: tuning the Hoplite's tactics so it defends the Dark Knight only at low health suits an axe whose power grows with the damage its user has taken.
• Gryphon Master and Werewolf: the flyer softens whole groups, and the Werewolf finishes the survivors.
• Dark Marquess and Shaman: debuffs land first, then attacks that hit harder on debuffed targets; the article names Refresh as the counter.
• Swordsman and Wereowl: the Wereowl feeds points so the Swordsman keeps parrying and keeps acting.

The second layer is specific. A community megathread collected squads from individual players, each written with front and back rows and each valid only for that player's roster, gear and progress. These are anecdotes with owners, not templates.

• A player's cavalry squads place Knights and a Radiant Knight, or a Doom Knight, in front with a Prince, Witch or Shaman behind, and note that the Knights need to act before their partners.
• Another player runs a physical tank in front with a Shaman-style debuffer and two Sellswords behind, calling those four enough for most fights.
• A flying-focused player puts two sword classes and a Cleric in the back with an evasion tank in front, aiming to delete flyers and evasive enemies.
• One long post lists eight squads after about a hundred hours, each with named characters front and back and each aimed at something distinct, such as a frozen battlefield or a first-turn charge.
• A two-member squad is reported as well: one unit absorbs the enemy squad while the other charges a board-wide attack.

• You can say what each unit is for, in one sentence, without referring to someone's list.
• The conditions are written down: who acts first, which abilities may spend points, and what gear is required.
• It holds up in fights other than the one it was built for, or you know which fights it should skip.
• You can name the source of the idea and the assumptions that came with it.

• Damage is not landing on evasive or flying targets: the accuracy side of the pairing is missing, or its effect is not set to trigger before the attack.
• The back row or the flyer collapses to arrows: there is no arrow-cover unit, or its other point-spending abilities compete with the cover ability.
• The front row folds: the front unit does not match the damage type being taken, since physical and magic cover are separate jobs.
• Damage is not enough: the debuff or the low-health condition the heavy hitter depends on is not in place.
• Nothing triggers at all: check unlocked skills, initiative order, tactic priorities and required gear.
• You cannot assemble the squad: the character-level examples depend on recruitment progress, so fall back to the class-level pairs or check the recruitment pages.

Two philosophies appear in the captured threads and neither is wrong: generalist squads that handle anything, and specialist squads built around one devastating plan. The specialists report glaring weaknesses, and the players who post them usually name the cost.

Observed 2026-09-26. The newest patch that could be confirmed for this wiki is v1.05 (2024-05-27), and the supported platforms are PS4, PS5, Nintendo Switch and Xbox Series X|S. No captured combination source carries a patch number, so none of these squads can be confirmed against the current build. Several candidate results for this query were not retrieved by the capture pipeline, and no video transcript is used on this page. Not covered here: how many combinations exist, which characters are available at which point of the story, and the exact gear paths behind the examples.