Classic League of Legends Update 4: Graves Returns, and Riot Admits the Matchmaking System Is Broken

Hook

At 11 p.m. on September 23, I reopened Classic League of Legends, locked in Graves, and fired one shot into a mid-lane minion. The gun kicked on the old rhythm. The shot rang with the old texture. Everything was exactly as I remembered it. And that is precisely why I sat there for another forty minutes after the match ended — not to queue again, but to reread the update announcement.

The community had been demanding Classic Graves since the day the mode was announced. Riot put him into the fourth update. The interesting part is elsewhere: the thing billed as the community's most-awaited pick arrived after three updates nobody asked for.

I do not predict the future; I excavate the past and throw it in your face. But this time, the story is not Graves. It is in the two percentages Riot just published from the Council's first vote: 52.8% and 48.8%.

Context

Some groundwork is needed, because this is not a story everyone follows.

Classic League of Legends is a separate game mode built on an older build of the game, where champions are returned to their original kits from before their reworks. This is not a professional competitive server. There are no teams, no tournaments, no pro players, no rankings that affect anyone's career. It is a nostalgia product, running parallel to the main client, operated by Riot on its own update cadence. The fourth update is proof that this is a long-term content line, not a one-off experiment.

The fourth update carries three groups of changes.

The first group is champions restored to their old kits: Graves, Fizz, Nami and Nautilus. Graves is the marketing headline; Fizz, Nami and Nautilus fill out the mid and support pools. The second group is systemic: jungle respawn timers were adjusted, the Eye Item was brought back, and three new items were added. The third group is balance: Akali, Galio, Kassadin, Poppy and Shyvana were buffed; Fiora, Morgana and Twisted Fate were nerfed.

The changes were presented by David Turley, known as Phreak, a long-time Riot Games figure. He is not a coach, not a pro player, not a broadcast analyst. His role here is purely communications: explaining to players what just happened to their game.

And then there is the Council, a mechanism built to let players vote on content. Players accumulate voting power by playing the mode. The first vote has already taken place, covering match duration, snowballing, jungle respawn timers, the Eye Item and three proposed items. The next vote will let the community choose which champion Riot restores next.

Drawing on my experience following matches in this mode since its early days, I have learned one thing: Classic's pull is not the nostalgia. That feeling lasts about three games. What keeps players around is the sense that decisions about this mode are being made transparently. And that is exactly where the trouble starts.

Core, Part One: A Balance Philosophy Copied Straight From the Main Client

The balance approach in the fourth update mirrors Riot's methodology for the competitive client exactly — except it is applied to an old sandbox.

Five champions were buffed: Akali, Galio, Kassadin, Poppy and Shyvana. Three were nerfed: Fiora, Morgana and Twisted Fate. The list splits into two clear groups, and both are familiar to anyone who has read a Riot balance sheet in the past decade.

Akali and Kassadin are near-absent from matches in this mode. Poppy and Shyvana sit in the top-lane and jungle corners few players touch. Galio is a defensive pick ignored when players want fast damage. On the other side, Fiora and Morgana appear almost by default in team compositions, and Twisted Fate is a staple mid pick for the nostalgia crowd.

The methodology is identical to how Riot handles the main client: pull underrepresented picks up, push dominant picks down. The problem lies in a detail the announcement omits. No numerical magnitude was published. No percentages, no base changes, no target win rates. Players know Fiora was nerfed; they do not know by how much.

For a mode that does not put competitiveness first, withholding magnitudes is defensible by design. But it also means nobody — including those of us who write analysis — can grade the true depth of this balance pass. Any conclusion about whether Fiora has been knocked off her dominant position has to wait for win-rate and pick-rate data. That data does not exist yet.

More notable is the systemic group. Jungle respawn timers, the Eye Item and three new items are not a single champion's business. These are structural-layer changes, the kind Riot usually only ships in preseason patches on the main client. Putting them into a nostalgia mode shows Riot does not treat Classic as decoration. They are rebuilding the whole experience, not patching one champion at a time.

Restoring the old kits of Graves, Fizz, Nami and Nautilus reinforces that read. Returning a champion to a pre-rework kit means maintaining a separate code branch, split from the main client. That is real engineering cost, not marketing cost. Publishers do not maintain two code branches for fun.

Riot is not patching a nostalgia mode; it is running two products in parallel, and the old one is being resourced like a real product.

That leads to a consequence few people discuss. Once an old mode is resourced like a real product, it must meet real-product quality standards. And that is when the problems surface.

One technical point matters here: old kits are not uniformly weaker than modern ones. After years of reworks, many champions received baseline buffs and operational changes to suit a faster match pace. Returning them to their originals does not just restore a feeling; it creates a new balance board with entirely different strengths and weaknesses. Classic Graves is the clearest example: his old kit operates on a completely different logic from his modern kit, to the point where the two versions are almost separate champions. Restoring him is not flipping a switch.

