League of Legends Dev Tracker

Have you noticed if you crash after you’re clients been running for a long time or are you seeing this after starting up and playing a game or two

Hello, I just poked the team working on this;

re: account transfers - They have uncovered more problems are originally anticipated, but the good news is that they are actively working on it and should be available soon. The bad news is I don't have an exact date to share.

I would love to be in a position where we are doing new features or enhancements. The team's mission is to make the client more performant and reliable, and we are not there yet. We have made really good progress, but we have a good amount of work to do until we can say we are happy and met our mission.

Okay, pull request incoming.

Addressed in a different reply

These are all good feature requests to enhance the collections tab. Unfortunately, the team's primary mission is to make the client more performant and reliable. We are not there yet, but as we move closer, we can look to introduce feature enhancements, we just can't commit to them until we are happy with our client improvements.

Hey! This is an answer from one of our engineers, not me :)

• This is an interesting question, and one possible explanation is that differences in network conditions, regional services, and the state of a player's account can all play a part in bugs that show themselves in the client. In the best case, the client has a way to handle a downstream issue and degrade the experience gracefully,  but there are also times where the edge case isn't covered, which is something we continuously look for to patch.
• For work? JavaScript. For fun? Rust is pretty cool.
• Cloud9 has always been a favorite of mine
• I don' think there is a date set for this, or whether the LoL dev team has finalized the plan around any sort of transition. Stay tuned. If or when this happens we will communicate it broadly.

The question - Why should we be forced to re-evaluate our opinion on the rune edits.. not once, but two times ["Save > Yes/No"] instead of it being auto-saved immediately after the edit?

The player that is opening Rune pages is doing so with intent to edit or just check the current selection. It should be logical that the game auto-save any edits done while the runes are open since your sole purpose of opening it was probably to "edit" the selection. This would also allow us to easily switch between different pages without being forced to save previous edits.

Hello, I just poked the team working on this;

re: account transfers - They have uncovered more problems are originally anticipated, but the good news is that they are actively working on it and should be available soon. The bad news is I don't have an exact date to share.

The major difference is being implemented with game engine technology vs web technology, for the most part. This allows for all the optimizations and standards that make the game run smooth to apply to the out-of-game experience as well.

I went into a fair amount of detail as to where League's on that in a different reply.

Right this isn't me saying that we were actually working on one, just that it could be pretty cool to do

I would like to know too.

u/Am1t8 when? #RitoPlease

We need more engineers, they are hard to find, send them our way:
https://www.riotgames.com/en/work-with-us/jobs

Hi, my friend and colleague penrif gave a good explanation above :)

https://www.reddit.com/r/leagueoflegends/comments/ldd2am/league_client_team_ama_about_the_client/gm5c0nl?utm_source=share&utm_medium=web2x&context=3

anything you desire!

wont be able to dodge karthus ult either

Thanks for the question! This is a deep one and is going to take a bit of history, so let's go for a little walk.

League, since the very beginning, has had two pieces of client software - the out-of-game client and the in-game client. For brevity, let's just refer to "the client" as the out-of-game one - the in-game one isn't what this AMA's about. Originally this was implemented on top of Adobe AIR, and went through a major rewrite a few years back, implemented on top of web technologies.

This split is not something that many games do. I struggle to think of an example really - the vast majority of games, including the other ones Riot makes, implement their out-of-game experience in the same piece of software that the in-game experience is delivered on. This has a lot of benefits, but the biggest of them is that the same experts that are tasked with making the in-game experience snappy and responsive can apply the same techniques to the out-of-game experience....

Good question, I am fairly new to the team, it will be one year In May!

One thing I wanted to do when I started on this team, I wanted to get a survey out globally to get a measure of sentiment around the client (you may have gotten it). This gave me a good idea of what we should work on in the second half of the year, which was champ select and End Of Game, since players reported issues with those two the most. As we implemented fixes over the past 5 months, we have seen really good trends in these survey results.

For example, the % of players who are very/somewhat dissatisfied with the client when we launched the survey was 50% in Brazil, North America, and South Korea. We are now trending towards below 40% for those three regions combined, which is a really positive trend, but we still need to do more to continue to move in the neutral/positive direction

We have also made good trends in month-over-month sentiment, with more people saying the client has i...

See this answer, happy to elaborate more if you would like.
https://www.reddit.com/r/leagueoflegends/comments/ldd2am/league_client_team_ama_about_the_client/gm59rgc?utm_source=share&utm_medium=web2x&context=3

honestly it probably wouldnt be that bad

A lot of the issue players see in the client are inconsistent at best, due to many factors like hardware, connection (yes, sometimes it's lag), antivirus software, and other programs a player might have installed. The things we can get accurate repro’s for are the things we can start fixing (depending on the severity of the issue). Depending on the type of work we do during a given patch we will run focused testing along with regression testing (full sweeps of the client) on the areas we specifically touched. At the end of each patch we run what we call an exit sweep to make sure everything in the client is working as we’d expect.

Something to keep in mind is that not all bugs are seen the same. If something is ear-flicky, that bug might sit on our backlog longer due to us prioritizing more critical work.

We try to upgrade to the latest stable version. But that it isn't always possible within a reasonable amount of time.

For example, the last time we upgraded Chromium we wanted to go all the way to version 80+, but had to settle for 74. On 75, some core APIs changed and upgrading our code would delay the upgrade for a couple of months. Since then, as we do other work, we improve the old code knowing that another upgrade is imminent.