sepalani
commented
6 years ago Currently, the only way to manage records is to use any sqlite database tool you want to alter the database. Creating a Web-UI takes time. Unfortunately, I don't have much time to make one at the moment.
Plus, it won't solve the real issue which is uploading cheated scores that's discussed here.
Even with such a Web-UI, each game has its own way to send/get records from the server. Some always push the player score on login and only a banning system can prevent a cheated score to be uploaded. All games can manage the player data however they want, so it will require a dissection tool per game in order to have a really effective banning system and detect cheated scores.
In sum, the only way to prevent a cheated score would be to ban players sending them and/or build a tool that can handle many binary formats used by each game to gather the score and check if it's a cheated one or not.
It would be nice to have such tool but that requires an insane amount of work. Nonetheless, if such a system is made at some point, it would allow the creation of a human readable statistic page per game which would be nice.
InternalLoss
Issues such as this would be much easier to deal with if a Web UI for generic records was able to be seen; even if per-game data couldnt be understood (and a way to implement custom record parsing should be an idea), it'd be a good idea to have an authentication-hidden page where you could delete inappropiate records etc.