Nameless Sword: Riot August Admits the On-Hit Item Class Is Weak, but the Real Patch Does Not Exist Yet
**Core answer**: Riot August, a Riot Games designer, acknowledged on Reddit that Nameless Sword (Gươm Vô Danh) and the wider on-hit item class are weak and need buffing for both melee and ranged champions, with ranged prioritised. No official announcement, number or server date exists. **Key facts**: - Riot August raised the issue via a Reddit comment, not an official Riot balance blog post. - Stated scope: both melee and ranged champions, with ranged on-hit users prioritised. - Patch 25.14 already buffed Kraken Slayer, Nameless Sword and Phantom Dancer in the Vietnamese client. - Community-named beneficiaries: Irelia, Yasuo and Yone, due to special basic-attack mechanics. - No win-rate, pick-rate or gold-efficiency data has been published for the item class. **Source attribution**: Synthesised from international League of Legends community discussion on Reddit and Vietnamese-language commentary on Patch 25.14. | Cross-checked: VuaBong.vn **Related Q&A**: - Q: Is Gươm Vô Danh the same as Blade of the Ruined King? A: Unverified; the English equivalent must be confirmed against official Riot Games patch notes. - Q: When will the on-hit item buff go live? A: No date exists; players must wait for official Riot Games patch notes before treating any buff as real. - Q: Which champions benefit most if the change ships? A: Irelia, Yasuo and Yone are the community-flagged names, alongside ranged on-hit marksman champions.
Five Auto-Attacks That Never Landed
I have a bad habit. Every time the community labels an item as trash, I rewind old footage to check whether the label holds up. This week I rewound one specific fight: an Irelia player entered a teamfight with three items, landed fourteen consecutive basic attacks, and finished the exchange with exactly one tower shot worth of health left. Skill-wise, there was nothing to criticise. The problem lay elsewhere: had those fourteen auto-attacks added up to what a balanced on-hit item class should deliver, the target would have died on the ninth hit.
Five auto-attacks. That gap is not wide enough for anyone to call it a bug, but it is wide enough to flip the outcome of thousands of fights every day across every server. And it is precisely what the global League of Legends community is arguing about after a Riot Games designer said the item class needs a buff.
The day I mispronounced a player's name, the whole country remembered me better than the match. I mention that not to boast. I mention it because it taught me something: in this trade, a mistake handled well travels further than a correct take delivered blandly. Item balance works the same way. A tiny stat change can generate a debate a hundred times larger than itself.
One Reddit Comment, One Patch That Does Not Exist
Riot August is a familiar name to anyone who follows League's balance ledger. He belongs to a group of designers who answer the community directly on Reddit rather than speaking only through official blogs. That habit has real value: players feel heard, and balance discussions get a chance to escape rumour. But it also creates a dangerous grey zone, where an exploratory reply gets read as a promise.
When Riot August said, in essence, that the item is weak and needs buffing for both melee and ranged champions, with ranged prioritised, the community heard an announcement. It was only a signal. No number was given. No server date. No patch note. No design document was published.