This balance pass was therefore mandatory, not optional. The moment old champions return, Riot must rebalance the entire area around them. The buff and nerf list in the fourth update is a direct consequence of restoring Graves, Fizz, Nami and Nautilus, not an independent tuning pass.

Core, Part Two: The Council and Two Percentages Nobody Read Closely

This is the most important part of the fourth update, and it has nothing to do with Graves.

The Council is a governance mechanism run by the publisher. Players earn voting power by playing the mode. Riot retains final say but hands part of the content-prioritisation process to the community.

The first vote produced results on match duration and snowballing. Two percentages were published: 52.8% of participants rated match duration as appropriate, and 48.8% rated the snowballing state as stable.

Both sit below a majority threshold. This is the detail most coverage skips when it writes that the community agreed. At 52.8%, nearly half of participants did not rate match duration as appropriate. At 48.8%, more than half did not rate snowballing as stable.

That distinction is not semantics. When a publisher presents vote results as evidence that its design is accepted, calling a plurality a consensus is a framing that benefits the publisher. The underlying data says a large bloc of players remains unconvinced — and that bloc is not small.

But there is a bigger information gap. For jungle respawn timers, the Eye Item and three proposed items, the announcement presents them as passed items but gives no percentages at all. Players do not know how much support those items received.

The asymmetry is worth noticing. Two items have numbers; three do not. If the unnumbered items were overwhelmingly supported, publishing them would cost nothing and would even be a communications win. Omitting the numbers only helps in one scenario: when the figures are not flattering enough to sit beside the other two.

I am not saying Riot is lying. I am saying the presentation is selective — and in a mechanism explicitly built to empower the community, selective presentation is the one thing that must not happen.

There is one more point about the Council's power structure. Voting power accrues through playtime. That mechanism rewards the most committed cohort, and that cohort does not represent the whole community. New players, players returning after years away, players who drop in for one or two games a week — all of them have a smaller voice. Vote outcomes therefore reflect the preferences of the hardcore group, not the entire player base. When Riot says the community wants something, one question is worth asking: which community.

The next vote will let players choose the next champion to be restored. That is the real test of this mechanism, and it is verifiable. If Riot implements the outcome, the Council has value. If Riot picks something else and cites technical reasons, the Council becomes ceremony.

Contrarian: Where I Could Be Wrong, and Where Riot Contradicts Itself

I could be wrong in three places, and I will say so before anyone catches me.

First, I assume the Council is a retention tool, without proof. The playtime-linked voting loop does have the shape of an engagement mechanic, but it could equally be a low-cost way for Riot to gather priority data. The two explanations lead to opposite conclusions, and the evidence to separate them is missing.

Second, I assume withholding balance magnitudes is a bad sign. For a mode with no competitive ladder, publishing win rates may do more harm than good: it turns a nostalgia experience into a spreadsheet to be optimised. Riot is reasonable to stay quiet.

Third, I may be underestimating the durability of legacy products. Many re-releases in this industry have sustained communities for years, not months. If Classic follows that trajectory, my concern about novelty decay will not materialise.

Thirty years of waiting, and what they got was a title they dare not boast about. Nostalgia players waited for the original version of something they once loved, and their verdict will not rest on emotion — it will rest on operational quality.

But there is one place I cannot defend myself, and it comes from Riot directly.

On bots in this mode, Riot says the problem is not as serious as community feedback suggests. On the player-classification system — matchmaking — Riot admits there is a problem: new players are being placed into the wrong skill tiers.

Those two statements cannot both be fully true. If new players are dumped into the wrong skill tiers, then some of what looks like bots in Classic lobbies may actually be misclassified humans. Riot itself proposes that hypothesis when it says bot-like behaviour may stem from players unfamiliar with old kits. At the same time, Riot downplays the severity of the bot issue. You cannot say the problem is small while admitting your matchmaking is broken.

For a mode that lives on returning veterans, this is a real risk. A veteran comes back, meets a lobby full of accounts behaving strangely, and leaves. They do not come back a third time.

Classic's biggest risk is not a shortage of nostalgia content; it is matchmaking quality — the thing that decides whether players stay or leave within their first three games.

I have watched enough legacy modes to know one thing: nostalgia content sells for a month, and operational quality decides the six months after that. Graves can pull players back for a week. A broken matchmaking pool drives them away in three days.

Takeaway

The September 23 roadmap is the next test, and it will not be measured in champions restored. If that update touches player classification, Riot is addressing the right problem. If it only adds champions and items, their priority order is already visible: content that sells comes first, systems come later.

I will be watching the Council's next vote, and I will be counting how many percentages get published this time. If it is still two numbered items and three unnumbered ones, the answer is already in hand — no need to wait for the result.