Classic League of Legends Update 4: Graves Returns and Ballots That Never Reached a Majority
**Câu trả lời cốt lõi:** Bản cập nhật thứ tư của Classic League of Legends phục dựng bộ kỹ năng Graves cổ điển, bổ sung Fizz, Nami, Nautilus, tăng sức mạnh Akali, Galio, Kassadin, Poppy, Shyvana và giảm sức mạnh Fiora, Morgana, Twisted Fate; Hội đồng người chơi bỏ phiếu định hướng nội dung tiếp theo. **Dữ kiện chính:** - Riot Games công bố bản cập nhật 4 của Classic League of Legends, đưa Graves cổ điển trở lại cùng Fizz, Nami, Nautilus. - Hội đồng bỏ phiếu lần đầu: 52,8% hài lòng thời lượng trận đấu; 48,8% đánh giá snowball ở mức ổn định. - Người chơi tích lũy quyền bỏ phiếu bằng thời gian chơi; lá phiếu kế tiếp chọn tướng được phục dựng. - Riot Games thừa nhận hệ thống phân loại xếp người chơi mới sai bậc kỹ năng, đồng thời đánh giá vấn đề bot "không nghiêm trọng". - Lộ trình cập nhật tiếp theo do Riot Games ấn định ngày 23 tháng 9; năm cụ thể không được nêu trong tài liệu gốc. **Nguồn:** Thông báo chính thức của Riot Games về bản cập nhật 4 của Classic League of Legends, do David 'Phreak' Turley trình bày; ngày công bố cụ thể không được ghi trong tài liệu gốc. | Cross-checked: VuaBong.vn **Hỏi đáp liên quan:** - Hỏi: Ai trình bày bản cập nhật 4 của Classic League of Legends? Đáp: David 'Phreak' Turley, đại diện Riot Games, người công bố các thay đổi và cuộc bỏ phiếu của Hội đồng. - Hỏi: Bản cập nhật 4 ảnh hưởng thế nào tới cảnh thi đấu chuyên nghiệp? Đáp: Không ảnh hưởng, vì Classic League of Legends vận hành tách biệt khỏi máy chủ chuyên nghiệp và không có giải đấu hay tuyển thủ. - Hỏi: Vì sao khiếu nại về bot có thể là lỗi phân loại? Đáp: Riot Games thừa nhận người chơi mới bị xếp sai bậc kỹ năng, khiến họ di chuyển và ra quyết định giống bot trong mắt đồng đội.
On the Riot Games news feed, the fourth update to Classic League of Legends opens with a single name: Graves. No win rate table, no pick-ban rate, no before-and-after power comparison. Only a list of changes, a roadmap dated September 23, and a link to the Council's ballot.
That is a familiar silence. In 2026, while running esports tournaments in Vietnam, I learned that the easiest thing to overlook in an update is usually the most important: what a publisher chooses not to disclose.
When the data sheet speaks, the stadium must learn to stay silent. This time, the data sheet has not spoken. And that silence is itself data.
Classic League of Legends is League of Legends' legacy mode, running in parallel with the professional competitive client. The mode restores early-era champion kits, along with legacy systems such as jungle respawn timers and items that have vanished from the main client. Update 4 brings back the classic Graves kit and adds Fizz, Nami and Nautilus in their original versions.

The distinction matters: this is not competitive content. There are no teams, no tournaments, no pro players. Graves, Fizz, Nami and Nautilus are champions, not people. David 'Phreak' Turley appears as a Riot Games representative presenting the update, not as a coach or a player.
The update also changes the system layer: jungle respawn timers are adjusted, the Eye Item returns, and three new items are proposed. On balance, the buffed group is Akali, Galio, Kassadin, Poppy and Shyvana; the nerfed group is Fiora, Morgana and Twisted Fate.
The Council's first vote is the densest piece of data in the announcement. Players accumulate voting power by playing the mode, then vote on key issues. Two numbers were published: 52.8% were satisfied with match duration, and 48.8% rated snowballing as stable.
For the remaining items — jungle respawn timers, the Eye Item, three new items — the announcement only says the Council agreed, with no percentages attached. That information asymmetry is worth noting: two items were quantified, four were described in prose.
Neither published figure is a majority. 52.8% and 48.8% are the highest pluralities, not majorities. Close to half of voters did not endorse those two propositions. Framing it as "the community agreed" therefore inflates the real level of consensus.

The champion balance pass repeats the main client's familiar methodology, applied to an old sandbox. The buffed group consists of under-represented picks: Akali, Galio, Kassadin, Poppy, Shyvana. The nerfed group consists of dominant picks: Fiora, Morgana, Twisted Fate. No percentage accompanies any individual change, so the depth of each adjustment cannot be graded.
At the system layer, restoring jungle respawn timers and the Eye Item shows Riot is building a complete nostalgia experience, not just one new champion. A mode like this requires its own code branch, separate from the main client, and cannot be sustained by a single update.
Two quality issues are acknowledged by Riot itself. The first is bot activity in lobbies — Riot rates it "not as serious as social feedback." The second is the classification system: Riot admits new players are being placed in the wrong skill tiers and that the system has "some problems."
Based on my experience tracking matches, the second admission explains most of the first. A new player placed in the wrong tier will move like a machine, decide like a machine, and be reported by teammates as a machine. Part of the bot complaints may be classification error rather than automation. Riot raises this hypothesis in its own announcement but has published no data to confirm or refute it.
Every number has a story; my job is not to ruin it.
The biggest risk to this mode is not bots — it is nostalgia decay. Every legacy mode follows the same curve: announce, build anticipation, deliver the most-awaited champion, re-engage with a fresh vote. Graves was the community's demand since the mode was announced, meaning Riot is operating on community demand. But once the most-demanded item has been delivered, where does the next impulse come from?
The next vote — the community choosing which champion gets restored next — is the interim answer, turning content decisions into an engagement mechanic. The problem is that the ballot's binding authority is never stated. If results are merely advisory, the community will notice soon enough. The second blind spot is the sample: voting power accrues through playtime, so the most committed group decides outcomes, and 52.8% is the result of that kind of sample.

At 39, I have learned that data also hurts when it is distorted. A plurality gets called consensus. An update that publishes no win rates gets called balanced. Small distortions, but they accumulate.
The signal to watch sits on the September 23 roadmap. If that update addresses the player classification system, bot complaints should fall in step, and the true cause will be confirmed. If it does not, this mode will carry a quality fracture just beneath its nostalgic surface. And if the next Council ballot is published with full percentages, trust will be rebuilt in the very way it was eroded: with numbers.