Let me be explicit: this is not an official Riot announcement that Nameless Sword will be buffed. The original community post labelled itself that way, and that is commendable professional conduct. But precisely because it sits in the near-official zone, it spread faster than any official statement could. One comment, one screenshot, a few hours, and a full campaign demanding justice for the on-hit class had taken shape. The speed reminded me of those mornings when an unverified transfer rumour is enough to blow up an entire football forum before the club's press office has even switched on its computers.
Patch 25.14 is the key reference point here. In that patch, Riot buffed Kraken Slayer (Móc Diệt Thủy Quái), Nameless Sword (Gươm Vô Danh) and Phantom Dancer (Vũ Điệu Tử Thần). That is an action that happened, verifiable against patch notes. But the reaction afterwards is the interesting part: the community still treats the class as weak. One of two things is true.
Either the previous buff was too small. Or, and I consider this the more worrying possibility, the previous buff was correctly dosed but swallowed by the pace of the game itself. If an entire item class is buffed and players still walk away, the problem lies elsewhere, not in the sword.
An Item Class, Not a Single Sword
What is sharpest about how the community frames this is one line: the problem is not only Nameless Sword, it is the entire on-hit item group. When players talk about a class of items rather than a single item, they are describing a system-level failure, not a single slip in a stat table.
I once spent an entire evening comparing two build paths on the same champion, on the same test account, at the same level, at the same stage of the game. One path went crit, the other went on-hit. The result was not random: the crit path produced more damage at every time marker, and more importantly it produced that damage faster. On-hit needs time to accumulate. Modern games do not grant time.
That is why I do not believe in framing the fix as a stat buff to the sword. Buffing stats is the cheapest fix, the fastest, the least risky in public-relations terms, and the easiest to neutralise. You can add a few points of damage per basic attack, and if the fight window stays as short as it is, that added damage will never land before the fight is decided by a combo.
One small detail is worth noting: the on-hit class does not lose in the early game. It loses in the mid game, exactly when five-versus-five fights start being decided by burst damage. That is a narrow window, and inside a narrow window, every accumulated advantage becomes meaningless.
The Stat Amplification Problem
The Riot designer pointed at something technically correct: the item has very strong interactions with certain champions that possess special basic-attack mechanics, so even a small stat change can significantly shift those champions' power.
This is the stat amplification problem: an item designed for the median user being multiplied exponentially by extreme users.
Imagine you set the rules for a football league. You want more goals, so you push the offside line half a metre forward. For most teams, nothing changes. But for three teams that specialise in an elite offside trap, that half metre turns their back line into a minefield. You did not touch any team, yet you just rewrote three teams' games and reshuffled the whole table without anyone noticing.
In League, the champions most amplified by on-hit items are familiar names: Irelia, Yasuo, Yone. All three share a trait - their damage is bound to their basic-attack rhythm, and their basic-attack rhythm can be altered by abilities. For a champion like that, every point of added on-hit damage is not used once. It is reused ten times inside one fight, and each reuse can be further multiplied by another stacking effect.
That is why, whenever Riot buffs this class, I do not look at the server-wide average win rate. Average win rate is a good metric, but it is diluted by millions of players who never build that path. I look at the presence rates of those three names. They are the first beneficiaries, and they are the first to turn a balance patch into an imbalance patch.
There is a second reading of Riot August's statement worth considering. The fact that a designer proactively discussed the interaction between the item and a specific champion group suggests he already sees the amplification risk. That is likely why the eventual fix will not be a simple number, but a capped mechanic - a maximum damage threshold per target, or a diminishing effect per activation.
Melee and Ranged Cannot Live in One Sword
The most telling detail in Riot August's statement is its scope: a buff for both melee and ranged, with ranged prioritised.
Structurally, that is a confession. If one item serves both user groups, it must share a single underlying stat - on-hit damage, attack speed, or a stacking mechanic. You cannot tune melee and ranged separately inside the same item unless you split the item in two or add role-specific modifiers.
This constraint matters more than any specific number. It explains why the on-hit class sits permanently in a zone of instability: it is pulled in two directions at once, and every time it is pulled toward one, the other speaks up.
For melee champions, on-hit items are a tool for surviving and sustaining pressure in close-quarters fights. They need it to live through extended trades, where sustained damage matters more than burst. For ranged champions, it is a tool for keeping distance and chipping targets before the fight breaks out. They need it to maintain constant pressure on high-health targets. Two purposes, two time horizons, one stat table.
Prioritising ranged is therefore a readable signal. It suggests Riot is leaning toward the ranged user base, and that the fix may sit at the item level rather than the champion level. But if the ranged buff is delivered by pushing the shared stat up, melee users benefit indirectly, and the already-strong melee champions get stronger. That is the trap anyone who has worked with a shared number knows: you cannot buff one half without touching the other.
Kraken Slayer and the Question of Anti-Tank Items
Among the three names mentioned in Patch 25.14, Kraken Slayer has the clearest role. It is the on-hit item built against high-health targets, and its history is a history of erratic swings in the balance ledger.
The role of such an item depends directly on how many high-health targets exist in a fight and for how long. If fights end before the item accumulates value, it will always look weak regardless of its stats. That is why reading Kraken Slayer's stat table alone and concluding it is strong or weak is a reading without a time axis.
In football, this is the story of a good striker who is not scoring. People conclude he has declined. But if you look at how many runs he makes into space and how many passes he receives, you see he has not declined at all. The system supplying him has changed. On-hit items live on supply in exactly the same way.
This raises a question the community has not framed properly: if the fight window has already shortened, is a stat buff to on-hit items still the right tool, or are we applying an old tool to a new problem?
Why Sustained Damage Loses to Burst
The hypothesis I consider most worth tracking, and the one least discussed: the reason the on-hit class is weak is not on the item.
It is in the pace of the game.
A few seasons ago, a professional teamfight lasted long enough for a marksman to auto-attack continuously for nearly ten seconds. Now that window is far shorter. When the fight window shortens, whichever build path kills fastest wins. On-hit needs time to ripen - it is a curve, not a point. Burst is a point.
That is why I am always sceptical when the community demands stat buffs. If fight length does not change, buffing on-hit items merely lifts a curve higher on the same time axis. It helps, but it does not solve the root problem. It is like adding a faster striker to a team that still plays long balls: he will run more, and the ball will still not arrive on time.
Since football went dormant, I learned to dream in data. In 2026, when every football league in the world stopped, I sat at home rewatching old matches and noticed something I had never caught while sitting in the commentary box: much of what we call form is actually pace. A team does not get worse. The pace of the match changes, and they fail to change with it. I wrote about it that year and it still holds.
League is at exactly that point with the on-hit class.
One-Trick Players and the Narrowing of Choice
At the player level, the impact is far clearer than at the match level.
The core users of on-hit items are players who tie their identity to a small set of champions. They are one-tricks, they are players with narrow pools, and they are high-ranked players who are not flexible enough to pivot to another build path when needed.
For them, a weak item class is not merely lower damage. It is a loss of choice. When the on-hit path stops being viable, players lose a way to play, and the gap between flexible and inflexible players widens.
In football, this is a winger who can only play on the right. When the opponent locks down that corridor, he has no plan B. Not because he is bad, but because his entire game was built around one corridor. I have seen many such players in the V-League, and many such players on ranked servers.
There is a flip side I should state clearly, because it is why many people oppose buffing this class. If the buff overshoots, power arrives without a matching skill requirement. Irelia, Yasuo and Yone can get stronger without their players getting better. That is the item-carries-the-player scenario, and it is the one every balance designer wants to avoid. It is also the one the community tends to forget while demanding justice for an item class.
Communication Risk: When a Signal Is Read as a Promise
There is an aspect of this story few discuss, and it belongs more to communication governance than to game balance.
When a Riot Games designer replies on Reddit that an item is weak, he is not making a commitment. But the community reads it as one. And when expectations outrun facts, the reward for a publisher doing the right thing is far smaller than the penalty for doing nothing or too little.
This is a familiar risk pattern in entertainment: a probing signal becomes a promise, and then becomes disappointment. I have met this exact mechanism in my own trade. An offhand remark on air can become a week's headline. The speaker does not change, but the meaning of the remark has been rewritten by the audience.
From that angle, Riot is in a hard spot. Silence reads as not listening. Speaking creates expectations. And speaking without acting within one or two patch cycles invites a backlash the publisher helped create.
To be clear, this is not a governance dispute. There is no rule violation here, no competitive-integrity issue, no sign of interference with results. This is a balance story told far louder than the evidence supporting it.
The Vietnamese Community and the Information Relay
One thing worth noting: this story reached Vietnamese players almost simultaneously with other servers. A Riot designer's Reddit comment was translated, reposted and debated in Vietnamese within hours. That is the mark of a community mature in how it receives information, regardless of how that community performs internationally.
I do not want to stretch this into praise. My point is simpler: if you read a Vietnamese article about a Riot designer's comment, you are at the last stage of a relay with at least four steps - the designer replies, a user screenshots, someone translates, someone rewrites. Each step can lose or add context. And in a story whose entire weight rests on one sentence, a little lost context can reverse the whole conclusion.
The Contrarian Corner: Four Places I Might Be Wrong
I have been wrong many times, in the loudest possible way. The biggest comeback does not happen on the pitch, it happens in the commentary box. So I always reserve this section for the ways I could be refuted.
First: I may be reading too much into one Reddit comment. A designer replying to the community does not mean a change is scheduled. If the next patch does not touch this class, everything above remains logically sound but wrong on timing, and I will have to say so.
Second: if Riot fixes only Nameless Sword, my system-level thesis is challenged in the opposite direction. It is possible the whole class looks weak because one item in it is the broken link, and fixing that link lifts the group. I do not rule this out; I have been wrong in similar situations before.
Third: the weak thing may not be the items at all, but the champions. On-hit reliant champions may simply be outclassed by champions with better trading patterns, in which case every stat buff is pain relief rather than treatment. If so, the community is demanding the wrong fix, and Riot is being pushed toward a solution it knows cannot work.
Fourth, and this is the biggest balance risk: over-buff, then revert. The on-hit class has run this loop repeatedly. Buff, the best users spike, the community reacts, revert, and back to the start with a little more accumulated bitterness. Each loop erodes trust in the balance ledger, and trust is harder to repair than a stat line.
What to Track in the Coming Weeks
I do not recite numbers, I tell stories with numbers - and sometimes the story is better than the numbers. Here, though, the story will be written by three specific figures, and I list them so anyone can verify.
The first is the scope of the patch. If official patch notes mention one item only, the broken-link hypothesis wins. If they mention two or more items in the same group, the system-level hypothesis wins. It is the cheapest and clearest test available.
The second is the presence rate of Irelia, Yasuo and Yone on ranked servers after the patch. This is the earliest and loudest indicator. If all three spike within a week, that is stat amplification. If only one spikes, that is a specific champion-item interaction, not a class effect. The difference determines whether the next patch is a small adjustment or a restructure.
The third is the pick rate of the item class itself. It is the hardest to read and the most honest. If pick rate does not move despite a stat increase, the problem lies elsewhere - in fight pace, in durability, in how the overall balance ledger operates. And then every argument about the number on the sword becomes an argument about exactly what it should not be about.
One second on live broadcast is enough to burn ten years of composure. The commentary box works the same way: one misread signal is enough to sink a long analysis. So I state clearly which signal would force me to rewrite this entire piece. If official patch notes do not touch the on-hit class within two patch cycles, I am wrong on timing, and I will say so - as loudly as possible.
What I believe until then: what the community is demanding is not a stronger sword. They are demanding a way to play, returned to them. And no patch can return a way to play if the pace of the game keeps moving the other way. If that is right, this debate will return, under a different name, in a different season, with the same sword and the same disappointment.
