Boss Preparation

Boss preparation starts when the boss is revealed, not at the final rest site. The visible opponent turns every card reward, shop, upgrade, and risky path into a more specific decision. You do not need a card-by-card script; you need to understand what the fight asks and whether the deck can answer it repeatedly.

Boss patterns and values can change during Early Access. Use the enemy index and each boss page for current moves, HP ranges, encounters, and the documented pattern.

Translate a Pattern Into Tests

An attack pattern is useful only after it becomes a deckbuilding question. Look for:

Opening pressure: Does the boss attack before setup cards can pay back their cost?
Large turns: Is there one turn that requires concentrated Block or mitigation?
Repeated pressure: Can the deck defend several turns without exhausting its resources?
Multiple targets or summons: Does damage need to be split or applied to all enemies?
Debuffs, statuses, or curses: Does the fight reduce consistency over time?
Phase changes or recovery: Must the deck produce another burst after appearing to stabilize?
A long clock: Does the boss become more dangerous while the deck remains flat?

Write the weakest answer in plain language. "I cannot block the large hit if my key Skill is in the discard pile" is actionable. "The deck needs to be stronger" is not.

Measure Setup Speed

Count the energy and cards needed before the deck reaches normal output. A three-Power engine may dominate turn six and still lose too much health on turns one through three. Test the bad draw order as well as the ideal one: if the scaling card is near the bottom, can the deck cycle to it and survive?

Useful fixes include immediate Block, cheaper setup, draw, Retain, energy, or a potion reserved for the opening. Another scaling card does not fix slow setup unless it also improves access or survival.

Separate Burst From Scaling

Burst answers a dangerous moment; scaling improves repeated future turns. Bosses often require both.

Burst damage can remove a summon or finish a phase before another attack.
Burst defense can survive the known large turn.
Scaling damage prevents the fight from lasting indefinitely.
Scaling defense keeps repeated patterns manageable.

When evaluating a reward, identify which category is missing. A deck with excellent inevitability may need one immediate answer. A deck that starts powerfully may need a reason its tenth turn is better than its third.

Use Known Bosses as Concrete Exercises

The current enemy data exposes several readable patterns:

Ceremonial Beast repeats a short Stamp and Plow sequence. A repeating pattern lets you compare defensive output against the same cycle rather than relying on vague averages.
Rocket moves through targeting, beam, charge, laser, and recharge actions. A sequence with a charge window asks whether setup or offense can exploit the lower-pressure turn before the payoff attack.
Knowledge Demon includes conditional behavior and Curse of Knowledge. This tests consistency and the cost of a fight that interferes with the deck over time.
Queen has conditional actions tied to encounter state. Conditional patterns reward checking the full move and encounter information instead of memorizing one loop.
Test Subject #C14 changes behavior around respawns. A phase-dependent fight asks whether the deck can rebuild output rather than spending every resource on the first apparent finish.

These are planning examples, not fixed scripts. Open the linked pages before the fight because damage values and conditions may be updated independently of this guide.

Spend the Remaining Map

Once the weakness is known, use each remaining node deliberately.

Card rewards

Take a card that answers the identified test immediately or completes a nearly finished package. Avoid speculative packages that require several more rewards when only a few floors remain.

Shops

Prioritize the bottleneck. Removal can improve access to a key answer; a potion can cover one dangerous turn; a relic can change the energy or draw budget; and a targeted card can fill the missing job. Saving gold has little value if the run cannot pass the boss.

Rest sites

Compare an upgrade with the health it risks. An upgrade that changes a cost or crosses a defensive threshold may be worth more than a small heal, but arriving without enough health to survive the opening is not a meaningful optimization.

Optional fights

An elite or extra encounter is worthwhile only if the expected reward improves the boss matchup more than the expected health loss harms it. The same route can be correct for one deck and reckless for another.

Plan Potions by Turn

Assign each held potion a possible job before entering:

Cover the opening while powers are deployed.
Survive the largest known attack.
Remove an additional target.
Accelerate damage before a dangerous phase.
Recover from the bad shuffle.

This prevents two common mistakes: using every potion at the first sign of damage, or preserving all of them until the fight is already lost.

Final Rest-Site Checklist

Before committing to the boss:

What is the most dangerous turn or condition?
What cards answer it, and how reliably are they drawn?
How many turns does setup require?
Does the deck improve during a long fight?
Can it handle additional targets or a new phase?
Which potion is assigned to which failure case?
Does an upgrade change a threshold more than resting changes survival odds?

If one answer is weak, make the final decision around that weakness. Boss preparation is not predicting every draw; it is reducing the number of draw orders that lose.

For broader construction principles, return to Deckbuilding and Scaling. For package-specific ideas, see Character Archetypes.