Am1t8

You are right, we are making one of our success measures on reducing memory leaks, not only in champ select, where we will start, but all over the client.

This is something I am considering, would live to share the technical details behind our work.

Can you direct message me the exact issue (report steps if possible), I can have the team look into it, thanks!

I will have the team look into this, definitely an annoying bug.

This is something we plan to tackle in the coming months! stay tuned!

Thanks for the feedback, and yes, while working on champ select, we will also be working on making improvements to the end of game experience

Fair question;

We had to start the year cleaning up our plugin architecture before we can unlock performance improvements within the client (we still are working on the architecture cleanup). We wanted to pick a KPI (improve client bootstrap time for a majority of our players globally) so we can track our success to players.

The survey was an independent exercise we ran to understand the biggest pain points around the client globally. Some regions actually wanted to see an improvement in bootstrap time, while others had more frustration around champ select and end of game. Using this data, we can make decisions on what we want to work on that will improve client performance and reliability for all our players globally. To measure our success, we want to see the frustration trend downwards, and now we have data that tells us if we make improvements to champ select and end of game, we should see a positive trend.

Although our re-architecture work is n...

Yes! love this post, because it is very similar to the approach we are taking with our UX discovery. For your points 1 & 2 , we (League Client Team) are identifying which animations are potential bottlenecks to performance, and we are working on collecting that data. On the other hand, your point #2, we are working in partnership with our champ select design team to understand what animations are most important to players and make sure if we have them, they do not cause reliability or performance issues. Right now, I can't say we can remove all animations, until we understand which ones are performance degrading and measure them against the value they provide our players.

For point three, I will need to work with the team to identify how and when we can look into low-spec mode.

Love the feedback!

Our goal is to deliver results quicker than that!

Appreciate the comment!

We wanted to take a different approach with this post. From feedback received in previous posts, players weren't that interested in a chart showing our re-architecture work (even though internally it's very important for us).

during our most recent milestone, we got a lot of architecture work done, addressed around 60 bugs, and improved our startup times for players around the world that have slower machines, and we got really close to our goal.

The purpose of the survey is that we wanted to get a global view of what the players wanted us to work on, we used that data, and now are going to work on two of the more critical parts of the game loop, which is champ select & end of game. Given these are very frustrating for players when they encounter problems, we plan to deliver changes to make both experiences more reliable over the next couple months.

Thank you

Thanks for bringing this up! One of our plugins had an outage recently, and it looks like the logging for that is a bit too much. We are working with the team to limit the size of the log files, we do not want log files this large!

The team is aware of broader issues impacting several of our games and services (e.g. our chat service spans across multiple products), they are looking into it!

Thanks for this, and you are right, looking at our global survey results, champ select pick/ban issues seems to be very frustrating with players, and we are starting our discovery on what we can do to make this better.

Appreciate the feedback and update, I can tell you we are working our hardest to improve the client for all of our players;

- We have a really complex architecture that we are working hard to clean up, and doing this will unlock opportunities to improve the player experience in the client, which we will provide an update on in our next dev. post at the end of the month or early September given our recent company-wide break. Our team's goal in this next post is to give you insight into what players want to see addressed in the client, and how we are going to tackle them, and provide player-facing KPIs to track progress & success.

- We are listening to you, our players! we are actively collecting information from players via a sentiment survey (you may have got it!), on things players are frustrated with the most in the client. We have got great information so far and we are going to use that to prioritize what we work on next.

-As we clean up the architecture...

Thanks for the feedback,

As mentioned below, we took out a number of plugins on client startup until they are clicked by the player.

We did have discussions and made sure any plugin we decided to defer on startup would load within 3 seconds for 90% of our players. We also wanted to acknowledge the user action of a click by introducing that loading widget.

Why did we do this? -- We want to improve the client start-up times for a majority of our players and we were able to achieve this by fixing our deferred loading technology. Think of it this way, If you were to visit a site, it will not load all the hyperlinks that are on the front page, they would load when clicked. With our architecture work, we intend to clean up not only the plugin architecture but have the technology that runs the client work the way it is intended to work.

for store it takes 3 minuts and the animation is just scracth my brain. [even the colours of it feels stupi...

We are working hard to untangle this spaghetti to unlock improvements across all parts of the client :)

Yeah, this is true, I have just recently joined this team and super excited about the work ahead, and my goal is to use player feedback and data to help us get the client to a better place. I hope to change this perception, but it won't happen overnight.

Thanks for the comment.

Yes! love this comment, we definitely want to be more clear on how our architecture work (reducing plugins + ember apps) directly relates to the player impact, and we hope to articulate this on the next dev. post (although I do not have an answer/date to 'the client is finally fixed'.we have a lot left to complete and we acknowledge that)

Thanks

Good question, very early results from our survey is that players want to know what we are doing more frequently, so a valid call out!

We have started adding our significant changes and bug fixes in the patch notes, but I am working with the team to see if there is anything else we can do to increase our communication with our community (on top of the dev. posts + patch notes)

Thanks!

I deeply hope that someday, these issues will be tackled. I hope that bugs will be fixed, instead of being left there for us to get used to them, for us to get used to a worse client.

This statement resonates a lot with me... we want to address as many of the bugs listed as we can. We are encouraged by our continued architecture work (as highlighted in our dev. blog post) that will help us remove these bugs, and if they do arise, allow the team to address them quickly.

Side note, we have launched a player sentiment survey around the client across various regions (random selection, some players may have got it already!), to capture the client pain points, and use this information to tackle the biggest issues for our players with regards to the client! Expect to hear more in our upcoming dev. post!

Thank you for the thorough post, this takes a lot of time and we appreciate it! We are reading this!