Valorant Dev Tracker

We balance around pro play and matchmaking separately - if Sage needs some buffs on the pro side of things, we can do that.

The reality is that Sage has been substantially stronger than any other agent in the game by a wide margin since closed beta, while also having an absurdly high pick rate compared to any other agent. If she ends up being too weak after these changes, we’ll ship some buffs to get her in the right spot.

We're currently investigating this. As mentioned in thread, downloading the latest redistributable from the microsoft website will resolve. We're working on getting it fixed in the patchline for those experiencing it. !pin

None announced, but it's being actively worked on. We'll hopefully be able to give a solid ETA soon.

The patch right before break was massive--Killjoy, deathmatch, and act ranks

You’re prevented from rescoping for the duration of the concuss

Your FPS example is close to what I intended. If I were to make a 20ms task take 10ms I would see that as a doubling of performance (100%) not a 50% increase in performance. You can do double the amount of the work with the same resources. I can see how this is confusing the way I wrote it. Sorry and thanks for trying to explain it.

We do monitor server tick rates on LIVE using the same data I show in this chart. For the vast majority of servers in we see a steady 128 tick rate. We do have a problem where on round transition the server takes a long time to setup the initial frame and spawn everyone in. That's usually when you'll see low server FPS show up in the top right.

You can actually see server tick rate in your game if you go to Video -> Stats -> Server Tick rate. You can see a graph of server frametime in realtime. It's generally a boring straight line. There are specific regions and specific data centers where they ran hot for periods of time and start to dip but we're constantly adding hardware as it's available and the player base grows.

The more common "server problems" tend to stem from networking outages on the route from players to our servers and complications that cause dropped packets or significant increases in network latency. The network graphs also exist in the settings me...

Thanks for the kind words everyone!

It's been a wild ride this year but what I'll remember most from my Valorant journey is the support and enthusiasm from everyone in the community, it's made this year a really special one (good special, unlike all the other kinds of special that 2020 has).

I'm confident in the future of anti-cheat on Valorant, there's a whole team of talented people that are working on hunting cheaters, improving Vanguard and generally fighting the good fight. They're talented and hard working and I'm going to miss them a lot!

This was a bug and should no longer be occurring. You can queue up as 5 with a total disparity of 6 from highest to lowest member (IE Silver 2 -> Plat 2)

Hello! This was a bug and should no longer be occurring. You can queue up as 5 with a total disparity of 6 from highest member to lowest member (IE Silver 2 -> Plat 2)

Glad you enjoyed it!

The servers that host games are a pretty simple tech stack. We deploy a single docker container that contains a go service that communicates back with the core game services that manage matchmaking players. The service just starts game server processes (which are written in C++ using the Unreal Engine).

You can read more about how the entire backend is developed and deployed in this series of tech blogs if you're interested. https://technology.riotgames.com/news/running-online-services-riot-part-i

In terms of performance, it didn't affect us much. I mention t...

Sorry if it was a bit much. I tried to ride a fine line of saying something meaningful and accurate vs being overly technical. In terms of cooling/power we don't really have many special requirements. I initially was concerned more about it but the actual power draw (and heat generation) wasn't even measurable in the test cases we looked at. I'd assume it has something to do with the way the power-supply / board draws power but I'm not certain as it's not my area of expertise.

Another thing to consider is that if we can reduce the number of hosts we even need to rack by tweaking, we can reduce overall power draw and heat generation of the data center.

A group of us are talking this week about process changes to enable doing more of these smallish quality of life changes. They're not big ticket features but their values adds up fast and we want to be better at delivering more of them regularly.

I maintain a list based on feedback and analysis and it's easily 75+ line items. We want to start checking them off!

I know there is some exploration being done around options for latency and data centers . I don't know the exact nature of the work or where it'll end up, but it's an active topic of discussion and effort.

We have a task to freeze the map until you close it. Not sure when it'll happen but it's pretty small so hoping to squeeze it in sometime soon.