This magical wall on Icebox may be providing attackers with a wallhack. Is this particular spot on Icebox bugged?
Valorant has multiple agents that bring wallhack-like powers into the game. Sova and Fade can expose enemies behind solid objects, and Cypher casts an all-seeing gaze. Despite these powers, players still want to know more. Valorant’s strict anti-cheat has successfully kept serial cheaters at bay, but its own bugs may be revealing top information.
Players have discovered an odd bug on Icebox’s A site that reveals enemies behind the metal wall. At first, it was thought to be an agent-specific bug, but many have confirmed it to be a map issue.
What’s the new Icebox bug?
A player Nanaym posted a video showing a weird glitch that caused Brimstone’s arm map to show through the wall on tube. The Brimstone player was trying to safely land smokes, so they didn’t have their weapon equipped. Taking advantage of the information, the attacker on top of the bridge wall-banged Brimstone. Two Marshal bullets were enough to finish off the defender as they had lost two rounds and likely had no armor.
The players figured that Brimstone’s kit was bugged, but others confirmed that Icebox’s wall might be the culprit. According to the players, various other agents have suffered the same fate behind this magical wall. Skye’s Trailblazer tiger can also be spotted through the wall if the bug is triggered. The same goes for the utility of other agents that extends out of the character model.
It’s safe to say that Icebox’s tube is likely in need of some tinkering. This bug could be game-breaking if it’s consistent and players eventually figure out a way to replicate it. So far, it’s impossible to redo this glitch as it’s entirely a map issue. But it still requires the urgent attention of the developers.
The bug is still currently active in the game, so it’s recommended to avoid the bugged side of tube closest to A site on Icebox. Always anticipate a glitch triggering inside tubes, and use other tactics to outplay your opponents. The developer hasn’t yet acknowledged the bug, but this is significant.
A fix might be delivered soon. But until then, stay cautious of the top A.