Hnefatafl Defender Strategy: Get the King Out
Defender strategy in hnefatafl is a timing problem: hold the king back while your soldiers create weaknesses, then commit him to a position threatening two corners at once. One escape threat gets closed; two, on the same turn, cannot be. Everything a defender does should feed that final fork.
Your resources are 12 soldiers and the king against 24 attackers on the 11×11 Copenhagen board. Outnumbered two to one, you hold three real advantages: interior lines, a single clear goal, and a king who moves like any rook and takes four attackers to kill. This guide assumes Copenhagen rules (reference); read the attacker guide too, because your whole game is exploiting the wall before it finishes.
The opening: fight for a quadrant, not the board
You cannot contest all four corners, and trying is the polite way to lose. Pick a quadrant early, ideally one where the attackers’ camps coordinate slowly or their first moves were clumsy, and put your soldier effort there. Your aim isn’t conquest; it’s keeping one region unsealed longer than the attackers can afford.
Keep the king home for now. On the throne he’s maximally safe (four-side capture, and soldiers can never occupy his square), and his unspent mobility is a standing threat that fixes attacker pieces in place. Every move the attackers spend hedging against a king dash is a move not spent on the wall. A king who leaves early gives all that up and hands the attack a concrete target.
What soldiers do in the opening: occupy lane-controlling squares in your chosen quadrant, stay off the board edge (the shieldwall capture punishes edge rows), and avoid trades that don’t damage the forming ring. You’ll need those bodies later, as walls, decoys, and sacrifices.
The middlegame: opening the lane and timing the king
The middlegame is about converting quadrant pressure into an actual open file or rank from the king’s region toward a corner. Sacrifices are your sharpest tool here, and defenders systematically underuse them. Offering a soldier to pull a wall piece off its post, or to force a capture that opens your lane, is routinely a winning exchange; your pieces exist to be spent on exactly this. The tempo mathematics are covered at the strategy hub: one clean tempo outweighs several soldiers.
Then, the commitment decision, the hardest judgment in the defender’s game. Move the king when a lane is genuinely open and his destination square threatens two corners; a square where his rook-lines reach two different corner approaches forces the attack to answer twice with one move per turn. Move him too early and he becomes the hunted piece with one plan; too late and the seal completes and no fork exists. When in doubt, one more preparation move is usually right; a king with the throne behind him keeps his options, a king in the open has spent them.
Remember he’s armed in Copenhagen. A king adjacent to the fight can close captures like a soldier, and a defensive line anchored by the king is one piece cheaper than it looks.
The endgame: fork, run, or fort
From a good middlegame, three finishes exist.
The fork is the clean one: king to the two-corner square, attackers close one route, king takes the other. Calculate it fully before starting; a fork with one route actually defended is just a long walk into the net.
The run is the opportunist’s finish: a sealed-looking position often has one sacrifice that breaches the wall for exactly one turn. Count the tempo precisely, breach, dash. This is where attacking walls of single thickness die.
The fort is the fallback: when escape genuinely isn’t there, an exit fort, king on the edge inside an unbreakable defender shell with a square to shuffle on, wins outright in Copenhagen. Forts are hard to complete against attention, but a half-threatened fort splits the attack’s effort beautifully. Note what you cannot do instead: stall. Perpetual repetition loses for the defense, so passive shuffling without a fort is a slow resignation.
Habits of strong defenders
Recount the king’s escape routes after every attacker move; the moment the count hits zero, switch from escape planning to breach planning, not despair. Watch which corner the attack over-defends, since over-defense somewhere means under-defense elsewhere. Spend soldiers proudly and mourn none of them. And play the attacking side regularly; nothing teaches king timing like feeling how much attackers fear an uncommitted king.
Then drill it live on the homepage. When you lose, find the move where your corner threats dropped from two to one; the mistake is almost always several moves before the capture. Both sides’ win conditions stay crisp at how to win.
FAQ
When should I move the king in hnefatafl?
When his destination creates two simultaneous escape threats and the route there is safe against every attacker reply. Not before, absent an outright blunder to punish, and not after the ring seals. Middlegame, usually; the exact turn is judgment, and erring one move late beats one move early.
Should defenders avoid all captures?
No, just captures without purpose. Take pieces when doing so damages the blockade, wins tempo, or defends your lane; decline trades that swap your escape fuel for wall bricks the attack can spare. You’re outnumbered two to one, so equal trades favor you less than they appear to.
How do I defend against the shieldwall capture?
Don’t build capturable rows: keep edge formations short, broken by gaps, or backed so no enemy can stand directly in front of each piece. The bracketing rule needs the whole row pinned, so a single gap defeats it. Full pattern details are in the capturing guide.
Is the defense easier in other variants?
Generally, yes. Edge-escape reconstructions like Tablut and Brandubh multiply the king’s exits and strain the attackers’ wall, and measured results in the tafl community bear the defensive lean out. Copenhagen deliberately hardened the defense’s job to reach balance, which is why it’s the competitive standard.