SEO guide
Slay the Spire 2 Ironclad Block Build
An Ironclad block-build guide for turning defense into damage without losing early fight tempo.
Quick answer
Ironclad block-build pages should explain when block is a win condition and when the deck still needs plain damage.

What to check first
Use this page as a practical search-intent answer first, then follow the related database links for deeper card, relic, character, boss, and patch context.
- Take enough early attacks before committing to slow block payoff.
- Upgrade the card that changes the next elite or boss turn.
- Treat block scaling as offense only after the deck can survive setup.
Block is not automatically scaling
A block build works only when the deck can convert defensive turns into progress. If the deck blocks well but never ends the danger window, elites and bosses still punish it. The first check is whether the run has enough front-loaded damage to buy time for the block package.
- Keep a damage floor before adding more defensive synergy.
- Ask whether the next boss rewards longer fights or punishes them.
- Use relic and route context before calling the build reliable.
When the build becomes real
The build becomes more than a pile of block cards when it has payoff, draw, and matchup coverage. Video review should capture the first fight where blocking changes the result, not only the finished turn where the deck looks solved.

- Track the first fight where block protects an upgrade or elite path.
- Mark expensive attacks and block payoff cards as support-dependent.
- Link weak damage floors back into Ironclad build fundamentals.
Common mistake
The common mistake is adding every block payoff before the deck has a way to win. A block build still needs damage conversion, draw smoothing, and a plan for bosses that punish slow setup. Exact block values, payoff text, and current-patch interaction timing are needs verification before this page should publish fixed thresholds.
Evidence to collect next
The next Ironclad block evidence pass should capture the reward screen, current block package, damage floor, next boss, and the first fight where block either protects an upgrade or fails to end the fight. The page should record why the deck won, not just that it produced a large block number.
Editorial note
This page is part of the first English-only content batch. It is written conservatively for Early Access and should be tightened whenever a major patch changes public information or run data.