🛠 The Tools ⚖ The Tribunal 📋 Run Sheet 📊 The Data

The Data

Run your own numbers. This is the same audited dataset the whole site is built from — every custom, ranked and quick-play game we've harvested since Feb 2025. Download it, hand it to Claude (or Excel, or Python), and check our math. If you find something we got wrong, the record is open.

Downloads

data/games.csv· one row per player per game · the file most questions need

Deduped and analysis-ready: date, mode, map, player, primary hero + role, result, K/D/A, damage, healing, MVP/SVP. Humans only, best source per game (full lobby detail where we have it, feed otherwise).

data/rivals.db· full SQLite database · the power tool

Everything, raw: matches, match_players (incl. bots), hero_lines (per-hero playtime within each game), rank_seasons, players. Claude Code and Claude desktop can query SQLite directly.

data/rank_seasons.csv· per-season peak ranks per account

Every account's rank arc across seasons (peak tier + rank score). Cross-platform ranks are separate ladders — compare with care.

The rules that keep the numbers honest

Bots are excluded from all player stats (is_bot=1 rows exist in the DB — filter them, or use games.csv which already did).
Draws are draws. Win rate = wins ÷ (wins + losses + draws) on this site. Count them — a prior version of our own numbers was ~7 points wrong from this alone.
Dedupe by source. In the raw DB most games have TWO rows per player (source='lobby' and source='feed'). Lobby is authoritative (full stats); feed only for kills/deaths/result. Never sum across both — games.csv has already picked one per game.
Primary hero = most playtime that game (from hero_lines), never the hero someone ended on. Feed-only games fall back to the first hero listed.
Feed-only games (newest nights until the mirror catches up) have result/K/D but no damage/heal detail — blank cells are missing data, not zeros.
Custom games = mode='custom-game'. One free-for-all night exists — exclude it from team win rates.
Win rate ≠ skill. Teams are deliberately balanced every week, so raw win rates carry teammate bias — that's why the site rates skill with Elo and four lenses, not win%.

Hand it to Claude — copy this first

Paste this prompt with the CSV (or point Claude Code at the URLs) and it inherits our conventions instead of re-learning our old bugs:

I'm analyzing my friend group's Marvel Rivals data from marvelgooners.com/data/ (games.csv; full SQLite at rivals.db).
Rules the numbers must follow:
- One row per player per game (already deduped). mode='custom-game' = our Friday customs; 'competitive' = solo ranked; exclude other modes unless asked.
- Win rate = wins / (wins+losses+draws). Draws count in the denominator.
- Blank damage/healing = missing lobby detail (newest games), NOT zero — exclude those games from damage/heal averages.
- primary_hero is playtime-based. hero_role: Tank / DPS / Healer.
- Win rate is a TEAM outcome (teams are re-balanced weekly to be fair) — don't present it as individual skill without saying so.
- Cross-platform ranked ladders aren't comparable (PC and console queue separately).
Sanity anchors to verify your load: ~600+ custom games, ~11 tracked players, record runs Feb 2025 → present.

Good first questions

"What's my win rate by hero, minimum 10 games, customs only?"
"Which map do I win most on, and does it depend on my role?"
"Build my form curve — rolling 30-game win rate over time."
"When X and Y are on the same team, who else being there changes the result most?"
"Re-derive the site's tank tier list and tell me if Cap is really 3rd."

Data regenerates with every site update — same pipeline, same audits. Fine print: this is our private lobby's harvested record; be chill with it. Receipts live at marvelgooners.com.