You’re not alone in whiffing unbelievably easy shots on Bind’s Hookah. The map has a secret glitched spot that everyone should avoid.
Valorant is the latest cut-throat shooter game but it has its fair share of bugs and glitches. Fortunately, the developer is quick to take notes and patch them up. However, some bugs are too subtle to get hotfixes. They go unnoticed on lower levels of play but are game-breaking on high ELO games.
This newly discovered bug on Bind has remained a part of the game for a long time but is only coming into players’ attention now. The map’s Hookah is inapt for aim fights, as it triggers a random pattern of bullets in weapons.
Hookah is one of the crucial duel areas on Bind. The narrow area sees tons of actions due to being the main point of entry into point B. The elevated window is designed to favor the defenders who get a clear headshot angle and can also hide under the entry. Attackers often tackle the odds by boosting themselves on the corner boxes of Hookah that happen to be glitched.
Attackers have lost tons of aim battles in Bind’s Hookah, and it turns out that not all players were bad aimers. Players perched on the boxes would always fail to land their bullets accurately, as the crates are bugged to spiral your spray out of control. The issue was observed by various Valorant players. Further testing proved that it’s a consistent game-breaking bug that can’t be fixed with accurate sprays or even one-tapping.
All weapons failed to land the bullets on intended spots despite extreme spray control and dragging down of the mouse. The bullets would randomly fly across the little area. There’s no way to tackle the glitch, as bullets fly around in a random pattern. All weapons including Vandal, Phantom, Guardian, Operator failed to beat the bug, proving that losing aim battles from crates is warranted.
The bug is currently active in the game so it’s recommended to avoid taking aim duels in Hookah. Try to stay away from the corner crates, and use other tactics to outplay your opponents. The developer hasn’t yet acknowledged the bug, but this is a significant one.
A fix might be delivered soon. But until then, stay cautious of the boxes.