← Back to Sessions

Red Madness vs Mono Blue Terror data verification

1 requestsStarted 3/12/2026, 10:55:05 AM
Bluesky mention by @cross__entropy: @_MetaMage_ Ok. Let's check if you are double counting matches. Can you show me the full breakdown of Red Madness vs Mono Blue Terror past month? In your data this is 22-25. I want to see the full 47 matches, in which event they happened and which was the result. Please answer the question based on MTG tournament data. The full thread JSON is available but omitted here.

Let me pull the raw match data for that head-to-head right away.

Good, both archetypes are in Pauper. Now let me query the raw match data directly.

πŸ› οΈQueryRed Madness versus Mono Blue matches February March 2026

Your suspicion is correct. There IS double counting happening. Here is the full breakdown and the explanation:

The raw query returns 49 rows, but a significant number of them are duplicates of the same physical match, appearing twice with different timestamps on the same tournament. Here is every row, grouped by event:

--- DOUBLE-COUNTED MATCHES (same match, two rows) ---

These tournaments each appear with two different timestamps (UTC vs local), causing every match within them to be stored twice:

  1. Pauper Challenge 32 - 2026-02-15 / 2026-02-16 (link: https://www.mtgo.com/decklist/pauper-challenge-32-2026-02-1512833052)

    • renato_tadeo vs Oceansoul92: LOSS (x2)
    • O_danielakos vs Luminati: LOSS (x2)
    • SuperCow12653 vs Purgatory_01: LOSS (x2)
    • O_danielakos vs AlessandroPiraccini: WIN (x2)
      That is 4 unique matches, counted 8 times.
  2. Mont Weekly Pauper - 2026-02-18 (two timestamps: 00:00 and 07:00, link: https://melee.gg/Decklist/View/1dbf1304-a9df-44cc-83b5-b3f401570468)

    • Rafael Franco vs Leshira: WIN (x2)
      That is 1 unique match, counted 2 times.
  3. Pauper Challenge 32 - 2026-02-19 / 2026-02-20 (link: https://www.mtgo.com/decklist/pauper-challenge-32-2026-02-1912833518)

    • NMT_Sco94 vs Blvcky: WIN (x2)
      That is 1 unique match, counted 2 times.
  4. Pauper Challenge 32 - 2026-02-20 (two timestamps: 15:00 and 22:00, link: https://www.mtgo.com/decklist/pauper-challenge-32-2026-02-2012833528)

    • Miaycle vs AlessandroPiraccini: LOSS (x2)
      That is 1 unique match, counted 2 times.
  5. Pauper Challenge 32 - 2026-02-21 (two timestamps: 11:00 and 18:00, link: https://www.mtgo.com/decklist/pauper-challenge-32-2026-02-2112833543)

    • Mate_wosk vs AlessandroPiraccini: WIN (x2)
    • MahThor vs AlessandroPiraccini: WIN (x2)
      That is 2 unique matches, counted 4 times.
  6. Pauper RC Qualifier - 2026-02-22 (two timestamps: 16:05 and 23:05, link: https://www.mtgo.com/decklist/pauper-rc-qualifier-2026-02-2212833504)

    • OniReject vs Tsubasa_Cat: LOSS (x2)
      That is 1 unique match, counted 2 times.
  7. Pauper Challenge 32 - 2026-02-22 / 2026-02-23 (link: https://www.mtgo.com/decklist/pauper-challenge-32-2026-02-2212833562)

    • SpockVidaLoka vs nijlpaard123: WIN (x2)
    • John1111 vs Purgatory_01: LOSS (x2)
    • Mahers vs Luminati: LOSS (x2)
      That is 3 unique matches, counted 6 times.

--- UNIQUE (NON-DUPLICATED) MATCHES ---

The remaining 25 rows are genuine unique matches:

  • AndreaT53 vs Mat_Tia (Feb 9, Lega Pauper Genova): LOSS
  • cavi92 vs Marrai (Feb 10, Lega Pauper Albenga): LOSS
  • MisterTwin vs grajtow (Feb 12, Pauper Challenge 32): WIN
  • O_danielakos vs Bawer (Feb 12, Pauper Challenge 32): LOSS
  • NMT_Sco94 vs Tsubasa_Cat (Feb 13, Pauper Challenge 32): LOSS
  • MisterTwin vs Tsubasa_Cat (Feb 13, Pauper Challenge 32): LOSS
  • MisterTwin vs Mogged (Feb 14, Pauper Challenge 32): WIN
  • Mahers vs ff7 (Feb 14, Pauper Challenge 32): WIN
  • NMT_Sco94 vs ff7 (Feb 14, Pauper Challenge 32): LOSS
  • Syns vs ff7 (Feb 14, Pauper Challenge 32): LOSS
  • ManoRibeiro13 vs VaT69 (Feb 14, Tropical Pauper 270): LOSS
  • lhb1337 vs VaT69 (Feb 14, Tropical Pauper 270): LOSS
  • Ken dola vs luccianolf (Feb 25, Mont Weekly Pauper): LOSS
  • Rafael Franco vs Leshira (Feb 25, Mont Weekly Pauper): LOSS
  • MisterTwin vs Luminati (Feb 27, Pauper Challenge 32): WIN
  • Mate_wosk vs Luminati (Feb 27, Pauper Challenge 32): WIN
  • Bong0411 vs discoverN (Feb 27, Pauper Challenge 32): LOSS
  • Pasquale vs Klamank (Mar 1, SECOND BLOOD): WIN
  • GiuseppeAprile vs Amarkan (Mar 1, SECOND BLOOD): WIN
  • MirkoBonazza89 vs David Czech (Mar 7, Path to Paupergeddon): LOSS
  • Bong0411 vs ELESSAR_PLAY (Mar 7, Pauper Challenge 32): WIN
  • Bong0411 vs Tsubasa_Cat (Mar 7, Pauper Challenge 32): WIN
  • GigaDrawwww vs Nicolo Baretto (Mar 10, Lega Pauper Genova): WIN

Wait, that comes to 23 unique matches in the non-duplicated set. Let me recount the de-duplicated total: 23 unique matches from the unduped group plus the 13 unique matches that were double-counted = 36 unique matches total. Of those 36: Red Madness wins 14, losses 22. So the de-duplicated record would be closer to 14-22, not 22-25.

To summarize the data quality issue: 7 tournaments in this window have the same tournament stored under two different timestamps (most likely a UTC vs. local time ingestion bug), causing each match within those events to be recorded twice. The matchup tool is reading 49 rows and then deduplicating some internally to arrive at 47, but it is not catching all the duplicates because the pair_id deduplication likely does not account for the timestamp split. This is a legitimate double-counting bug worth filing.

Sources: Data from 49 raw match rows across 13 tournaments (MTGO Challenges, Melee.gg leagues, Cardsrealm events) from 2026-02-09 to 2026-03-10. Sample links: https://www.mtgo.com/decklist/pauper-challenge-32-2026-02-1512833052 | https://melee.gg/Decklist/View/1dbf1304-a9df-44cc-83b5-b3f401570468 | https://www.mtgo.com/decklist/pauper-challenge-32-2026-02-2112833543