Should I switch datastores?

I debating whether I should switch the way I save and change data in my game. There are modules such as DataStore2 and ProfileService that I plan on switching to.

I’m currently using the normal datastore method (:GetAsync(), :SetAsync()).

So the question is, should I migrate datastores? I am aware of all the work needed to migrate, so is it worth it?

2 Likes

I’ve used DataStore2 for years now. I have not yet met any downside to it. Really easy to use, and you shouldn’t at all worry about data loss. :slight_smile:

Is it worth the work though? My game is near completion and I’m unsure.

How many hours do you think your migration would take?

About 2 - 4 hours (maybe)

11111111

Oh, then for sure, in my opinion. 2-4 hours is a very small amount of time, compared to what you use on scripting a game. But it all depends on your reason for switching.

With DataStore2 it takes me 5-10 mins max, to setup the basics on a datastore system in a plain new game. So not only do you learn more about using DataStore2, your future projects would also have a almost plug’n’play method of storing data.

Am I able to use multiple keys and save tables with it?

You can store multiple keys under something called a MasterKey, and yes, you can store tables, dictionaries ect. in those keys.

Edit: How could i make a sort of purchase saving system? - #6 by TortenSkjold

Thanks, will try out DS2. Hopefully it turns out well