I've been thinking for a while and I'm stuck between two approaches:
One of them is to put everything inside one datastore. This would make my request to the datastore in just one line, but I'm afraid that I would overload my datastore quickly. And it would be easier to manipulate it.
My second approach is to make multiple datastores – Character Stats, Character Customization, Inventory, Skills –, but by making this I'm afraid that the requests might be slower or something like that. Not to mention that it would be a bit harder to manipulate the data.
5 comments
1 datastore for players, 1 for the server, (to avoid throttles), going over the data limit would be weird, I'm pretty sure it's 260K chars..
if youre not going to save too much data (around <200000 characters, not sure) just put it into 1 datastore, it would make much more sense and be less confusing
im not a pro at datastore, but u should take the seconds approach let the first data load, then do a wait(0.5) then u should do the next datastore then wait(0.5) and so on
bad idea, datastore throttles way faster than you think stinkyest11, and more datastores means less chance of keeping your data, 1 save has a 99.9% to work (unless you're doing it very bad)
In addition, I recommend saving 1) when a player leaves, 2) on purhace, highly recommend, though, consider making a 'queue' system 3) ever 60 or so seconds (to make sure everything works right), and 4) when the server wants to shutdown (use bindtoclose!)