Valorant Dev Tracker

To start, we don't balance our ranked distribution based on what League is doing or their system. While I do talk with their designers, the Valorant team believes in the decisions from my team to do what we believe is the correct distribution for Valorant.

There are two outcomes I'd like to hit when setting our ranked distribution:

1.The community can start to paint a picture of skill related to that rank; "That was a Gold play", "That player has the crosshair placement of a Bronze player", etc.

2.Climbing ranks feels like you've increased in skill to get there, and by getting better at the game that rank increase feels meaningful. This prestige can also be seen in the population % of each rank, especially at the high ranks.

So with the above goals in mind you have to decide on 1 of 2 ways to balance your distribution:

1.You balance based on MMR, so every rank is even. For example; Iron = 500, Bronze = 600, Silver = 700, Gold = 800, etc. Beca...

I don't understand, this is just a picture of Jett's game art ;)

Any system is just trying to measure your skill against someone else, because the first step of creating a match is being able to find two similar skilled opponents/teams. There are lots of systems that actually don't look at Win/Loss and only care about performance like KDA(just depends on the game).

A Matchmaker's goal is to find a way to measure player skill and ensure fair matchmaking. You do this by figuring out how to measure players(This is MMR in most systems), then have the match maker guess the outcome of a match(the higher MMR team should win). It doesn't matter if MMR is based on performance, or win/loss, or even total money earned, etc. You want to find the thing that will predict player skill, or the match outcome, the best.

If you were to just measure win/loss, and create a win/loss MMR, then you go back and check at how often a team with a higher Win/Loss MMR actually wins, this is how to measure if your MMR system is working. If you make a system wh...

If you have good data scientists, and know the goals of what your system is supposed to do, it isn't too complicated. We have people who have dedicated their careers to match making and rating systems, or people who are just amazing mathematicians. Games have been working on match making for a while now, and you have systems like True Skill 2 which can detect way more than players even realize. Highly suggest watching a GDC talk by Josh Menke to learn more about this space if it interests you.

You can see a comment I made on this deeper in the thread: ...

TECHNICALLY if you wanted to try to calculate missed or faked ability usage:

You could bounce a couple traces around corners, or check to see if an ability was in the eyesight of an enemy player(so they looked at the ability means it effected their judgement), then look to see if they moved from that spot, were dealt damage, etc. There are some other ways as well, but our system does not take into account fake abilities because there would probably be a large false positive % to them.

All hypothetical, but it probably isn't worth the work in the long run to determine fake or missed abilities.

As for a system that can determine ability usage, that's pretty easy and our system does do this. You could look at any ability, how many people it hits, what it is doing, etc. and figure out its impact. I'm not going to talk about how we do this, or how the systems evaluate abilities, but every ability could technically have a measurable % it helps win a round or get a...

Interesting. I'll forward the comment over to the team that handles that, and it's good to know in the context of game consistency. Thanks!

Hey, thanks for the post. The team that handles hit reg reviewed the footage.

This article has some great background on the topic.

What's happening in the video is definitely not what you should expect to see under normal conditions.

It raised some eyebrows that ping and packet loss look fine here (love to see those readouts turned on), since that causes the vast majority of issues like this.

In this case, the behavior exhibited still does indicate that there's SOME kind of issue in the network connection, but it's not clear what that issue is. I could speculate on a few things, but they'd just be guesses, so I don't want to be misleading.

That's not a sa...

As a Raze main, f*ck

All ranks got squished, even previous radiants started Diamond 1. Soft resets push all ranks down, it helps prevent inflation or players who get boosted and sit higher than they belong.

We also made adjustments to how your MMR is calculated which caused movement in ranks and where people belonged. This is because we pulled out a system that weighted MMR based on number of games played.

Episodes are about 6 months, you'll have plenty of time to improve and get back to gold if you choose to.

Well, maybe you can explain me why every match doesn't end up close. Then why is there in every game 1 player performing utterly bad. Why do I get matched with 2nd or 3rd accounts who doesn't take ranked seriously.

Lets look at your matches this act on this account: https://tracker.gg/valorant/profile/riot/Omen%23diff/matches?playlist=competitive

You've played 25 matches 19 out of 25 matches ended in 13-6 or higher. That means only 6 of your matches, out of 25, would have been considered "One Sided"(by how we measure games internally).

Even if you increase that to 13-8, 12 of your matches ended at or above...

This is awesome! I'm an engineer that worked on loadout equipping and validation. It's really cool seeing players leverage the client API to build their own features. Past suggestions I've seen have mostly revolved around having preset loadouts (for example a loadout for each agent), which is relatively more expensive to build. Seeing interest in straight up randomized loadouts (which is much cheaper to build) is exciting. I'm personally excited for any opportunity to play with more than one skin forever.

Ban / No Ban Update: Using the client API to modify loadouts does not seem ban worthy. The client API isn't officially supported for third party use, so don't expect future compatibility.