Overlapping MTG League Seasons: How One Game Updates Multiple Scoreboards

Overlapping MTG league seasons are a feature, not an accident. Nerd Leagues lets you run multiple seasons at once inside the same league, and a single recorded game will update every active season whose dates cover it — independently, with each season tracking its own scoreboard. This article is for commissioners who want to understand exactly what happens when seasons overlap.

How overlapping MTG league seasons actually work

Overlapping MTG league seasons work by running the season update logic in a loop, once per game record. When a game gets logged into a league, the system pulls the game's recorded date and asks the database: which non-archived seasons in this league have a date range that covers this date? Every season that answers "I do" gets its own independent ELO update for that game.

Two specifics matter here:

• Date matching uses the game's recorded date, not the date played. If you log a game on Tuesday that you actually played on Saturday, only seasons whose window covers Tuesday will register it.
• Date matching is inclusive on both ends. A game on a season's start date counts; a game on a season's end date counts; a game one day past the end date doesn't.

There's no UI confirmation telling you which seasons a game just updated. The work is silent — record the game, and any season that should have caught it already did.

Why you'd want overlapping MTG league seasons in the first place

Overlapping MTG league seasons unlock a few patterns that a single timeline can't:

• Monthly + quarterly + annual scoreboards. Run a 30-day "March 2026" season inside a 90-day "Q1 2026" season inside a 365-day "2026 League" season. Every game updates all three; you crown three different winners on three different cadences without re-recording anything.
• 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, so the regular season finishes on the same games that the playoffs scoreboard fights over.
• Themed mini-seasons. A "Pre-Release Week" season for the seven days following a new set drop, sitting on top of an ongoing year-long league. Players still gain (or lose) ELO in the main league, and a parallel mini-leaderboard rewards whoever showed up that week.
• A/B-testing house rules. Run a "No Sol Ring" season for a month alongside the regular season; if you tag those games into the experimental season's window only, you can compare standings between the two without splitting your league.

How the ELO math works across overlapping seasons

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

That distinction matters. Each season tracks its own scoreboard, so a player who has been crushing your "2026 League" for three months might walk into a fresh "March 2026" season at the default rating of 1000, even though their annual-season ELO is sitting at 1240. When a game gets recorded:

• The annual season computes the change against the player's annual-season starting ELO.
• The monthly season computes the change against the player's monthly-season starting ELO.
• Both updates land on the same database commit, but they can disagree about how much ELO a win or loss is worth, because expected scores depend on starting ratings.

If you want the underlying math, see MTG League ELO: How Per-League Ratings and Standings Work. The same formulas apply per season.

How archived and deleted seasons interact with overlap

Overlapping MTG league seasons respect the archive flag. The query that picks active seasons explicitly filters out archived ones, so:

• An archived season inside the date range of a new game does not get updated. Its standings stay frozen exactly as they were when you archived it, even if a brand-new game was played the day after.
• An unarchived season starts catching new games again, but games that were recorded while it was archived are not retroactively scored. If you need clean standings after a long archive break, ask an admin to run a season ELO recalculation.
• A deleted season is gone — past, present, and future. Future games inside that range only update whatever other seasons still cover the date.

For the create / edit / archive / delete walkthrough itself, see Creating and Managing MTG League Seasons.

What overlapping seasons don't do

A few things to set expectations:

• There's no warning when you create overlapping seasons. Nerd Leagues doesn't try to detect intent; if you set up two seasons with overlapping dates, the system assumes you meant it.
• There's no per-game opt-out. You can't tell a single game "count toward Q1 but not the annual season" — the date-range loop catches every active season unconditionally.
• There's no shared K-factor budget. If three seasons cover the same date, a winner doesn't earn ⅓ of the usual ELO in each — they earn the full amount in each, independently. Per-season ELO is a parallel scoreboard, not a slice of a single pot.

Where to go next

Once your seasons are set up the way you want them, every league game you record will fan out automatically. To see what other side effects a recorded game triggers — Discord notifications, email alerts, per-league and per-deck ELO updates — see Recording an MTG League Game. The next sibling article in this category covers the per-season standings UI on the public league page; it slots in as a cross-link once published.