The intervening 'if' clause: how Aetherflux Reservoir actually wins (and loses)

TL;DR: Aetherflux Reservoir's "50 or more life" check happens twice — once when the trigger goes on the stack, and again when it resolves. If an opponent drops your life total below 50 in response, the trigger fizzles and you don't get to kill anyone. This is Comprehensive Rules 603.4, the intervening 'if' clause, and most pods get it wrong the first time they see it.

---

The moment the pod goes quiet

You're at 52 life. You've cast your 50th spell this turn. Aetherflux Reservoir's triggered ability goes on the stack: "Whenever you cast a spell, you gain 1 life for each spell you've cast this turn. When you gain life this way, if you have at least 50 life, you may pay 50 life. If you do, Aetherflux Reservoir deals 50 damage to any target."

You announce the trigger. You name the player you're killing. The table reaches for their cards.

Then someone plays Toxic Deluge for X=12. Your life total drops to 40.

You argue that the trigger already happened. They argue it hasn't resolved yet. The table pulls out phones. Someone types "aetherflux ruling" into Google. Five minutes pass.

Here's what actually happens.

Aetherflux Reservoir

Comprehensive Rules 603.4: the intervening 'if'

The Comprehensive Rules have a specific mechanism for this situation. CR 603.4 reads:

"A triggered ability may read 'When/Whenever/At [trigger event], if [condition], [effect].' When the trigger event occurs, the ability checks whether the stated condition is true. The ability triggers only if it is; otherwise it does nothing. If the ability triggers, it checks the stated condition again as it resolves. If the condition isn't true at that time, the ability is removed from the stack and does nothing."

That's the intervening 'if' clause. It creates a two-gate system: the condition must be true when the trigger would go on the stack, AND the condition must be true again when the trigger resolves.

Aetherflux Reservoir has this structure. The trigger event is "you gain life this way" (from casting a spell). The intervening 'if' is "if you have at least 50 life". The effect is "you may pay 50 life and deal 50 damage".

When you cast your 50th spell and gain life, the game checks: do you have 50+ life? If yes, the trigger goes on the stack. If no, nothing happens.

When the trigger resolves, the game checks AGAIN: do you still have 50+ life? If yes, you may pay and deal damage. If no, the trigger is removed from the stack. It does nothing. You don't get the option to pay. The target doesn't take damage.

That's why Toxic Deluge kills the combo. The first check passed (you had 52 life when you gained life from the spell). The second check failed (you had 40 life when the trigger tried to resolve). The trigger fizzled.

How to spot an intervening 'if'

Not every 'if' in a triggered ability is an intervening 'if'. The structure matters.

Intervening 'if' structure: "When/Whenever/At [trigger event], if [condition], [effect]."

The 'if' comes immediately after the trigger event, before the effect. The condition is checked twice.

Non-intervening 'if' structure: "When/Whenever/At [trigger event], [effect] if [condition]."

The 'if' comes after the effect starts. It's part of the effect itself, not a gate on whether the trigger goes on the stack. It's checked once, during resolution.

Example of a NON-intervening 'if': "When Sengir Vampire deals combat damage to a creature, destroy that creature if it was dealt damage this turn." The 'if' is inside the effect. The trigger always goes on the stack when Sengir deals combat damage to a creature. The condition ("was it dealt damage this turn") is only checked during resolution.

Aetherflux Reservoir has the intervening structure. "When you gain life this way, if you have at least 50 life" — the 'if' comes between the trigger event and the effect. Two checks.

Toxic Deluge

Three more examples from the format

The intervening 'if' pattern shows up on dozens of cards. Most players learn it the hard way. Here are three common ones.

Sphinx's Tutelage

Sphinx's Tutelage

"Whenever you draw a card, target opponent mills two cards. If two nonland cards that share a color were milled this way, repeat this process."

The intervening 'if' here is subtle. It's in the second sentence, not the first. The repeat effect has an 'if' clause: "if two nonland cards that share a color were milled this way". That's checked when the repeat trigger would go on the stack, and again when it resolves.

Practical scenario: you draw a card. Sphinx's Tutelage triggers. You mill two cards from an opponent (Island and Sol Ring — one blue nonland, one colorless nonland). No shared color. The repeat trigger doesn't go on the stack at all. The 'if' failed the first check.

If you HAD milled two blue cards, the repeat trigger would go on the stack. But if someone exiled Sphinx's Tutelage in response (with Generous Gift, Chaos Warp, whatever), the repeat trigger would check again on resolution: "was this process done by Sphinx's Tutelage?" No, because Sphinx's Tutelage no longer exists. The trigger fizzles.

Approach of the Second Sun

"If this spell was cast from your hand and you've cast another spell named Approach of the Second Sun this game, you win the game. Otherwise, put Approach of the Second Sun into its owner's library seventh from the top and you gain 7 life."

This one tricks people because the 'if' is at the beginning of the effect, not obviously intervening. But it is. The trigger event is "this spell resolves". The intervening 'if' is "if this spell was cast from your hand and you've cast another Approach this game". The effect is "you win the game".

When Approach resolves, the game checks: was this cast from your hand? Have you cast another one this game? If yes to both, you win. If no to either, you don't win (you get the library effect instead).

The trick: if someone exiles Approach from the stack with Summary Dismissal or makes you draw it with Notion Thief before it resolves, the "cast from your hand" condition can't be true anymore because the spell never finished resolving from the hand zone. Most pods don't catch this. The intervening 'if' does.

Why pods get this wrong

The intuition is: "the trigger happened, so the effect should happen." That's how most game mechanics work. If you declare attackers, those creatures are attacking. If you cast a spell, that spell is on the stack. Cause leads to effect.

Intervening 'if' clauses break that intuition. The trigger goes on the stack, but the effect is still conditional. The stack presence doesn't guarantee resolution.

The other reason pods get it wrong: they confuse "the trigger went on the stack" with "the trigger already resolved". If you have 52 life when Aetherflux's trigger goes on the stack, it FEELS like the 50-damage option is already locked in. The visual of announcing "I'm killing you" reinforces that feeling.

But the stack is a data structure, not a timeline. Nothing on the stack has happened yet. Everything on the stack is still conditional on the game state when it tries to resolve. Intervening 'if' clauses make that conditionality explicit.

The practical takeaway

When you're about to win with a combo that has an intervening 'if' clause, and your opponents are reaching for interaction, the question is: can they change the condition before your trigger resolves?

For Aetherflux Reservoir: can they drop your life total below 50? If yes, your trigger fizzles.

For Approach of the Second Sun: can they exile the spell from the stack, or change the zone it was cast from? If yes, you don't win.

For Sphinx's Tutelage: can they remove Sphinx's Tutelage before the repeat trigger resolves? If yes, the repeat fizzles.

The inverse is also true. When you're the one STOPPING the combo, don't let the combo player convince you that "the trigger already went off" so your interaction is too late. If it's still on the stack, and the card has an intervening 'if', you can change the condition and fizzle the trigger.

This comes up most often with Aetherflux Reservoir because the life-total condition is so easy to interact with. Any damage spell, any life-loss effect, any Toxic Deluge. If it resolves before Aetherflux's trigger does, and it drops the caster below 50 life, the combo is dead.

The next time someone at your table casts their 50th spell at 52 life and announces they're killing you with Aetherflux Reservoir, and you have a Lightning Bolt in hand, you know what to do. Point them to CR 603.4. Show them the math: 52 minus 3 is 49. The trigger checks twice. The second check fails. The combo fizzles.

And then you untap.

---

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