Combo and win condition theory

Storm count in EDH: discipline for any deck, not just combo

Tracking the number of spells you cast each turn keeps you honest. Here's why.

TL;DR: Storm count (CR 702.40) is the number of spells cast this turn. Combo decks track it to win. Every other deck should track it too — it tells you whether you're cantripping toward a combo or grinding incremental value. Knowing your average storm count per turn reveals what your deck actually does, not what you think it does.

What storm count is

Comprehensive Rules 702.40a defines storm: "Storm is a triggered ability that functions on the stack. 'Storm' means 'When you cast this spell, copy it for each other spell that was cast before it this turn. If the spell has any targets, you may choose new targets for any of the copies.'"

The key phrase is "for each other spell that was cast before it this turn." That count — the number of spells anyone cast this turn before you cast your storm spell — is storm count. It resets at end of turn. It counts spells from all players. It counts spells that resolved, spells that were countered, and spells still on the stack.

Tendrils of Agony

Tendrils of Agony cares about storm count because it drains for 2 life times the number of copies. If storm count is 9 when you cast Tendrils, you get 10 copies (the original plus 9 storm triggers), draining for 20 life total. At a 4-player table that's lethal to one player, close to lethal for two.

But storm count doesn't only matter for cards with the storm keyword. It matters any time you need to know "how many spells did I cast this turn." The number tells you something about your deck's actual game plan.

Scenario 1: Rashmi and the spell-per-turn engine

Rashmi, Eternities Crafter

Rashmi, Eternities Crafter triggers whenever you cast your first spell each turn. During an opponent's turn that trigger is powerful — you get a free card or you cast something off the top. The trigger condition is "your first spell each turn." That's storm count = 1 on each opponent's turn.

A well-tuned Rashmi deck casts exactly one spell per opponent turn cycle. Storm count stays at 1 during each player's turn until it gets back to you. Then on your turn you cast 3-5 spells: a land, a ramp spell, a cantrip, a value piece, maybe a counterspell if someone tries to interact.

Your storm count on your own turn might hit 4 or 5. That's the engine. You're not comboing — you're chaining spells to generate card advantage, leave up interaction, and trigger Rashmi on the next go-around.

If your average storm count on your own turn is 7+, you're not playing a Rashmi value deck. You're playing a storm deck with Rashmi as the card-advantage engine. That's fine — but you should know it. It changes your mulligan decisions. It changes how you sequence your spells. It changes whether you hold up mana for interaction or go all-in on casting as many spells as possible.

Tracking storm count taught me that my Rashmi deck was actually a Aetherflux Reservoir deck. I thought I was grinding value. The numbers said I was comboing on turn 6-7 with high spell velocity. I added more counterspells and more interaction — storm count dropped to 3-4 per turn, win rate stayed the same, games got more interesting.

Aetherflux Reservoir

Scenario 2: Aristocrats and the storm-trigger pattern

Blood Artist triggers on every creature death. "Whenever Blood Artist or another creature dies, target player loses 1 life and you gain 1 life." In an aristocrats deck you're sacrificing 5-10 creatures per turn when the engine is online. Each sacrifice is not a spell — it's an activated ability. Storm count doesn't move.

But the spells you cast to enable those sacrifices do count. You cast a creature. Storm count goes to 1. You sacrifice it to Viscera Seer. Storm count stays at 1. You cast Zulaport Cutthroat. Storm count goes to 2. You cast Phyrexian Altar. Storm count goes to 3. You sacrifice Zulaport to Altar for mana. Storm count stays at 3. You cast Pitiless Plunderer with that mana. Storm count goes to 4.

The storm count tracks how many pieces you assembled this turn. When storm count is 4-5 in an aristocrats deck, you're probably about to loop. When storm count is 1-2, you're setting up.

The discipline: if your storm count in an aristocrats deck regularly hits 6-8, you're running too many cantrips and not enough sacrifice outlets. The spells should be creatures and enablers. The triggers should be doing the work. High storm count in aristocrats means you're churning through your deck looking for pieces — which means your density is wrong or your tutors are missing.

I ran an aristocrats list for six months before I started tracking storm count per turn. Average was 6.5. I was casting Village Rites, Deadly Dispute, Night's Whisper, and Sign in Blood to find my combo pieces. Storm count told me the problem: I had 12 draw spells and 8 sacrifice outlets. I should have had 4 draw spells and 16 outlets. I flipped the ratio. Storm count dropped to 3.2 per turn. Win rate went up.

Scenario 3: Control and the one-spell discipline

Control decks want low storm count. The ideal control turn is: pass with mana up, counter one spell, pass again. Storm count on your turn: 0. Storm count on an opponent's turn: 1 (your counterspell).

When your control deck's storm count starts creeping up — 3 spells on your turn, 2 on an opponent's turn — you're not playing control anymore. You're playing midrange. That's not a value judgment. Midrange is fine. But if you think you're playing control and your average storm count is 4+ per turn cycle, your deck is lying to you.

The storm-count test for control:

Storm count 0-1 per turn: you're controlling the game. You're answering threats. You're not developing your own board.
Storm count 2-3 per turn: you're playing midrange. You're answering some threats and deploying some threats.
Storm count 4+ per turn: you're playing combo or value engine. Control is not your primary game plan.

I thought I was playing a control deck with Talrand, Sky Summoner. Storm count average was 5 per turn. Every cantrip made a token. Every counterspell made a token. Every bounce spell made a token. I was storming off with 2/2 fliers. That's not control — that's a go-wide token strategy with counterspells as a secondary plan.

I rebuilt the deck with storm count discipline in mind. Cut half the cantrips. Added more board wipes. Added more single-target removal that didn't care about storm count. New average: 1.8 spells per turn. Games took longer. I won fewer games but felt more in control of the ones I did win.

The meta-point: storm count reveals your deck's real identity

You build a deck with an idea in mind. "This is a Rashmi value deck." "This is an aristocrats combo deck." "This is a control deck." Then you play 10 games and track storm count per turn. The number tells you what the deck actually does.

If your Rashmi deck averages storm count 7, it's a storm deck. If your aristocrats deck averages storm count 8, it's a cantrip deck. If your control deck averages storm count 5, it's a midrange deck.

Tracking storm count is how I learned which of my decks were actually combo decks in disguise. I had three "value" decks that all played the same: cast 6-8 spells per turn starting on turn 5, try to close by turn 8. They felt different because the cards were different colors and the commanders were different archetypes. The storm count was the same. They were all combo decks.

The discipline: pick one of your decks. Play five games. Track how many spells you cast each turn (including opponents' turns if you have instant-speed interaction). Average those numbers. If the average is 5+, you're playing a high-velocity deck — combo, storm, or value-engine. If the average is 2-3, you're playing midrange. If the average is 0-2, you're playing control or stax.

Then ask: is that what I thought I was playing? If yes — great, your perception matches reality. If no — you have a choice. Rebuild the deck to match your idea, or keep the deck and update your idea.

Storm count doesn't judge. It just counts. But the count tells the truth.

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