Sometimes a character walks into a tactical shooter and just—rips the rulebook in half. That was Raze back in the spring of 2020, when VALORANT was still in closed beta and everyone was desperately trying to figure out what kind of game Riot had actually made. I remember booting up my first few matches and being absolutely flattened by a rocket launcher from a flying agent I never even saw coming. And I wasn’t alone. The community went up in flames, and honestly? The debate got personal.
The core of the problem was simple but explosive. VALORANT had been pitched as a reimagining of Counter-Strike: Global Offensive’s tight gunplay, enhanced—not replaced—by agent abilities. Riot hammered that message in 2019: abilities are supplementary, gunplay is king. Then along came Raze with a kit that felt like it had been air-dropped straight from Overwatch. Cluster grenades, a deployable Boom Bot that chased you down with a landmine, and a rocket launcher that could be fired while she hung in the air after a satchel jump. You didn’t need pixel-perfect aim. You just needed to know your ability combos, and entire teams could evaporate. For a game still trying to earn its hardcore tactical stripes, this was a gut punch.
The moment the conversation exploded into the mainstream? That would be the developer-versus-streamers showmatch. Riot’s own dev team locked in Raze and absolutely decimated a squad of professional streamers that included Summit1g. It wasn’t just a loss—it was a clinic in ability-based destruction. Summit1g, never one to hide his feelings, vented on stream and on Twitter, calling out the agent’s design as fundamentally broken. His words crystallized something a lot of players were already feeling: this isn’t the game we were promised. I mean, come on, when the people who built the game use a character to clown on some of the biggest names in the scene, you know something’s up.
But here’s where it gets tricky—and deliciously human. Not everyone was grabbing pitchforks. Shroud, the human aimbot himself, dropped a tweet saying he found Raze “mostly balanced.” That sent fresh ripples through the discourse. Some streamers practically exhaled in relief, grateful that a voice with that much weight was pushing back against the rising tide of nerf demands. Others stayed firmly in the opposition camp, replying with clips of being deleted by a Boom Bot from around a corner. The community was split right down the middle, and you could almost hear the argument bouncing between discord servers at 3 a.m.
Looking back at it from 2026, the whole saga feels like a rite of passage. Riot didn’t immediately slash Raze into oblivion—they played the long game. Over the next dozen patches, her kit got tuned: grenade damage tweaked, Boom Bot health adjusted, ultimate cost increased. Slowly, the devs pulled her back into a place where gunplay mattered more. And you know what? The meta evolved. Players learned to listen for the distinct clink-clank of her satchel charge, to bait out the rocket, to punish her aggressive positioning. The optimal playstyle that seemed absent in those first feverish weeks eventually emerged, and reports of Raze’s overwhelming strength turned out to be… well, a bit exaggerated. She’s still a menace in the right hands—I’ve watched a Raze main dismantle a site with nothing but blast packs and a sheriff—but she no longer feels like a cheat code.
What fascinates me now is how much that little controversy shaped VALORANT’s identity. Raze became the lightning rod for a conversation about what the game actually wanted to be. Could an agent with high ability-kill potential coexist with a tactical shooter’s soul? Six years later, the answer is a clear yes, but only because Riot listened—not just to the rage, but to the data and the dedicated players who stuck around to find the counterplay. The game is richer for having her, and that early friction probably saved future agents from crossing the same line. Funny how things work out. These days, when someone complains about a new duelist’s burst potential, I just smile and think back to the beta. You had to be there.