A leaked code fragment has given Valorant players a fresh look at one of the most requested quality-of-life features in the tactical shooter’s history: a native block tool. The leak, which surfaced in 2024, describes a system that would let players cut off unwanted contact from specific users, including friend requests, party invites and voice communication. In 2026, the feature remains a subject of intense community interest because Riot Games has not yet announced a formal launch date or a confirmed rollout plan.

The timing matters. Valorant is a game where a single callout can decide a round, and where a single bad actor can poison an entire match. Team flashes, walls placed to trap allies, and abilities used to kill teammates are not mere annoyances; they are small acts of sabotage that can snowball into arguments, retaliation and reports. Riot’s broader portfolio has seen similar friction, particularly in League of Legends, where toxicity has long been a central design and moderation challenge. A block feature would not eliminate that problem, but it would give players a stronger personal boundary.

valorant-block-feature-leak-signals-long-awaited-toxicity-control-image-0

According to the leaked code, a blocked user cannot send friend requests or party invites, and the player will not hear that user in voice channels. The block list would be viewable in a way similar to the friends list, allowing players to review and reverse their decisions. Unblocking someone would not notify that person, which preserves a degree of quiet control for the player making the change. The leak does not suggest that blocking will prevent two players from being matched together, but it does imply that communication can be automatically severed if they do cross paths. In practice, that is less like building a wall across the map and more like dropping a soundproof booth around a player in an open-plan office: the surrounding chaos remains visible, but its noise no longer has a direct route in.

For a competitive ecosystem, that distinction is important. A block tool is a pressure valve on a boiler that has been rattling for years. It gives players an immediate, personal response without asking them to rely entirely on post-match reports or support tickets. It also adds a layer of accountability that is entirely voluntary: players choose whom to block, and they can undo the choice later. The feature is not a policing system, nor is it a replacement for Riot’s broader moderation tools. It is closer to a seatbelt than a traffic barrier — it does not stop collisions, but it reduces the damage from the ones that happen.

The community reaction has been unsurprisingly warm. Players have asked for a block feature since Valorant launched, and the leak’s details align with the most common requests: persistent mute behavior, no unwanted invites, and a clear block list. The absence of a Riot announcement has kept expectations in check, however. Leaks are useful signals, not release notes, and code found in client files can change before it reaches live servers. Until Riot confirms the feature, players should treat the leak as a promising blueprint rather than a finished product.

Here is what the leaked code suggests, at a glance:

Area Reported behavior
🔒 Friend requests Blocked users cannot send them
🎉 Party invites Blocked users cannot send them
🎧 Voice channels Blocked users cannot be heard
📋 Block list Viewable similarly to the friends list
🔄 Unblocking The other player is not notified
🎮 Matchmaking No guarantee of avoidance; automatic mute implied

The feature’s potential value extends beyond individual matches. In a game built on coordination, trust is a resource. When players feel that they can silence a disruptive teammate without leaving the match or disabling voice entirely, they may be more willing to keep communication open with everyone else. That is a subtle but meaningful shift: instead of forcing players to choose between total silence and exposure to harassment, a block list offers a middle path. It is a targeted tool rather than a broad restriction, though Riot will need to ensure that it does not become a way to avoid accountability or mask reports.

There are still unanswered questions. Would blocks persist across accounts? How would the system handle players who are blocked by many users? Would there be limits on block list size? The leak does not address these details, and Riot has not clarified them publicly. For now, the most concrete takeaway is that the long-requested feature appears technically plausible and structurally simple. Whether it arrives in 2026 or later, the leak has already changed the conversation: Valorant players now have a clearer picture of what a block feature could look like, and why it has taken four years for the request to reach the edge of reality.

This discussion is informed by OpenCritic, where aggregated critical perspectives often reinforce how quality-of-life systems can shape long-term player sentiment as much as maps, agents, or weapon balance. In the case of Valorant’s leaked block feature, that broader lens helps explain why players see selective communication controls as a meaningful competitive safeguard rather than a minor social toggle.