Snowdancer build: Battlefield support controller

What is this build trying to do?

Bring practical healing and forced movement, with enough movement of your own to stay in range. Pick upgrades for the party’s recurring problems. In a melee-heavy group, prioritize effects that help allies reach productive attack positions.

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. Choose whether the round needs healing, enemy displacement or allied access.
2. Check all legal destinations and hazard interactions before selecting forced movement.
3. End within support range of the next fight rather than remaining behind the party.

Treat movement of allies and enemies as part of the same puzzle. Clear access for a melee ally, move a threat away from a fragile character, or prepare a hazard interaction. Decide which outcome matters before spending your support action.

Which cards should you prioritize?

Divide the hand into allied support, enemy displacement and element supply. Cross Winds is digitally confirmed to pull an ally-like scenario figure, while Gathering Force, Polar Vortex, Whiteout and Lifting Gust are named in official fixes. Read their actual target restrictions before planning around them. A control-heavy hand needs enough self-movement to remain in range; a healing hand still needs a useful turn when nobody is injured.

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?

Movement and range support can make your control reach the correct target. Energizing Baton appears in a digital interaction with The Spirit’s Call; inspect the legitimate current effect if you are considering that combination. Do not equate moving an ally with granting them movement for every scenario rule.

Blinding Flurries is named in digital notes with a muddle interaction. Compare condition support with the party’s actual initiative: a debuff after the threat has acted may be less urgent than a perk that improves setup reliability. Choose according to how often your control prevents attacks.

What should you change when the plan fails?

Gathering Force’s effect is corrected not to reduce allied movement. That does not make every forced-movement or movement-granting ability legal on every special object; the Ice Block and other scenario entities have their own restrictions.

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 Snowdancer 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.32895 — Primary official digital announcement; historical patch facts require current-version context.
• Hotfix Notes 10/8 — Primary official digital announcement; historical patch facts require current-version context.
• Patch Notes 0.10.3 — Primary official digital announcement; historical patch facts require current-version context.
• Patch Notes 0.31582 — Primary official digital announcement; historical patch facts require current-version context.
• Patch Notes 0.12.3 — Primary official digital announcement; historical patch facts require current-version context.
• Patch Notes 0.11.3 — Primary official digital announcement; historical patch facts require current-version context.
• Patch Notes 0.11.2.28335 — Primary official digital announcement; historical patch facts require current-version context.
• Closed Beta Hotfix Notes 4/17 — Primary official digital announcement; historical patch facts require current-version context.
• Patch Notes 0.10.2 Hotfix — 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.