League of Legends Dev Tracker

We are down to:
- 48 plugins
- about 4 build configurations

It breaks down to 3 plugins with 3 special configs and 45 with the same build configuration. The ideal would be to get rid of the plugin system and have a single app. We are working towards that. The last few special configs are very tricky to get rid off.

Hey, i posted this in an earlier thread

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.

it is true tho

Thank you, appreciate the feedback, but we still have more to do!

We just did!

Hey, Response here

We posted our latest this AM, the link is in the post.

"Never" is not applicable here. It is a large effort, but League has invested in large efforts like that before - we just don't do so lightly.

I do look at every client related post when they are posted, and I respond when I feel like a have a good answer to the concern, and I am extremely data-driven. For Example, we have data from our survey results and show a positive trend from people being very upset with the client towards the more neutral/positive side. I want to share more of these findings with players when I can. Does this mean we are done? hell no, if you see in our latest post, we need to do many things to upgrade chromium, which will provide big player benefits, and fixing JS errors, continuing to reduce memory leaks, etc.

I deal with the constant complaining by looking at the data we have, and it provides me comfort knowing we are making the client better for our players globally, and if this trend reverses, I will be the first to tell you.

Please take a deep breath and re-read my post. At no point am I blaming the backend, and the fundamental change of going to native is what most of the post is talking through. The part you quoted is covering the idea of re-implementation without any fundamental changes - ie, take another swing using the same tech stack, which I think you'd agree would be folly.

Ive been working really hard this year to inject more personality and spontaneity into my casts. Last year I was intentionally serious/kinda bland imo, but Ive really been liking the balance Ive struck so far. How do you think Ive done? No wrong answers!

tech issues

We really do appreciate and read this type of feedback, and our devs talk about these types of changes all the time.

Our specific team is focused on improving the overall client performance and reliability, while feature teams across League of Legends maintain many of the features you ask about. While I can't speak specifically to the features you ask about, we can ask our colleagues on the teams that own these experiences to see if they are got any plans to adjust and/or update

YEP SCHALKE

Native by default, with CEF to cover the pieces that truly are best covered by JS stack. Best of both worlds.

Don't suppose you have a magic wand I could borrow?

lol ;)

It's not using Electrion ;)

It's built on top of the Chrome Embedded Framework, with a custom-built foundation underneath.

As to your larger question of why the JS stack is sometimes picked over native solutions - I can't possibly speak for the entire tech industry on that, but I'm happy to give my personal opinion based on what I've seen in general industry trends.

I think there was a lot of hype super early in the development of the interactive web that had people believing the future of the native application was limited. The Google suite in general gave that a lot of ammunition - if you can compete with MS Office using web tech, what can't you do? That's a sane, reasonable conclusion to make if you aren't aware of the massive amount of work that goes into making those products as smooth as they are. As with much tech industry hype, there is a lot of value inside of it. Web-based applications are hugely valuable and solve many problems that ...

Season start notifications as well as several of the popup modals that are shown when a player first logs in are implemented using the same system.

While we have made improvements over the past year to the system (with our data, after we implemented multiple fixes we have seen a dramatic drop in this issue), We know that there are still problems where the local settings file resets on players' machines.

This is especially true when multiple accounts share the same PC. We have work on our backlog to holistically address how we save player preferences and persist the state of what they have seen or not seen, and hope to have more details later

Season start notifications as well as several of the popup modals that are shown when a player first logs in are implemented using the same system.

While we have made improvements over the past year to the system (with our data, after we implemented multiple fixes we have seen a dramatic drop in this issue), We know that there are still problems where the local settings file resets on players' machines.

This is especially true when multiple accounts share the same PC. We have work on our backlog to holistically address how we save player preferences and persist the state of what they have seen or not seen, and hope to have more details later

Season start notifications as well as several of the popup modals that are shown when a player first logs in are implemented using the same system.

While we have made improvements over the past year to the system (with our data, after we implemented multiple fixes we have seen a dramatic drop in this issue), We know that there are still problems where the local settings file resets on players' machines.

This is especially true when multiple accounts share the same PC. We have work on our backlog to holistically address how we save player preferences and persist the state of what they have seen or not seen, and hope to have more details later.