Trap defense that actually works

A trap corridor has one job: make a party spend time in a place where your dungeon can hurt it. Everything else — the trap names, the trigger choice, the decor — serves that sentence.

The public build gives you ten trap mechanisms and five trigger families, but almost none of the numbers. That is enough to design a defense stack. It is not enough to claim a mathematically optimal build, and this guide does not pretend otherwise.

What defense must do

• Delay. Slow the party down so more mechanisms can trigger and your minions can reach the fight.
• Separate. Break a tight formation. A corridor and a control effect can turn one party into a queue.
• Damage. Subtract health before your minions and Boss have to trade blows.
• Convert. Leave survivors alive for the Cell Block. Prisoners are a confirmed system, not a bonus afterthought.
• Preserve. Keep your own workers out of the kill zone and your Boss alive. A defense that kills three adventurers and your cook is a bad trade.

The defense stack

This is a design stack, not a required build order. The trigger and trap families are confirmed; the five-stage arrangement is editorial.

Trap roles

Trigger plan

The five published triggers behave differently in principle, even though their exact values are unknown:

• Pressure plate: positional. The party must step on it. The official example wires one to a Dart Thrower.
• Tripwire: a line trigger. Useful when you expect a specific path through a corridor.
• Sensor: detection-based. The obvious choice for an area or a flank, but its filters are undocumented.
• Lever: manual. Good for a reserve trap you want to fire on command, assuming a minion can operate it.
• Timer: rhythmic. Potentially useful for a repeating hazard, but the interval settings are not published.

For a first corridor, start with a pressure plate and one damage trap. The official wiring screenshot gives you a confirmed example. Then add a second trigger farther down the corridor, so a party that survives the first hit meets another decision.

Test the circuit before the invasion

1. Build one trigger and one mechanism.
2. Send a minion through the trigger zone. Watch whether the trap fires and whether the minion is harmed.
3. If the minion is harmed, add a service route or restrict worker access.
4. Add a second mechanism and test again. Do not stack five unknowns.
5. Only then add a control or utility layer.

Minions and the Boss

Traps are a force multiplier, not a replacement for bodies. The official material presents the corridor as one part of a defense that also includes minions, doors and the Boss.

• Put the Boss behind the first line, not at the entrance. It should be able to reach the fight without being the first thing the party meets.
• Keep a response squad. One or two combat-capable minions with real weapons, set to stay in the domain during a raid.
• Send non-combatants away. Use “Retreat on invasion” and “Confine to Domain” on cooks, scholars and haulers.
• Keep a healer or healing plan. The Behavior tab has a “Seek healing” setting; the exact healing system is not fully documented.
• Use the Cell Block. A corridor that leaves survivors alive is more valuable if you have a prison and guards ready.

Invasion-day checklist

After the fight

The defense does not end when the last adventurer falls. Prisoners need chains, guards and interrogation. Wounded minions may complain or become less effective. The Boss may have taken an Extreme wound in front of the crew, which the Grumbling log can surface as “Saw the Boss get wounded.”

Treat the post-fight state as the start of the next defense: heal, restock, replace losses and read the complaints. The minion management guide has the recovery routine.

Common mistakes

Sources