Okay, first of all why I created this and not using the existing ProfileStore is the following (I want to defend myself first as maybe the creator of ProfileStore might be reading this post, I dont have any means to talk shts of your creation, these are my personal problems and honestly ProfileStore is really great resource):
- Boiler plate setup. Before ProfileStore gets run, you need to setup how it handles player when they join and when they leave.
- Everything is saved despite nothing really changed. Unlike ProfileStore who has a standard auto-save frequency for everything and saves everything despite theres actually changes or not and those quotas might be use instead for other logic in the system (game).
- The many metadata besides what the player data actually have (I know this is something needed). But I want to make sure less memory gets written when it finally touches the database.
- This one I hope Im not correct with this and Im not sure whether it actually caches the data in the server memory, everytime you read data it needs to ask the database again (Im not really sure if ProfileStore does have caching mechanism, this one I might be wrong).
I guess these are the things? Maybe?
For the whole part, I guess you should use AI (though you are not fan of AI maybe) to do the scrutiny things.
I also want to point out that maybe the resource is bloated because it is a large file, the resource is large because almost anything is automated for you. If you notice, the APIs it exposes are just mainly for read and write and schema introduction and nothing else. Everything is hidden, this is something I can totally brag because why not I am lazy.