Why the On-Hit Item Class in League of Legends Cannot Be Fixed by a Single Buff

That night in Beijing, what kept me awake was not a teamfight. It was a single line of text. A community forum exchange, screenshotted, shared, translated, and carried into Vietnamese League of Legends groups in under six hours. In it, a Riot Games designer acknowledged that the on-hit item group has a problem — that it needs a buff, for both melee and ranged champions, with ranged prioritized.

No timeline. No patch note. No change live on the test server. Only an acknowledgement.

And yet, within a single night, the community had built an entire debate about what Riot should do next. I have followed this game's balance cycles for a long time, and there is a pattern I have learned to trust: when a community finishes building its expectations before a publisher finishes building a patch, the party hurt last is usually the community itself.

The more interesting detail sits elsewhere. This debate does not revolve around one item. It revolves around an item group — and the way the community framed the question accidentally pointed at the sorest spot in the whole balance problem.

Context: an item group that lives on patience

On-hit items trigger their effects on basic attacks. They do not reward a burst of abilities, and they do not promise a clean kill in two seconds. They reward rhythm: hit, hit, hit, with power stacking through attack speed and accumulation effects.

For League players, this is a distinct philosophy. For me, it recalls female volleyball hitters who live on consecutive high balls: no finishing swing looks beautiful without twenty touches before it. Victory comes from repetition, not from a moment. An item build reads like a whisper passed through every auto-attack, and the player has to listen to it for thirty minutes.

The problem is structural: when the meta tilts toward burst damage and fights that end fast, an item group that needs time to scale is naturally disadvantaged. You cannot stack anything if the game ends before you land enough hits.

Riot saw the signal. In Patch 25.14, they buffed three items from this group: Kraken Slayer, Gươm Vô Danh and Vũ Điệu Tử Thần. That was a deliberate adjustment aimed at exactly the item group considered weak. When the patch landed, the community's general feeling did not change.

An item gets buffed and still nobody wants to buy it. That signal points beyond the stat line.

Three overlapping layers

The first layer is the item layer. Kraken Slayer, Gươm Vô Danh, Vũ Điệu Tử Thần and several other attack-speed items share a common fate: they appear in very few players' builds, and when they do appear they are usually a fallback rather than a first choice. When an entire item group lands in that state, a buff handed to one or two members only produces a small patch of light inside a large dark area.

The second layer is the champion layer, and this is the part I care about most. A small change to an on-hit item's stats can produce a very large change in the power of a specific group of champions. The reason lies in special auto-attack mechanics: champions such as Irelia, Yasuo and Yone have abilities that reset or rewrite how basic attacks are calculated. For them, each point of attack speed or on-hit damage is not multiplied along an ordinary curve, but along the curve of their own kit.

This is the stat-line amplification problem, and it is not new. An item is designed to serve the median user. But when it meets a champion sitting at the edge of the distribution — an extreme user with its own mechanics — the same stat line can launch that champion upward or crash it downward. No stat line stays still in the middle.

Based on my experience watching these matches, this is the least predictable type of change in the entire balance system. A champion's win rate can creep by a few thousandths after a seemingly harmless item adjustment, while its presence rate in high-ranked games jumps by whole tiers. One-trick players notice the change before the statistics charts even update.

The third layer is structural, and it is the hardest. The acknowledgement says the item needs a buff for both melee and ranged. That means two user groups with entirely different damage profiles share one stat line and cannot be tuned independently. A melee champion auto-attacks to maintain pressure inside a short fight. A marksman auto-attacks to hold distance and finish a target from range. One item, two rhythms, two different time windows.

When one item must serve both, the designer is forced to place the balance point somewhere between the two groups. Any point in the middle means neither group is truly satisfied. And because both melee and ranged are dissatisfied, both have a reason to call this item group weak — even though their reasons are completely different.

The final consequence of these three layers is a narrowing of build diversity. A player who mains an on-hit champion progressively loses options, gets pushed toward a single path, and that path is usually not the best one. Once build diversity dies, individual skill erodes with it: strong and weak players are locked into the same mould, and what separates them is only mechanical execution, not strategic choice.

