I seem to recall having multiple datastores being a bad idea. I have an old save file for every player which I want to preserve. I don’t want to touch this data in anyway other than to read what data they’re using. This data belongs to PlayerStore1. The data is in an outdated format and I really just don’t want to modify it in anyway
Instead I want to have a new datastore, PlayerStore2. PlayerStore2 is going to be my primary datastore from now on. I seem to remember, however, that a few years ago it was considered bad practice to have more than 1 datastore for a game. It’s probably nonsense (and doesn’t really even make sense) but I was wondering if there’s any validity to the claim?
When the usage of multiple data stores is said to be a bad idea, your case isn’t what’s being referred to; you are just switching from a legacy data store to a new one.
Having multiple canon data stores (either one per player or one per statistic (such as coins)) could be seen as a bad practice because of the extra web requests needed to maintain all the keys of multiple data stores.
There’s also nothing wrong with having multiple datastores as long as you’re not hitting any limits. It’s definitely better to use just one, but using multiple isn’t awful.
I’m responding to a 1 year old old post - Is this bad practice? I know it will ping the participants. Only recently received my posting ability here and don’t want to ruffle feathers!
2 Primary question - I have a single, standard datastore to save a table of various values. I’m now trying to implement a leaderboard to show one of the values in the table. Do I need a 2nd - ordered datastore for my single value that will be on the board?
