Saga and Battle Card Types Explained
Sagas and Battles are two of Magic: The Gathering's most structurally unconventional card types — each one bends the normal rules of permanents in ways that reward players who understand their specific timing and mechanical quirks. Sagas arrived in the Dominaria set (2018) and have appeared in dozens of printings since, while Battles debuted with March of the Machine (2023) as a genuinely new card type for the first time in years. Knowing how each one enters, progresses, and leaves the battlefield is essential reading for anyone exploring the full scope of Magic: The Gathering card types and subtypes.
Definition and scope
A Saga is an enchantment with a subtype of Saga. Its card frame is laid out vertically in chapters — typically 3, though some Sagas have 2 or 4 — each labeled with a Roman numeral (I, II, III). The text box is divided into horizontal bands, one per chapter, with each band describing an ability that triggers when that chapter is reached.
A Battle is its own card type entirely, currently with one subtype: Siege. Battles entered the game with a specific mechanical identity: they are the first card type that enters the battlefield under one player's control but can be attacked by that same player's creatures — a structural inversion of normal combat logic.
Both types share one key structural feature: they carry counters that track their progression toward a terminal state. For Sagas, those are lore counters. For Battles, they are defense counters. Reaching zero (for Battles) or exhausting all chapters (for Sagas) triggers a transformation or removal effect.
How it works
Sagas follow a precise sequence governed by Magic's Comprehensive Rules (specifically rules 714.1 through 714.4):
- When a lore counter is added that meets or exceeds the final chapter number, the Saga's last ability triggers, and then the Saga is sacrificed as a state-based action after that final ability resolves.
The result is a guaranteed three-turn (or N-turn) story arc that can't be removed by simply waiting it out — if the Saga resolves on the battlefield, the player will get at least Chapter I.
Battles (Siege subtype) work differently. When a Battle enters the battlefield, the caster chooses an opponent as its "protector." That opponent effectively defends the Battle. The controller can then attack the Battle with their own creatures — treating it like an opponent for combat purposes — while the protector may block those attacks with their creatures.
Defense counters start at a number printed in the lower right of the card (common values are 6 through 10). Each point of damage dealt to the Battle removes one defense counter. When the last defense counter is removed, the Battle is exiled and transforms into a powerful spell or permanent — typically a creature or planeswalker — that enters the battlefield or resolves under the original controller's control.
For a deeper look at how combat targeting and attacker declaration interact with Battles, the combat phase breakdown covers the relevant priority windows in detail.
Common scenarios
Sagas in practice most often function as value engines across multiple turns. The Saga The Eldest Reborn (from Dominaria) mills opponents, forces discards, and then reanimates a creature from any graveyard across its three chapters — a mini-game that rewards the controller for keeping the Saga alive, but doesn't actually require it. Even if an opponent destroys the Saga on Turn 2 of the game, Chapter I has already resolved.
Battles most commonly appear in midrange and control builds where the controlling player has creature density to attack them efficiently. The Siege Battle Invasion of Ikoria — one of the earlier printed examples — searches for a non-Human creature, then transforms into Zilortha, Apex of Ikoria, a 8/8 with trample. The defense counter total (6 for that card) determines how quickly the payoff is accessible.
A critical distinction worth flagging: Battles are vulnerable to removal spells the same as any permanent. An opponent can simply cast Destroy the Heretical or any enchantment removal on a Saga, or direct damage removal at a Battle, before the controller benefits. The Saga's "you get at least Chapter I" guarantee does not apply if the Saga is countered on the stack.
Decision boundaries
The fork in decision-making between these two types follows a clear pattern:
- Use a Saga when incremental, guaranteed value across multiple turns is the goal. The automatic progression removes dependence on additional resources after casting.
- Use a Battle when the transformed backside is the primary payoff and the player has the board presence to remove defense counters reliably within 2–3 combat steps.
- Don't cast a Battle into an empty board. With no attacking creatures available, defense counters will never decrease, and the card simply sits inert — protected by an opponent who has no incentive to attack it.
- Sacing a Saga early is sometimes correct. Proliferate effects (which add counters to permanents that already have them) can accelerate a Saga to its final chapter in a single turn, burning through all chapters faster than the natural one-per-turn pace.
The stack and priority rules govern both Saga chapter triggers and Battle transformation events — both go on the stack as triggered abilities, giving opponents a window to respond before resolution. That window is narrow but real, and experienced players account for it in threat assessment. More on evaluating those windows is covered in the threat assessment and removal section of this reference.