KDA Is Not a Vanity Metric for Supports—It Is a Pressure Map

When fans say KDA does not matter, they usually mean that a player can farm safe kills, avoid risk, and post a pretty stat line without actually controlling the game. For a support, that criticism is even louder. A support can protect their KDA by sitting behind the ADC, never initiating, and only collecting assists after someone else has already made the play. But Keria’s 2022 LCK Spring season flips that assumption completely. His KDA was not a shield; it was a map of pressure. During T1’s undefeated 18-0 regular season, Keria finished with one of the highest assist totals in the league while keeping his deaths extremely low. That combination is not passive. It means he was present for almost every winning fight, yet rarely gave the enemy a free shutdown or a free objective. KDA is calculated from kills, deaths, and assists, but for a support the assist column is a record of participation in every lane’s success. Keria was not tagging along; he was often the first mover. His Renata Glasc, Nautilus, Karma, and Thresh games show the range: he could disengage, engage, shield, or roam. A support with a high KDA on a perfect team could be accused of being carried, but Keria’s low deaths came from perfect positioning, not from avoiding contact. His KDA is a pressure map: it shows where T1 created advantages and why the enemy could never breathe. MVP voters should look at that map, because it explains how a support controlled the entire league.

Keria’s Assist Volume Turned T1’s Lanes Into a Permanent Threat

The assist column is where Keria’s MVP case becomes undeniable. League of Legends support players live and die by assists, but not all assists are equal. Some come from late cleanup after a fight is already won; Keria’s came from the opening moments. He partnered with Gumayusi to dominate the bot lane, then drifted mid to unlock Faker, then joined Oner for river fights and tower dives. T1’s 18-0 regular season was not built on one carry’s heroics. It was built on Keria arriving first, forcing a summoner spell, absorbing a crucial cooldown, and letting Zeus or Faker convert the advantage. His assist volume reflected that role. Every time T1 collapsed on a side lane, Keria was there. Every time Oner invaded, Keria rotated first. Every time Gumayusi needed space, Keria created it with a hook, a shield, or a zone. When analysts compare supports, they often separate “engage” and “enchanter” players. Keria refused the binary. On Nautilus and Thresh, he started fights; on Karma and Lulu, he amplified carries; on Renata Glasc, he did both. The result was a support who multiplied every resource T1 had. MVP awards often go to the player with the flashiest kills, but Keria’s assist count was the connective tissue of the best regular season in LCK history. His KDA was not padding—it was evidence that T1’s stars shined because he kept the lights on.

Low Deaths Reveal the Discipline Behind His Aggressive Roams

The death column is the most underrated part of Keria’s KDA. Support is the role most likely to die for vision, for a ward, for an engage that fails, or for a lane sacrifice. A support who dies often can still be great, but a support who roams aggressively and rarely dies is breaking the role’s usual economy. Keria did exactly that. He played champions like Nautilus and Thresh, which require him to be the first body into the fight. He also played enchanters, which require perfect spacing to avoid being blown up. In both styles, his death count stayed remarkably low. That does not mean he played safe. It means he calculated risk at a level few supports can match. He knew when to flash forward, when to bait a hook, and when to walk away. He knew which ward was worth contesting and which objective was already lost. Those decisions do not always appear in highlight reels, but they appear in KDA. Every death a support avoids is a death the enemy does not get to convert into dragon pressure, tower plates, or baron vision. Keria’s low deaths kept T1’s map closed. When he did die, it was usually in a trade that opened something larger. That is the difference between a passive support and an efficient one. KDA explains why Keria deserved MVP honors because it proves his aggression was disciplined, not reckless.

The MVP Case Extends Beyond KDA to Vision, Draft, and Teamfight Command

KDA is the starting point, not the entire argument. Keria’s MVP case also rests on vision control, draft flexibility, and teamfight command—areas where box scores are incomplete but still leave fingerprints. T1’s perfect regular season required a support who could play every style: engage, enchanter, roam, and protect. Keria’s champion pool made T1 impossible to draft against. If the team needed a Renata Glasc ultimate to turn a fight, he delivered. If it needed Karma speed to enable Zeus’s side-lane pressure, he delivered. If it needed a Nautilus lock-down on Faker’s target, he delivered. His vision score and roam timing gave T1 information before objectives spawned, which is why they so often won fights before they began. In teamfights, Keria was the player who decided the shape of the engagement. He could start a fight, peel for Gumayusi, or bait enemies into a collapsing trap. Those actions created assists and protected his KDA, but they also created the conditions for every other MVP-caliber player on T1 to perform. When the LCK named Keria the regular-season MVP, it was a historic moment for supports. The award did not happen because voters ignored KDA; it happened because KDA, combined with the eye test, showed a support who was not a passenger on a superteam. He was the driver. KDA explains why this support player deserves MVP honors, but vision, draft, and teamfight command explain why the honor was inevitable.