RiotTuxedo

Over the years there's match history website has suffered from a lack of strong ownership resulting in a lot of bugs that never really get fixed. In my mind, there's two possible solutions: 1) we decide this product is super important to the player experience and prioritize maintaining it over other opportunities OR 2) we decide community developers do this better than we do and we get out of the business of maintaining products that community developers have done and will do better than we could.

I'm a huge advocate of APIs and sharing data and in my mind giving this problem space to the community is what's best for players. Basically I believe in competition and I think a community of developers competing to build the best match history website will result in some kick ass tools for players. Not just now, but in the future as new developers enter the space and try to outdo their predecessors.

In general, custom games are considered private. The old system which allowed custom games to be viewed if you knew the game id is a poor security practice which is typically referred to as security through obscurity. In essence, we allowed people to view custom games if they knew their id but if we truly consider custom games private we should properly secure them. If players believe customs games shouldn't be private, then the...

We're also looking into solutions that will allow players to query for their own private custom games with OAuth tokens through the Riot Games API. These are tokens unique to a player which allow us to ensure a player is looking up their own match history. This solution is something we're looking into but wasn't a requirement for deprecating web match history. In the interim, the tournament code solution is what should be used to create public custom games.

I believe this should be Tuesday, Sept 7th Monday, Sept 13th. The article should be updated soon.

I believe this should be Tuesday, Sept 7th Monday, Sept 13th. The article should be updated soon.

Our goal for the initial launch of the VALORANT API was to ensure a level of stability while also ensuring that players have access to tools powered by the API. We accepted submissions from the community leading up to the launch and then carefully sifted through those applications to chose a group of applications to be part of the initial wave of access to the API. As you pointed out, it feels bad that not everyone got access all at once but we wanted to make sure those that did get access had enough resources to make something cool while also ensuring that the API remains stable.

Specifically, I'd like to clarify two things:

1. The initial wave wasn't chosen based on wealth, but rather compelling concepts and the ability to deliver on those concepts.
2. We do plan on granting access to more products in waves so we can continue to ensure the stability of the API.

If you're interested, there's a discussion going on related to this in the ...

Depends on if you're closer or further from the angle in relation to your opponent.

If you're closer to the angle, you're at a disadvantage so quickly wide peeking is the best way to negate this advantage because your opponent will see you before you see them. This is the suggestion in the video.

If you're further from the angle, slowly peeking means you'll see your opponent before they see you. This is the example I gave.

I'm so happy that others have found this to be helpful. I remember when I first realized this, it figuratively blew my mind. I've played differently ever since. Now if I could only get good at clicking heads.

:(

AYAYA

Yep my team has been talking with developers interested in the space and we're working with the VALORANT team to expose a set of APIs for the game. No timeline on this yet but it's looking it'll be post close beta. There's a lot of work the VALORANT team has to do before launch.

All developers are given a development API key when they sign up so they can explore and experiment with the API. However if you're building an app that gets used by players, we require developers to register the product (and stop using the development key). Once a product is reviewed and there are no concerns, we grant a production API key that remains static. Some developers were skirting our policies and registration process by making requests with multiple developer keys. Expiring developer keys after 24h makes this approach less feasible.

In the last example, Viper is holding the close angle and Jett is peaking with a pistol. Jett can see Viper before Viper can see Jett because Jett is further away from the edge. Each has its risks, the slower you work you way up the more exposed you are from your left (from A site) but you can beat someone holding a close angle if you slowly check it from a farther angle. Hope that makes sense.

Not necessarily. There's always reasons to peak and smart ways to do it (with a buddy or with utility). If you're going to peak long C, I'd say don't do it slowly because the person holding the long angle will see you before you see them.

I don't know definitively. I don't work on VALORANT, I work on the Riot Games API. I just posted this cause I've seen some people confused about how someone shot them when they couldn't see anyone. Maybe a member of the VALORANT team will swing by and let us know :)

I noticed this right after I posted it /facepalm

For anyone else wondering, farther for physical distance and further for metaphorical, or figurative, distance. As in, if this gets noticed any further I'll get even more embarrassed xd

Oh hello Reddit! Glad y'all are finding this useful. I've got some examples in the Twitter thread if anyone's interested how this looks in game.

https://twitter.com/RiotTuxedo/status/1250637504895541248
...

Thanks for understanding, but keep up the good fight. Priorities are based on what player's want so the more people want all content localized for every region the more likely it'll happen. Don't let me discourage you, but now you know why I work on helping third-party developers. The dev community does some great things for players.

/u/HOUNDfre as for your edit,

edit: can you actually explain why is it such a resource-draining job when third-party apps can already do this? I understand that no way im getting an honest answer here but whatever, asking doesn't hurt

There's two sides to this. Why can third-party apps do this and why does it take a lot of time for Riot to do this correctly. When a player modifies their own client, either by themselves or via a third-party app, then the changes are localized to them. If the client breaks it only affects them and they can easily just re-install the client or remove the app. If we do this and it's done poorly, it'll affect millions of players.

Now we're wandering into territory that I'm not the subject matter expert (sme) on so some of what I say ...

To my knowledge, the solution to this problem isn't as easy as enabling the option to select any language in any region. An implementation of this done poorly, could make the whole client experience worse. So from my perspective, it's either we leave it how it is or we commit to doing it the right way which will take more time than we can spare.

I understand that this is something that players want, which is why I came into this topic originally to say if you modify the client to enable another language it's unlikely you'll get banned. However if you download a program to do this for you and the program does something shady, you're also risking getting banned so exercise caution.