Getting rid of the client and merging it into the game would be a start. The issue is League is toxic by design, and it gets worse because the developers keep trying to milk it for more money every year. Add to that the fact that its got spaghetti code like no tomorrow.
League has so many problems that it would be better for Riot to just develop a whole new game with all the fixes built in than for them to keep using duct tape on the current one.
I still contend the old “Adobe Air” client was more usable and organized than anything that came after…
In the last year that I played it, they added the Riot Launcher, which was nothing but a massive PLAY button that really only functioned to launch the other ‘new’ client. It was mind-boggling how dumb it was…
they added the Riot Launcher, which was nothing but a massive PLAY button that really only functioned to launch the other ‘new’ client
Don’t forget that it also got rid of the individual animated splash pages and theme music that used to play for every champ release and event (eg. Worlds). Used to be so hype.
There was a devblog a while back a developer talked about how much technical debt the game has because its coded in LUA, like the second oldest programming language known to man, and modifying literally any of it will break other parts of it because everything was built on top of the old stuff. Basically, the code has never been refactored.
That’s not really what that blog post is talking about. Lua isn’t actually particularly old as far as programming languages go and one of the most commonly used scripting languages in game development, due to it’s easy embeddability. And it’s a perfectly fine language in that regard.
Their problem is that they built their own visual scripting language on top of Lua called BlockBuilder. And that comes with quite a bit of overhead, since the way they’re doing it needs a number of additional heavy operations. And Lua is a full blown programming language that comes with a lot of functionality that they don’t need for that use case, but still need to account for.
So the complaint is, that they used Lua instead of using a simpler and constrained language
Getting rid of the client and merging it into the game would be a start. The issue is League is toxic by design, and it gets worse because the developers keep trying to milk it for more money every year. Add to that the fact that its got spaghetti code like no tomorrow.
League has so many problems that it would be better for Riot to just develop a whole new game with all the fixes built in than for them to keep using duct tape on the current one.
I still contend the old “Adobe Air” client was more usable and organized than anything that came after…
In the last year that I played it, they added the Riot Launcher, which was nothing but a massive PLAY button that really only functioned to launch the other ‘new’ client. It was mind-boggling how dumb it was…
The new client was better until Alpha Patch 5
It was never designed to carry as much bloat as they’ve put into it since
Those were the days
Don’t forget that it also got rid of the individual animated splash pages and theme music that used to play for every champ release and event (eg. Worlds). Used to be so hype.
I always see people say it’s got spaghetti code but I’ve never seen much about it.
Do you have a source?
There was a devblog a while back a developer talked about how much technical debt the game has because its coded in LUA, like the second oldest programming language known to man, and modifying literally any of it will break other parts of it because everything was built on top of the old stuff. Basically, the code has never been refactored.
Blogpost here.
That’s not really what that blog post is talking about. Lua isn’t actually particularly old as far as programming languages go and one of the most commonly used scripting languages in game development, due to it’s easy embeddability. And it’s a perfectly fine language in that regard.
Their problem is that they built their own visual scripting language on top of Lua called BlockBuilder. And that comes with quite a bit of overhead, since the way they’re doing it needs a number of additional heavy operations. And Lua is a full blown programming language that comes with a lot of functionality that they don’t need for that use case, but still need to account for.
So the complaint is, that they used Lua instead of using a simpler and constrained language