What better ways are there to storing user data in a DataStore?

[rogchamp (pasta)]

Yes, why do you care about the old data? That’s what I have been asking the entire time.

@posatta

In the case of user data, you don’t necessary need to consider the old value; if the user’s in the server, the values you have been using in that server should be correct anyway.

@posatta

The only benefit I can see with UpdateAsync is if you’re saving the old data to another place or don’t check if the value you’re setting is nil. If there’s any other benefits that make it easier not to lose data, I’d be much more interested in using it. I just don’t see any major benefits.

@posatta

I don’t see any reason to compare new and old values when the new value could be completely different. Of course, you should do checks to make sure all your data’s there before you save, but you don’t have to use UpdateAsync to make sure what you’re saving isn’t nil.

@posatta

You should only ever use UpdateAsync if your new value depends on the current value.

[Complextic]

We care about old data because if the SetAsync() errors then all the data is lost, but if it errors with UpdateAsync() the old data was not erased so it has something to fallback on.

[rogchamp (pasta)]

Where does it say that on the wiki? None of the error handling pages on datastores say this.

[rogchamp (pasta)]

That is completely irrelevant. If the SetAsync errors, it makes no sense for it to delete the data. If it can’t access Roblox servers, how would it delete the data?

[Complextic]

I don’t know what to tell you at this point. All I can tell you that my game experienced a lot of data loss issues with SetAsync() and I switched to UpdateAsync() and I havn’t had the same data loss issues.

[Complextic]

Other people are also saying exactly what I’m saying:

Do you use SetAsync or UdateAsync when changing player data?

I’m currently in the process of setting up my latest datastore. I was just wondering, what would you recommend to save player data: SetAsync or UpdateAsync? In the past, I’ve always used SetAsync, however the wiki recommends the latter: [image] Also, in what situations can SetAsync cause serious data saving problems, and when is UpdateAsync always the better option?

UpdateAsync or SetAsync

I’m cache-ingthe player’s data everytime they join the game and saving the cache everytime I leave. Should I use updateasync or setasync?

[rogchamp (pasta)]

(Taking the post that is saying to use UpdateAsync, rather than the few that aren’t.)

@colbert2677

That’s OnUpdate. UpdateAsync runs a function that cannot yield, passes in the old value as the only argument and expects to be returned with a new value created by the function.

SetAsync or UpdateAsync can be used to save players data for another session. It’s more preferable that UpdateAsync is used in the case that multiple instances are referencing the player’s data, in which their stuff can be overwritten.

It looks like they’re talking about when you’re using multiple scripts to access to same datastore, which makes sense. I agree with using UpdateAsync in that case, thanks for linking these threads.

[Complextic]

Np sorry for the bad discussion I’m really bad at explaining things