Original Post — Direct link
18 days ago - /u/RiotTuxedo - Direct link

Originally posted by Smallzfry

Is that date a typo? Should it be September 11th, or is that saying August 11th for next year?

Also, the reason I stopped using the built-in match history page is because it stopped working years ago. It then took long enough to fix that I (and my friends) got used to using op.gg instead. Just like Dominion and Twisted Treeline, this seems like it's just being removed because Riot neglected it to the point that it can't be salvaged easily. I really don't like that everything is being moved to third-party tools, but I guess I see the reasoning when there's good drop-in replacements.

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

18 days ago - /u/RiotTuxedo - Direct link

Originally posted by playhacker

On Aug 11th around 10:00 AM PST, the League Web Match History site will be permanently taken offline.

August 11th of next year??

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

18 days ago - /u/RiotTuxedo - Direct link

Originally posted by Abarn279

OK nobody is talking about this but this is a BIG issue for anyone who runs amateur leagues in customs. Client match history only goes 20 games back and the web match history is currently the ONLY way for you to pull history for your own customs. opgg does not work for this as the riot Api doesn't support pulling custom games for a player

Cc /u/RiotTuxedo

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.

17 days ago - /u/RiotTuxedo - Direct link

Originally posted by Abarn279

Any idea why y'all scrub custom games of usernames and such when regularly quieried by game ID? Is it for the purpose of hiding things like scrim results for high level play, and it just happened to trickle down into everything else?

I run an amateur league that doesn't use tournament codes so I put together this janky-but-solid solution that takes in match ID's with metadata (mostly player names associated with each position), grabs the private game data using match ID, and massages the two together:

https://github.com/Abarn279/tcl-data-aggregator

Obviously the real answer to this is implement the tournament code API, but it still doesn't fix the issue of not being able to pull up old scrim results and such through customs without a 3rd party implementing oauth

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 they shouldn't be secured at all (like we've done with customs made with tournament codes).

17 days ago - /u/RiotTuxedo - Direct link

Originally posted by TreeKeeper15

Why is the match history website being taken down when it provides more information than the client? Some things, such as build order, are only online, and that sucks.

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.

17 days ago - /u/RiotTuxedo - Direct link

Originally posted by Sp00ky_Senpai

This is small, but: with no way to copy/paste from client, the online match history was the best way I knew to scout people with funky characters in their name in clash, since I don't know of a way to highlight and copy text in the client. You'd find one of the games in their clash history, view that game in the web match history, and then you'd have actual text you could copy over into opgg or whatever.

Does anyone have other ways they handled this? If it's the first game of the night and the person with funky characters isn't in someone else's match history, I'm not sure how we're supposed to scout them.

/u/RiotTuxedo I know this probably isn't your department, but if there isn't an easy solution I'm not thinking of, could you pass this concern to the clash people? just being able to copy names from the scouting screen would be a huge help.

I'll pass that feedback along. I'd also suggest googling and searching for a Clash tool if you're looking for scouting info. There's several sites that do this and you'll want to find the one that you enjoy, but if you don't already know of any I'd check out https://www.lolvvv.com. I remember talking with them when they were iterating on their Clash tool they seemed to be pretty passionate about Clash scouting.

17 days ago - /u/RiotTuxedo - Direct link

Originally posted by Jinxzy

Hey /u/RiotTuxedo, just to be sure: This is just the matchhistory site being shut down, but the ACS API will still be functional?

After Monday, Sept 13th ACS will no longer ingest new match history and will effectively become read only. It may stick around a bit longer than the match history website, but it won't include new data from live shards. If you're a developer, you should move to match-v5 in the Riot Games API. If you're using ACS for pro matches that data should be obtained from Bayes.

17 days ago - /u/RiotTuxedo - Direct link

Originally posted by Darkshiek

What are the best places to follow for updates on the League APIs? I run a website for an amateur league that uses the game IDs from custom games to keep track of all of our players' stats and such. While I'm going to spend the next week or two trying to pivot towards the tournament API, but being able to use custom games as a solution was nice for us as it was so lightweight. If a captain wasn't able to make it to a game, someone else could still make the lobby, if someone entered the game wrong (wrong player/role/champion), we could go back to the official match history and see what actually happened. There's quite a few useful things going away with this update.

Tagging u/GitGene here. He's in charge of the comms for the Riot Games API. I believe the best place to follow for updates is the Riot Games Dev Rel Twitter account. There's also a community managed Discord server and usually they are up-to-date on any changes coming to the API.

17 days ago - /u/RiotTuxedo - Direct link

Originally posted by cdillon42

so in reality this means, "why should we pay people to do this, when the community will do this for us for free" RIOT Games.

I can definitely understand this perspective, but I definitely don't share this point of view for a couple reasons.

  1. There are areas that Riot is uniquely positioned to solve. Player Behavior systems are one example. We've seen community developers create products in this space and we generally discourage it. Replays were originally a community endeavor but they weren't positioned to create a quality product (a lot of the community solutions were hacky). Players asked for this repeatedly and Riot was uniquely positioned to provide a reliable solution. A web based match history product, in my opinion, doesn't fall into this category. Other Rioters have talked about this before, but when resources are limited you have to focus your attention and our focus is typically on problems Riot is uniquely positioned to solve.
  2. This is mostly my opinion, so I wouldn't say this is Riot's opinion or the opinion of my colleagues: Riot is a video game company as opposed to a web design company. The websites we do run are typically one of these problem spaces where we're uniquely positioned to solve; publishing (lol.com), account management, player support. Match history isn't a problem space where we're uniquely positioned to solve and the core requirement is having some form of match history in the client. If players feel the client match history is subpar and that's the reason a match history website is needed, I'd say that's feedback for the client. We do believe match history should be available out of the client, which is why we provide the Riot Games API and have worked to include match history in the League+, soon to be, Riot+ mobile app.
  3. Over the last couple years we've worked to enact policy to allow community developers to monetize their products in player friendly ways. This is specifically so community developers can get compensated for their efforts. I'm not going to pretend this is perfect and every community developer is making bank. There's plenty of work to do here, but our goal is to support community projects that are player focused and are valuable to players.

Obviously, you don't have to agree and in fact I appreciate players being critical and holding us accountable. Keep us honest.

17 days ago - /u/RiotTuxedo - Direct link

Originally posted by cdillon42

i also understand where you are coming from but coming from halo 3 days, bungie had a website for match history that was awesome (sometimes buggy) but it worked well, so to me using the excuse that you guys are a game developer just irks me. lasted i checked (a year or so ago for some nostalgia :'( ), the match history is still up.

the thing i don't like about 3rd party developers is that they need revenue from somewhere and that revenue comes from ads. some of those ads are pesky and intrusive.

also, thank you for the reply

Now you're speaking my language. Grew up with Halo. I also loved their website. Heat maps. Medal counts. Bungie really did a great job and set the bar super high. When I look back on that whole product it feels like an outlier. There weren't a lot of web experiences that Bungie provided apart from that. I'm assuming they decided this was an important core player experience that they wanted to provide and specifically wanted to make it available everywhere and not just in game.

When I look at our match history, at least the web part doesn't feel like a core part of the experience and we have other methods which we're using to make this data available out of game. Even today what 10 years later? I think the Bungie website is still the gold standard for web match history. I think there are some community websites that are close if not on par with Bungie. At least right now creating a great web match history experience isn't a priority for Riot. Bungie did a lot of things right and I think Riot just has different priorities typically focused more on the in game and client experiences.

As for the ads being pesky and intrusive this tells me we need to do better supporting community projects (which we knew, but that's how I'm parsing your feedback).