Fixing the symptom and the substitution trap

The popular community reading is: the item is weak, so raise the stats. I think that reading misses a more important possibility.

The on-hit item group may be reflecting a cause at the system level rather than at the stat level. When champion durability is tuned toward longer fights, sustained-damage playstyles benefit. When kill speed rises, burst playstyles benefit. If the game's power curve becomes steeper — meaning games end before on-hit players land enough hits — then no stat increase on a single item can return what was taken away at the level of time.

In other words, the problem with on-hit items may be a pacing problem, expressed outwardly as an item stat problem.

The evidence sits in the adjustment history itself. Riot buffed this group in Patch 25.14. If the cause were stat-related, that buff should have produced a visible shift in pick rate. The fact that the group is still considered weak after a buff means either the buff was insufficient or it was offset by meta drift. Both possibilities lead to the same conclusion: treating the symptom lets the symptom grow back.

I once wrote about women's football and met the same pattern. A sponsor pours money into a women's competition, media covers it heavily, and everyone says the problem is solved. Three years later, average salaries have barely moved, because the root sat in training infrastructure and access to pitches — not in that single cheque. One investment does not fix an underinvested structure. One buff does not fix an item group that has lost its place in the game's pacing.

The second, less-discussed risk is blowback. If the on-hit buff overshoots, the champions who benefit directly will rise in presence, and the next cycle will be a nerf aimed at those very champions. This is the buff-then-revert loop this game has already run through several times with on-hit items. Players get two strong weeks, then two months weaker than before.

There is one directional clue worth noting: ranged prioritized. If Riot genuinely prioritizes on-hit marksmen, the fix likely sits at the item layer rather than the champion layer. That is technically sensible, because an item-level fix adjusts a whole class of users in one move. But it also exposes the hard part: to prioritize ranged while keeping melee acceptable, a designer needs a tool that can separate the two groups — and a shared stat line is not that tool.

One more point about sourcing. The original exchange carries no link and no full context. A statement can be shortened, placed next to a different question, or distorted through several layers of translation. The community commentary itself noted that this is not an official buff announcement, and that handling is proper. But communities tend to read the content and skip the disclaimer.

I have seen the same thing in another discipline: an unverified piece of information powerful enough to fuel a week of debate, and when it was confirmed false, nobody went back to correct it. Expectation travels faster than fact, and it does not retract itself.

Three signals to track

All three sit outside the conversation currently causing the storm.

The scope of the change is the first. If Riot only adjusts one item, the story repeats in a few months. If they touch the whole group, that is the signal that the cause has been recognized at the user-class level.

How they handle the melee-versus-ranged problem is the second. A shared stat change will always leave one group behind. A role-specific modifier, or a restructuring of the item group, is what actually reaches the root.

The pacing curve in upcoming patches is the third, and probably the most important. If average game length keeps shrinking, every on-hit buff is only a short-term loan, repaid later with a nerf.

In this problem, the truly weak party is not the item. The weak party is the player who chose a playstyle built on patience, inside an environment that rewards explosion.

In esports, I find the heartbeat of a generation that does not need a pitch but still needs a game. That heartbeat does not follow every kill. It follows every basic attack — steady, repeated, and very easy to miss inside the noise of bursts.

I do not think a buff will save the on-hit item group. I think it will create a short window of light, enough for two more weeks of debate, and then everything returns to where it was, alongside a nerf aimed at a few familiar names.

But one thing is genuinely changing. The way the community frames the problem has shifted from one item to an entire group, from stats to structure. A community that knows how to demand the right thing is hard to satisfy with a cosmetic patch.

An empty stadium once taught me that football never lacks spectators, only noise. An item group is the same: it does not lack users, it lacks a reason to be used.

And if you are someone still loyal to the on-hit playstyle, let me ask you one question: are you waiting for a stat line to be fixed, or for a design philosophy to be acknowledged?