Unicorn Overlord Drakenhold Team: What to Change
Drakenhold is the second region, and the captured players are still running four-slot squads here; one of them notes that five-member teams are still a long way off. What changes is the enemy mix, so this page is about adjustments rather than a rebuild: which of your units get punished by wyverns and casters, what an anti-air squad looks like, and where the cavalry habit still holds.
Keep the early skeleton, one dedicated soak in the front row with everyone else behind, and change what your front row is made of. In the captured threads, mage knight-type units get targeted by wyverns, a shield tank's weak magic resistance pushes it toward the back row unless it is paired with a magic shield, and one squad in your army should be built for fliers, typically archers with a character standing in front to absorb arrows. Cavalry standing in a row is still described as a strong direction here.
On this page
- Evidence state
- Community-reported; no captured list of who is available in Drakenhold
- Version scope
- v1.05 era (2024-05-27); observed 2026-09-26
- Squad size
- Four slots, with five-member squads still far off in one player's report
- New threats
- Wyverns and caster pressure on weak-magic-resistance units, per that thread
- Platforms
- PS4 / PS5 / Nintendo Switch / Xbox Series X|S
What actually changes in Drakenhold
A player asking for help in this region describes the problem as having more units than ideas: the more characters they received, the less clear it became which squads to build. The replies do not propose new squads so much as point at three pressures.
First, fliers. Wyvern-type enemies are named as the reason mage knight-type units have a rough time here, and the same reply adds that those casters do much better later in a magic-oriented region. Second, magic. One player moves a shield tank to the back row because its magic resistance is weak, and another suggests pairing armoured units with a holy knight-type for a magic shield. Third, the four-slot limit itself: with four slots there is rarely a reason for more than one dedicated defender in front with three characters protected behind, and that only relaxes once five-member squads open up.
There is a counter-current, too. Another reply argues that cavalry remain effective in this region, taking a hit or two and paying it back with offense and mobility, and advises putting a good defender in every squad.
Steps: adjust without starting over
Confirm the skeleton still matches
One dedicated soak in the front row, sustain behind. If a squad has two defensive characters and nobody dealing damage, that is the squad to rebuild.
Check who your front row is meeting
Against wyvern and caster groups, keep squishy casters and weak-magic-resistance shield units out of the exposed slot, move the shield unit behind, or give the armoured character a magic shield source.
Build one anti-air squad from units you already run
One captured suggestion is an archer group with your flying characters and a fighter-type who absorbs arrows, so the fliers can do their job without being shot down.
Keep the cavalry row together
Knights standing in a line continue to be described as a strong choice here, and the same thread notes knights want to be in a row with each other rather than spread across squads.
Put the toughest character directly behind the soak
One player's layout puts the tank in the middle of the front row and the toughest back-line character, or one with a counter or parry, directly behind them.
Give the back row the gear
The same thread treats AP and PP items as scarce, so decide who receives them instead of spreading them across squads.
Why these are adjustments, not a rebuild
The job list has not changed: soak, sustain, and damage with a purpose. What changed is which targets your damage has to answer. Fliers break the assumption that your front line can reach everything, so a squad that was fine against infantry stalls; magic makes your most durable physical unit the worst choice for that particular fight; and the four-slot cap forces a trade, which is why the captured players keep coming back to one defender with three protected characters.
One reply frames the whole thing as a skills question rather than a stats question: what a unit's skills do matters more than its numbers, and units that refund action points, with mercenary and knight types named, are worth keeping around. Another player reports that assists hit harder the more units of the same assist type you field, which is one player's read on the system rather than a documented rule.
Layouts players reported in this region
Everything below is an individual layout, quoted as an example rather than a recommendation, and the capture does not verify when each named character joins.
- A player at this point in the region lists seven four-slot squads built the same way, one character in the middle of the front row with a named partner directly behind, among them Alain with Berenice, Ochlys with Lex, Virginia with Clive, Travis with Bruno, and Hodrick with Auch. The same player reports running only one dedicated tank per squad and says five-member squads are still far off.
- A four-slot squad described in another thread as a starter unit for this region: Virginia, Chloe, Berenice and Leah. That player says the squad carried them through this region and the next one on the hardest difficulty they played.
- Three visible replies in a group post from a player a few missions into the region: a dark marquess-type and an evasion flier up front with a caster and a healer behind; a knight tanking the front with a housecarl for area damage, a sellsword to finish kills and a shaman in the last slot; and advice to put an archer in the fourth slot because of what the region fields. Only three of that post's thirteen comments were visible in the capture, and the page carries a note that its thread titles were generated by Meta's AI.
Signs the adjustment worked
- Every squad still answers the two questions: how it hurts the enemy and how it survives.
- Your flier problem has a named solution, a squad you send at flying enemies instead of improvising.
- Shield and caster units stop dying on the maps that used to punish them, because they no longer stand where those enemies hit first.
- Item decisions are deliberate: your AP and PP gear is concentrated on squads you actually rely on.
Version scope and open questions
The freshest captured thread for this region was about five months old at capture with no absolute date, another thread is about a year old, and the group post only resolves to roughly two years ago. 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. One cross-check source dates from 2024-03-22, before the 2024-04-25 patch, so its examples are launch-period practice rather than current-version testing.
No source in the capture lists which characters are available in Drakenhold or when they join, so no layout above is tagged by availability. The comments about wyvern pressure, magic shields and assist behaviour are players describing their own experience, and one detail from a source thread, a quest name and region spelling that appear nowhere else, is not repeated here because it could not be verified.
Frequently Asked Questions
Do I need to rebuild my squads on reaching Drakenhold?
No. The captured advice keeps the four-slot skeleton and changes the front row's composition plus one squad's purpose.
How do I deal with wyverns here?
Build one squad for them. One suggested shape is an archer group plus a fighter-type who absorbs the arrows aimed at your fliers.
Should shield tanks stand in the front row here?
The captured replies split by situation: shield units are fine in ordinary play, but weak magic resistance pushes them to the back row, or behind a magic shield, once casters and wyverns are the threat.