Source: GameRiv. Verified against multiple sources; datamines and reports are labelled as such, not stated as fact.
Riot Shut the Data Pipe One Day Before Launch
Match history for the new mode never reaches the public API, and Riot asked the developer community to leave it alone.
Riot has decided that one of its live modes plays better with no stat page attached to it.
On July 28, 2026 at 15:47 UTC, the Riot Games Developer Relations account posted that League Classic match history data won’t be available through the Riot API, and asked the third-party developer community not to aggregate or display League Classic data to users in any form. Riot framed the reason as preserving the spirit of the mode.
There is one carve-out, and it is the interesting part. League Classic is supported as a valid map type in Riot’s Tournament API, so community-led Classic tournaments can still be created and managed. Organized competition keeps its data. The stat-site layer that sits between a normal game and a tournament doesn’t get any.
That post did not go quietly. It drew roughly 979,000 views, 5,447 likes and 112 replies when we checked on July 29, 2026, which is enormous for a developer relations note about an API.
League Classic went live the next day, July 29, 2026, alongside Patch 26.15. It rebuilds Season 3-era kits, old runes and masteries and retired items around a 60-champion roster, and it runs natively inside the existing Riot Client instead of shipping as a separate download.
Look at that rune page editor for a second. The old rune shop runs down the left, eight page slots sit across the top, and a live statistics readout tallies critical damage, armor and cooldown reduction while you build. Optimization was never absent from Season 3.
What Riot just decided is where that optimization is allowed to live. Inside the client, on your own page, is fine. On a leaderboard somebody else runs is not.
The cinematic even stops on the mastery screen, Offense red, Defense blue, Utility green, every slot unspent. A nostalgia film that pauses on a spreadsheet tells you what people are actually coming back for.
The Carve-Out
Riot blocked the public data and kept the tournament pipe open, which is a choice about who gets numbers.
Read the two halves together and it stops looking like an oversight. Riot closed the public data pipe on League Classic and deliberately kept the Tournament API open for it, which sorts the audience into people running a bracket and everyone else.
The enforcement half is softer than the technical half. Riot asked. A scraper does not need an API, and Riot knows that, so whoever aggregates League Classic anyway becomes the test of whether asking is enough.
- Riot Games Developer Relations posted the data policy on X on July 28, 2026 at 15:47 UTC.
- The post states League Classic match history data will not be available via the Riot API.
- Riot asked that League Classic data not be aggregated or displayed to users in any form.
- League Classic is supported as a valid map type in Riot’s Tournament API for community-led tournaments.
- The post had roughly 979,000 views, 5,447 likes and 112 replies when checked on July 29, 2026.
- League Classic launched July 29, 2026 alongside Patch 26.15.
- League Classic rebuilds Season 3-era kits, old runes and masteries and retired items with a 60-champion roster, inside the existing Riot Client.
- Riot published the launch cinematic Welcome Back, Summoners on the League of Legends YouTube channel on July 29, 2026.
- Brian Holinka, an eleven-year World of Warcraft combat and PvP designer, joined the Riot MMO as Principal Game Designer in June 2026.
What This Means for the Riot MMO
Riot made a live call about who gets performance numbers, and the MMO version of that call is much bigger.
The loudest complaint about the modern MMO is that external data solves the game before you get to play it. Parse sites rank your raid night afterwards, and a gear-score check at the group finder decides whether you get a raid night at all.
Riot has never had to answer that question for an MMO. It just answered a much smaller version of it in public, on a live product, and it chose to withhold the data layer rather than watch a mode get optimized flat in its first week.
Whether that instinct survives contact with a real MMO is the thing to watch. An MMO’s data policy gets decided at the API long before it gets decided in a design doc.
An MMO’s data policy gets decided at the API long before it gets decided in a design doc.
The company making that call is the same one that hired Brian Holinka in June 2026 as Principal Game Designer on the Runeterra MMO, after eleven years designing World of Warcraft combat and PvP. That is the exact discipline where third-party data culture is the defining social problem.
Riot has not put a date on the MMO and did not do so here. Our earlier read of what its job listings imply is in Decoding Riot’s MMO: Job Postings Hint at a 2029 Release, and nothing in this week’s news moves it.
- Riot has now set a precedent that it will withhold match data from its own API when that data would undermine how a mode feels to play.
- The MMO version of this question is not tier lists, it is raid parses and gear checks at the group-finder door.
- Riot kept the Tournament API open, which hints at the split it prefers: organized competition gets data, the ranked-adjacent social layer does not.
- Riot asked rather than only blocked, so enforcement is partly social and the policy will be tested by whoever scrapes around it.
- Holinka joined in June 2026 from eleven years of WoW combat and PvP design, where third-party data culture is the defining social problem.
| Data policy | League Classic (live now) | The Riot MMO (unannounced) |
|---|---|---|
| Match history in the public API | Not available | Not revealed |
| Third-party aggregation | Riot asked developers not to, in any form | Not revealed |
| Organized competition | Supported as a map type in the Tournament API | Not revealed |
| Scope | Season 3-era League, 60 champions, inside the Riot Client | Set in Runeterra. Everything else is unrevealed. |
Classic modes are the other half of this argument. Riot is rebuilding the version of League that people remember rather than the one they queue into, which we wrote up when the rewind was announced in Riot Is Rewinding League to Season 3. The reason the bet keeps paying is the one League Classic Is Coming and WoW Classic Will Not Die laid out: players keep picking the build of a game that still felt unsolved.
A mode with no public data is unsolvable on purpose for a while. That is a small, cheap experiment for a MOBA. For an MMO, where the data culture arrives with the genre, it would be a founding decision.
Your Take
Should the Riot MMO block third-party sites from aggregating your raid and PvP performance data?
The next real signal is whoever tries to aggregate League Classic anyway, and what Riot does about it.
Reported from GameRiv and corroborating coverage. The MMO read is ours and clearly speculative. Analysis by RuneGrove.
