Valorant Now Has Yet Another Agent Glitch, This Time With Sova

Valorant has been one of the top names in the entire roster of tactical FPS titles. This Riot Games title will be entering the global championship scene next year, and we expect it to rise to the stature of Riot’s iconic MMORPG League of Legends soon. However, it has had its fair share of glitches and issues, sometimes even game-breaking ones.

Further reading: Counter-Strike: Global Offensive- Fnatic Pro Krimz Receives VAC Ban But the Reason is Clouded in Mystery

Recently, Twitch streamer Average Jonas posted a tweet showing a glitch that he experienced in the game. Due to this glitch, Sova’s arrows seem to travel through walls instead of bouncing off them. Jonas found this out this glitch in a custom match. In the tweet, he called out to the devs at Riot, asking them to double-check this.

“Hey, @PlayVALORANT @riotgames I think I just broke your game.. Might wanna doublesho.. I meant doublecheck this!“

Now, looks like this issue is not a widespread one yet since other players have not reported this bug. However, devs should look into it before it becomes a persistent issue.

Further reading: With the Return of Tfue, Nickmercs and Before the Galactus Event, Is Fortnite Back To Its Former Glory?

Agent bugs are still on the rise in Valorant; After Killjoy, Sova has taken the place

Those who play the game on a daily or those who are aware of the recent happenings in the game, know of the recent Killjoy bug in Haven. Due to this bug, players can place Killjoy’s turret inside walls (yes, you heard that right). Therefore, the turret will be shooting enemies as soon as it detects them while staying invisible.

Since it is inside a wall, you will not be able to damage it, providing an ultimate line of defence, while the user keeps getting a couple of free kills for as long as the turret is active. While some players have come with a way to counter the Killjoy glitch, devs have not fixed it yet.

However, given the past record of Riot Games, the devs will surely fix it in the upcoming patch cycles. At least, we hope that is the case.