Trapper build: Forced-movement trapper

What is this build trying to do?

Combine trap creation with reliable ways to apply or trigger traps. Preserve movement that crosses your own setup safely when needed. Before upgrading raw trap power, solve any recurring difficulty delivering it to targets.

This is a role-based strategy framework. It does not claim to be a verified level-by-level digital card, equipment or perk list. Check the current digital card text before making an irreversible selection.

How do you set up a repeatable turn?

1. Identify the intended target and a legal path for trap delivery.
2. Build the trap without closing the only safe route for teammates.
3. Trigger or apply the trap through a supported effect rather than hoping for voluntary enemy movement.

Work backward from the hex where the target must end up. A powerful trap is only useful if the enemy can be made to trigger it or another ability can apply it. Leave a friendly route through the room and identify flying targets early.

Which cards should you prioritize?

Use trap creation, a dependable trigger or forced-movement route, and a way to cross the area after setup. Proficient Hunter is digital-confirmed to require a hex with a trap. Persistent Pitfalls is documented in mid-pull interactions, and Path of Pain and Mother of All Traps are confirmed movement-related candidates to inspect. Keep a non-trap contribution when the encounter includes enemies your delivery package cannot reach.

Compare a candidate card against the job your current hand cannot accomplish: reaching a useful hex, making the primary attack legal, surviving the next enemy action or recovering a disrupted turn. Avoid upgrading a number while losing the only action that keeps the sequence reliable. Exact level selections remain subject to digital Codex verification.

How should equipment and perks support the plan?

Choose movement that solves crossing your own setup and positioning for delivery. Decanter of Mists appears with Unavoidable Outcome in a fixed interaction, but its availability and current effect must be checked before building around it. An item that creates a trap is useful only when you can apply it.

Careful Footing and Machinate appear in digital notes. Assess Careful Footing when safe movement over your own layout is the bottleneck. Verify the current interaction with Spring Loaded rather than assuming a perk automatically triggers or avoids every trap-related effect.

What should you change when the plan fails?

A forced-movement chain can expose the Trapper to retaliation. Official Path of Pain fixes explicitly preserve retaliate damage in relevant range. Do not calculate the turn solely from trap damage while ignoring the character’s position.

Identify whether the failure was positioning, timing, a resource shortage or a party mismatch before replacing the entire hand. Record a change and test it over another expedition rather than changing several decisions at once.

Which references help with this build?

Start with the Trapper class reference, use party composition to assign allies’ roles, and revisit card economy when the party exhausts before completing its objective.

Evidence boundary: Roster name corroborated against tabletop index and digital full-roster announcement; exact digital class text and unlock require Codex verification. Strategy is tabletop-informed editorial advice.

Sources and version notes

Researched on October 16, 2026 for the digital edition. Strategic recommendations are editorial advice; they are not represented as hands-on testing. Refer to current in-game tooltips when a patch changes an interaction.

• Official Frosthaven announcements and patch notes — Digital: 1.0 features and earlier patch-confirmed names. Historical fixes do not prove current bugs.
• Cephalofair official Frosthaven FAQ — Tabletop ONLY: class mechanics and rules context; not a claim of exact digital implementation
• Frosthaven asset index — Tabletop ONLY: seventeen class names and source asset identification, no digital numeric parity
• Patch Notes 0.32366 (July 22) — Primary official digital announcement; historical patch facts require current-version context.
• Patch Notes 0.13.30384 — Primary official digital announcement; historical patch facts require current-version context.
• Patch Notes 0.32181 — Primary official digital announcement; historical patch facts require current-version context.
• Patch Notes 0.31273 — Primary official digital announcement; historical patch facts require current-version context.
• Patch Notes 0.31984 — Primary official digital announcement; historical patch facts require current-version context.