Drum of Battle

Draft note

Treat Drum of Battle as a signal card until the surrounding deck has enough payoff. It should not be evaluated in isolation from Ironclad scaling and relic support. The right question is whether the deck can use the card on the turn it appears, not whether the finished build would love to have it later.

Support density check

If the run already has the pieces that turn Drum of Battle into a payoff, the card can move up quickly. If the deck still lacks damage, block, draw, or relic support, it may be better to take a simpler card that wins the next fight.

• Count existing enablers before calling it a build-around pick.
• Compare it against immediate damage and block needs.
• Use Ironclad build pages to decide whether the package is actually open.

Best partners

Drum of Battle is safer when Ironclad already has cards or relics that reward repeated attacks, strength scaling, exhaust cleanup, or tempo conversion. It is weaker when the deck needs one plain attack, one block card, or one upgrade to survive the next route segment.

• Pair it with Ironclad shells that already have reliable defense.
• Use it after the deck proves it can spend a setup turn without bleeding HP.
• Check Conflagration and Ironclad build pages before treating it as a build label.

Common mistake

The common mistake is treating Drum of Battle as proof that an Ironclad synergy deck is open. One payoff card is not a package. Exact card text, upgrade value, and interaction timing are needs verification, so the page should teach the support-density test first.

Evidence to collect next

The next Drum of Battle pass should capture reward context, the deck before the pick, existing enablers, the next two fights, and whether the card was playable on awkward turns. Screenshots should include current patch and upgrade text before the tier stance moves.