Logo
Nerd Leagues
NEW! Nerd Leagues is now on iOS and Android Download on the App Store Get it on Google Play

Overlapping MTG League Seasons: How One Game Updates Multiple Scoreboards

3 min read Updated Jul 31, 2026
A single recorded MTG league game updates every active season whose dates cover it, each with its own independent standings. Here's how that fan-out works and why the same game can move two seasons by different amounts.

Overlapping MTG league seasons are supported: a league can run several seasons at once, and a single recorded game updates every active season whose dates cover it. Each season keeps its own independent scoreboard.

How overlapping MTG league seasons work

When a game is recorded into a league, every non-archived season whose date range covers the game's date gets its own ELO update for that game. Two specifics matter:

  • Matching uses the game's recorded date, not the date played. Log a game on Tuesday that you played on Saturday and only seasons covering Tuesday register it.
  • Matching is inclusive on both ends. A game on a season's start date counts; a game on its end date counts; a game one day past the end date doesn't.

Nothing in the record-game flow reports which seasons updated. Record the game, and the standings reflect it the next time you open the league page.

What overlapping seasons let you run

Overlapping MTG league seasons cover patterns a single timeline can't:

  • Monthly, quarterly, and annual scoreboards at once. A 30-day March 2026 season inside a 90-day Q1 2026 season inside a year-long 2026 League. Every game updates all three, and each crowns its own winner.
  • Playoffs nested in a regular season. A Summer 2026 season runs June 1 to August 31; a Summer Playoffs season runs August 15 to August 31. Late-summer games count toward both.
  • Themed mini-seasons. A Pre-Release Week season covering the seven days after a set drops, on top of an ongoing year-long league.

How the ELO math works across overlapping seasons

The math is identical season by season — same K-factor, same expected-score formula, same win/loss accounting. The only thing that varies is the starting ELO each player and deck brings into that season.

Because each season tracks its own scoreboard, a player sitting at 1240 in your annual season can walk into a fresh monthly season at 1000. When a game is recorded, the annual season computes the change against the annual starting ELO and the monthly season computes it against the monthly one. Both update from the same game, and the two can disagree about how much that win or loss was worth, because expected scores depend on starting ratings.

MTG League ELO has the underlying formulas. The same ones apply per season.

How archived and deleted seasons interact with overlap

Only non-archived seasons are updated, so:

  • An archived season inside a new game's date range is not updated. Its standings stay exactly as they were when you archived it.
  • Unarchiving resumes new games, but games recorded during the archived stretch are not scored retroactively. Ask an admin to run a season ELO recalculation to close that gap.
  • A deleted season is gone — past, present, and future. Later games in that range update only whatever other seasons still cover the date.

Creating and Managing MTG League Seasons covers the create, edit, archive, and delete controls.

What overlapping seasons don't do

  • No warning on overlap. Nerd Leagues doesn't check for overlapping date ranges. Two seasons with overlapping dates are created as specified.
  • No per-game opt-out. There's no way to count a game toward Q1 but not the annual season. Every active season covering the date is updated.
  • No shared K-factor budget. If three seasons cover the same date, a winner earns the full amount in each, not a third of it. Per-season ELO is a parallel scoreboard, not a slice of one pot.

Where to go next

Season Standings covers reading the per-season tabs on the league page. Recording an MTG League Game covers everything else a recorded game sets off.