There is a cost - there is no 'easy' change - there are only inexpensive changes. Should they prune it at some point? When? Where is that line drawn? Should they just let it sit, useless, in their database for eternity? All of these are cost questions. Currently, this doesn't happen - you don't need to reach out to the PVP.net servers while you're in-game, as all interactions happen on the servers actually running the League client.Īdditionally, this'd be extra space in their database, for every single user that ever plays any amount of games. For either transaction, this means adding new functionality, which is saving user-specific settings to Riot's servers while the game is going on. ini file from settings in db and download it to hard drive) or (parameterize settings when the game starts and load them into RAM). Log in -> enter game lobby -> match is starting -> (construct.
It's more likely that instead of a naive file structure just sitting on their web server, they'd have your settings data stored in a database, likely the same database that the PVP.net client authenticates to and accesses other information (e.g. You'd need to have the client somehow authenticate that they're you to a web server, which is a function that may not currently exist in Riot's infrastructure. Firstly, serving up a public file with any kind of user data in it is generally frowned on.
