History of Benalia

Commanders that run History of Benalia most

Deck counts from EDHREC.

• Sidar Jabari of Zhalfir: 2,003 decks
• Dion, Bahamut's Dominant // Bahamut, Warden of Light: 1,682 decks
• Garnet, Princess of Alexandria: 1,261 decks
• Syr Gwyn, Hero of Ashvale: 753 decks
• Aryel, Knight of Windgrace: 459 decks
• Satsuki, the Living Lore: 303 decks
• Haytham Kenway: 152 decks
• Tori D'Avenant, Fury Rider: 30 decks

Often played with History of Benalia

Cards that show up in the same decks on EDHREC.

• Gallant Cavalry
• Diamond Knight
• Joust
• Call the Cavalry
• Knight of the New Coalition
• Zhalfirin Lancer
• Venerable Knight
• Inspiring Veteran
• Worthy Knight
• Belle of the Brawl

Rulings

• 2018-04-27: Once a chapter ability has triggered, the ability on the stack won’t be affected if the Saga gains or loses counters, or if it leaves the battlefield.
• 2018-04-27: A chapter ability doesn’t trigger if a lore counter is put on a Saga that already had a number of lore counters greater than or equal to that chapter’s number. For example, the third lore counter put on a Saga causes the III chapter ability to trigger, but I and II won’t trigger again.
• 2018-04-27: Once the number of lore counters on a Saga is greater than or equal to the greatest number among its chapter abilities—in the Dominaria set, this is always three—the Saga’s controller sacrifices it as soon as its chapter ability has left the stack, most likely by resolving or being countered. This state-based action doesn’t use the stack.
• 2018-04-27: If multiple chapter abilities trigger at the same time, their controller puts them on the stack in any order. If any of them require targets, those targets are chosen as you put the abilities on the stack, before any of those abilities resolve.
• 2018-04-27: The final chapter ability of History of Benalia affects only Knights you control at the time it resolves. Creatures you begin to control later in the turn or that become Knights later in the turn won’t get +2/+1.
• 2018-04-27: As a Saga enters the battlefield, its controller puts a lore counter on it. As your precombat main phase begins (immediately after your draw step), you put another lore counter on each Saga you control. Putting a lore counter on a Saga in either of these ways doesn’t use the stack.
• 2018-04-27: If counters are removed from a Saga, the appropriate chapter abilities will trigger again when the Saga receives lore counters. Removing lore counters won’t cause a previous chapter ability to trigger.
• 2018-04-27: Each symbol on the left of a Saga’s text box represents a chapter ability. A chapter ability is a triggered ability that triggers when a lore counter that is put on the Saga causes the number of lore counters on the Saga to become equal to or greater than the ability’s chapter number. Chapter abilities are put onto the stack and may be responded to.