Riot reworks Mel's W in League of Legends: reflect removed, ally shield and movement speed added

In a practice room in Hamburg there is a sound I learned to recognise before I could see the screen: the W key pressed twice, very fast, then going completely quiet. The Mel player sits at the third row of machines, shoulders tilted slightly forward, eyes fixed on the dark space beyond her opponent's vision. She waits. Not for a teamfight — for one specific projectile: Jhin's fourth shot, or Seraphine's enchanted chord. The room goes silent. Then W fires, the projectile turns around, and on the other side of the screen someone exhales in a way I can hear clearly through my headset. That is Mel's rhythm. I don't analyse matches; I remember faces when the match ends — and here, that face belongs to the person who was just hit by their own ability. This week Riot Games announced they are reworking Mel's W. The reflect is gone. In its place: projectile destruction, plus a shield and movement speed for nearby allies. The rest of the kit is being tuned as well — passive, Q, E, R. Patch 26.22, expected on live servers roughly three weeks after the announcement. Mel arrived in League of Legends with an uncomfortable reputation. She was labelled the most frustrating champion on the roster, in Riot's own framing. The problem sat in W: an ability that reflected every incoming projectile, turning an opponent's spell into a weapon against them. For the Mel player, that was a moment to celebrate. For the person opposite, it was the feeling of their ability evaporating out of the game — worse, it came back and killed their teammates. Riot says it tried multiple rounds of adjustments to preserve the mechanic. A design team does not abandon a champion's signature ability after several failed tuning passes unless the mechanic cannot be tuned at all. Reflect is a binary mechanic: it either catches the spell or it doesn't. There is no middle ground to adjust with numbers. The first beat of any balance patch isn't in the numbers — it's in whether the design team chooses to keep or delete a mechanic. Here, they deleted it. This rework is not an ordinary power reduction. It is an identity migration. Mel's W moves from a punish tool to a peel tool. Her competitive function changes category: from a reactive burst-denial mage to a utility mage with genuine support-role viability. Three changes add up to that direction quite clearly. First, W now grants a shield and movement speed to nearby allies — that is the signature of the enchanter class, not of a solo-lane duelist. Second, E loses root duration at close range and gains it at maximum range. That is the clearest signal of all: the system is paying players to hold their spacing and taxing players who step in. Third, the passive gains health and armour scaling — a mage with armour growth is usually built to survive a dive rather than to win a duel. Those three lines combine into a posture: stand further back, hold the rhythm for someone else, hand the burst damage to a teammate. The beat keeper never stands in the middle of the pitch. That sentence applies to the new Mel literally. On the other side of the balance sheet are the old Mel players. Her competitive value rested on a reactive read skill: deciding when to hold W to catch a Seraphine ultimate or a Jhin fourth shot. Deleting the reflect deletes that skill. This is the harshest class of balance change — not a numbers nerf, which players can adapt to, but a skill-obsolescence event. Someone who spent hundreds of hours learning reflect timing carries nothing into the new version except the habit of holding W too long. Riot states the rework will make Mel more balanced while preserving her unique identity. But the unique identity named in the same announcement was the reflect mechanic. Those two sentences sit awkwardly together. A champion's identity cannot be simultaneously deleted and preserved in one patch. There is one point worth crediting to dedicated Mel players. W still destroys projectiles. The ability to deny a spell survives; only the reward attached to it changes. Instead of returning damage, it now hands a shield to the whole team. Structurally, that is a fair trade for the back line: a defensive ability that can save someone, rather than a defensive ability that only inflicts pain. The clearest beneficiaries are projectile-reliant champions who were previously punished by their own damage. Jhin with his fourth shot, Seraphine with her enchanted chord, any marksman who once dumped a full combo into Mel and received double in return — all of them escape that fear. The second group is melee divers, who previously could not close on a reflect-holder without killing themselves. The third group, rarely mentioned, is Mel's own teammates: for the first time they get something out of that ability. The losers are clearer. Beyond the specialists, there are teams that used Mel as a counter-pick into projectile-heavy compositions. That pick loses its core tool. Based on my experience following matches and training sessions, reworks of this kind usually produce about three weeks of chaos before the community settles on a new way to play. Those three weeks are the best window to watch, because players haven't yet memorised the champion and are still experimenting. The most interesting question sits in Riot's stated goal. The team says the rework aims to limit situations that feel too frustrating when playing against this champion. That goal is only half achieved. The frustration has two layers. Layer one: my spell goes out and disappears. Layer two: my spell goes out, comes back, and kills my teammate. The rework deletes layer two. Layer one remains fully intact, because W still destroys projectiles. The opponent will still stare at the screen and see nothing happen. That feeling doesn't disappear; it simply stops arriving with the opponent's laughter attached. The choice of examples is also worth noting. The two illustrations in the announcement are reflecting Seraphine's ultimate to charm the entire enemy team, and reflecting Jhin's fourth shot back at Jhin. Both are rare, spectacular, highly shareable moments. No figure is offered for how often such moments actually occur in an average game. Balancing on memorable clips rather than frequency data always carries the risk of over-correction. A mechanic that is intensely frustrating but rarely triggered gets treated as though it fires every game. The counter-intuitive angle deserves airtime too. For professional flex value, this change is not straightforwardly negative. Flexibility between mid and support is priced highly in draft, because it lets a team defer revealing its roles until the opponent has committed. Losing solo-lane power while gaining role ambiguity can be a net positive. That is a structural inference, not something the announcement states. On timing: Riot typically ships patches about two weeks apart. Patch 26.22 lands in the late-season window, most likely after the World Championship patch lock and before the following spring split. If so, the competitive shock is deferred and teams get a full preseason to adapt. A rework-level change landing in that window is far gentler than one landing mid-split. The limits of this piece also need stating. The source provides no win rate, pick rate or ban rate for Mel before or after the patch. No team, player or tournament is named. Every professional-level read above is an inference from kit structure, and needs re-checking once live-server data appears. We watch the match, but we live in the silence between matches. That silence here is the three weeks from announcement to deployment. Inside those three weeks, thousands of Mel players will sit in front of their screens and rehearse a new habit: pressing W not to hit back, but to cover the person beside them. What I want to know isn't whether Mel ends up strong or weak. It's whether a player who learned to love the reflect will still recognise their champion after it has been taught to protect people instead.