The next major Valorant update goes live later today (early morning tomorrow for EU) and will bring us a brand new map and rank to compete for!
In Episode 5, Act 1, the majority of the update will follow a more traditional format with tweaks to various aspects of gameplay, agent abilities and weapons.
Here's everything you need to know about the Valorant 5.0 update for when it's live in just a few hours!
Don't Miss: Discover Razer's Ultimate Gaming Laptops Now
Valorant Episode 5, Act 1 Release Time
We were initially expecting Valorant Episode 5, Act 1 to drop around 6 am PST / 9 am EST / 2 pm GMT on Wednesday, 22 June. The date is confirmed but it now appears that the update will take place at 11 pm EST / 8 pm PST and at 4 am GMT. This is according to the timer that appears in-game confirming the end of the competitive queuing for Episode 4.
This is a fairly standard pattern for updates now so there are no changes expected to come but if it occurs, we'll keep you updated!
Valorant Server Downtime
Valorant servers are expected to go down while Episode 5 is made live. This could last anywhere from 30 minutes to a few hours. It all depends on whether Riot servers play ball and how large the update is!
Queues will also be expected once the servers go live again as players attempt to rush back into the game and get playing.
New Valorant Map & Rank
The two big talking points from Valorant Episode 5, Act 1 will be the new map - Pearl - and the brand new rank - Ascendant - which will be live in this update.
The new map will even have its own playlist for two weeks before it enters the competitive map pool.
As for the new rank, Ascendant will enter Valorant above Diamond but below Immortal as a way to better balance the competitive game modes.
Stretching the ranking system should offer better matchmaking experiences across the board.
Going too far with adding ranks may make it harder to find truly fair games, but players have been actively campaigning for this new rank to level the playing field for some time. Hopefully, this is the answer to the issue!