Valorant: How patch 1.02 bugs have postponed ranked matchmaking

Image Credits: Riot Games

If you were eagerly waiting, since the game’s official launch, to finally try out Valorant’s ranked matchmaking feature, then unfortunately, you will have to wait a little longer.

Patch 1.02, which was quite a big update and brought with a lot of changes, has also been plagues by some game-breaking bugs, which are ruining the matchmaking experience.

Because of these bugs, Riot Games has disabled ranked mode across all regions and will be relaunching it once they patch them up, which might either be tomorrow or later this week.


There are primarily two bugs which are affecting Valorant at the moment

1. The bug that makes you spawn in the enemy base

Yes, you heard us right, there is currently a bug in Valorant which has been making players spawn in the enemy base once the round ends.

Valorant’s game director, Joe Ziegler, took to Twitter yesterday to say that the devs have discovered a bug that makes players “every once in a while spawn in the opposing team’s spawn point.”


2. Ghost mode during normal matchmaking

‘Ghost Mode’ is a feature in Valorant which is only allowed in custom games, with the cheats feature on, and allows players to fly to any place in the map and even go through obstacles.

This mode also seems to have accidentally become available during a public unrated game, especially to those players who have had their ghost mode feature bound to a hotkey.

A Reddit post by DisciplinedPenguin points out his experience with this hotkey bug. “I just hopped onto a game and pressed c by accident, turned me to ghost mode, worked for other people too. Pretty game-breaking bug, hope it doesn’t [sic] delay ranked.”

This bug is perhaps even more problematic than the first one. However, it seems that the Riot devs are aware of this issue and will be patching out a fix as soon as possible.


In a tweet, Valorant executive Anna Donlon wrote:

“This morning we decided it would be cool to let players fly around the maps to see the changes we made. JK, it was a bug caused by ongoing refactoring of how observer slots work. Code is weird sometimes. Fix was quickly identified and deployed. Thanks for putting up with us.”