Cascade resolution: the stack order most pods get wrong

TL;DR: When you cast a spell with multiple cascade triggers (like Maelstrom Wanderer's two instances), they go on the stack and you choose their order. The last one you put on the stack resolves first. That choice matters because the first cascade can flip a card that itself cascades, creating a chain before your second trigger even resolves.

The scenario most pods auto-pilot through

You tap seven mana and cast Maelstrom Wanderer. Two cascade triggers go on the stack. Most players just start flipping cards from the top of their library, resolve the first spell they hit, then flip more cards for the second cascade. The game state advances and nobody thinks twice about it.

That's wrong. Not game-breaking wrong, but procedurally wrong in a way that occasionally costs you value.

Maelstrom Wanderer

When Maelstrom Wanderer's triggered abilities go on the stack, you are making a choice about their order. The Comprehensive Rules give you that choice explicitly. The choice has gameplay implications. This article walks through what the rules actually say and why it matters.

What the Comprehensive Rules say (CR 702.85a)

Cascade is defined in CR 702.85a:

"Cascade" means "When you cast this spell, exile cards from the top of your library until you exile a nonland card whose mana value is less than this spell's mana value. You may cast that card without paying its mana cost if the resulting spell's mana value is less than this spell's mana value. Then put all cards exiled this way that weren't cast on the bottom of your library in a random order."

Each instance of cascade is a separate triggered ability. If a spell has cascade twice (printed on the card), each instance creates its own trigger. Those triggers are objects on the stack.

Stack order: CR 405 governs what happens next

When multiple triggered abilities trigger at the same time (which they do when you cast a spell with two cascade instances), CR 605.3 tells you they all trigger, then CR 405.3 tells you how to order them on the stack:

The active player puts their triggers on the stack in any order they choose. Then the non-active players do the same in turn order. Then priority passes and the stack resolves from the top down.

In a four-player Commander game where you cast Maelstrom Wanderer on your turn, you are the active player. Both cascade triggers are yours. You choose their order.

That means you pick which cascade trigger goes on the stack first and which goes on second. The one you put on second (the top of the stack) resolves first. The one you put on first (underneath the top) resolves second.

Most pods skip this step. Players just assume the triggers resolve in the order they appear on the card or in some default sequence. That's not how the stack works. The active player chooses.

Why the choice matters

Let's say you cast Maelstrom Wanderer and you choose to put cascade-trigger-A on the bottom of the stack and cascade-trigger-B on top.

Cascade-trigger-B resolves first. You exile cards from the top of your library until you hit a nonland card with mana value less than 7. Let's say you flip Bloodbraid Elf (mana value 4). You cast it without paying its mana cost. Bloodbraid Elf itself has cascade, so a new cascade trigger goes on the stack.

Bloodbraid Elf

Now the stack looks like this (top to bottom):

• Bloodbraid Elf's cascade trigger (new)
• Maelstrom Wanderer's cascade-trigger-A (still waiting)

Bloodbraid Elf's cascade resolves. You exile cards until you hit a nonland card with mana value less than 4. You cast that spell. Then, finally, Maelstrom Wanderer's cascade-trigger-A resolves and you exile more cards from the top of your library.

The key insight: the FIRST cascade you resolved (trigger-B) exiled cards and cast a spell BEFORE the second cascade (trigger-A) touched your library. If the spell you cast off trigger-B had cascade (or any other effect that manipulates your library), it affects what trigger-A sees.

Contrast this with the opposite choice. If you put cascade-trigger-A on top, it resolves first, exiles cards, casts something, and completes before trigger-B even starts. The two cascades are independent unless you choose an order that makes them interact.

The practical move: pause and choose

When you cast a double-cascade spell, take five seconds and announce your stack order out loud.

"Maelstrom Wanderer's first cascade trigger goes here, second cascade trigger goes on top."

Or just: "I'm resolving this cascade first, then that one."

The table will understand. If they don't, show them this article or CR 405.3. The rules are unambiguous. You have the choice. Making the choice explicitly avoids the situation where you flip cards, realize you wanted the other order, and have to rewind the game state because you auto-piloted through a decision point.

Most of the time the order doesn't matter. You flip two spells, you cast them, you win or you don't. But sometimes you flip Throes of Chaos off your first cascade and that creates a third cascade trigger before your second Maelstrom Wanderer cascade resolves. In that scenario the order you chose determines how deep into your library you dig before the game state stabilizes.

Throes of Chaos

Cascade chains: the reason this matters in competitive pods

In high-power or cEDH metas, cascade chains are a real line of play. Cards like Imoti, Celebrant of Bounty grant cascade to every spell you cast with mana value 6 or greater. If you cast a 7-mana spell, you get one cascade trigger from Imoti. If that 7-mana spell also has cascade printed on it (like Apex Devastator, which has cascade four times), you now have five cascade triggers on the stack.

You order all five. The first one you resolve can flip another cascade card, adding a sixth trigger before the other four resolve. The math spirals quickly.

In casual pods this matters less because most players aren't running enough cascade cards to create long chains. But even in casual pods, getting the stack order right is the difference between looking like you know the rules and looking like you're winging it.

And occasionally it's the difference between winning and losing. If your first cascade flips a tutor and you can arrange your library before your second cascade resolves, you've turned a random pair of flips into a pseudo-deterministic sequence. That's not competitive-legal tutoring (you're still exiling at random from the top), but it's more controlled than flipping blind twice.

The common misconception

The misconception is that cascade triggers resolve in the order they're printed on the card. They don't. Printed order doesn't govern stack order. The active player's choice does.

Some players think the triggers go on the stack simultaneously and resolve simultaneously. That's not how the stack works. Objects on the stack resolve one at a time, top to bottom. Multiple triggers that occur at the same time all go on the stack, but they occupy distinct positions in the stack and resolve in sequence.

Some players think "first cascade" means the first trigger you put on the stack. It doesn't. "First" in normal English means "first to resolve," which is the LAST trigger you put on the stack. This is the same LIFO (last in, first out) structure that governs every other stack interaction in Magic. Cascade doesn't get special treatment.

Now you know. And the next time someone in your pod casts Maelstrom Wanderer and just starts flipping without announcing stack order, you can pause the game, cite CR 405.3, and make them choose. It's a real choice. Not a procedural step. Not a default. A choice that sometimes changes the outcome.

Take the five seconds. Make the choice. Win more games.

---

This is a Commander Pulse evergreen. For weekly EDH data digests delivered to your inbox, sign up here.