There were some people saying that if there are more players in my game setasync will basically mess up on me? is that true?
✓ ANSWER ACCEPTED
Why are people saying don't use setasync for data store?
1 answer
✓ Accepted answer
#Well, what they're saying is (mostly) wrong. I think. Don't quote me on that.
Do what you want to do. You should use SetAsync if you want to completely overwrite the player's information, or if the player's information is nonexistent. Even then, you could make your own artificial UpdateAsync that could work wonders compared to the normal. UpdateAsync updates the previous given value. It's rather different when you think about it. You should always take in consideration what you're using, and the way you're using it. Read up on the topics here.
https://www.robloxdev.com/api-reference/function/GlobalDataStore/SetAsync
https://wiki.roblox.com/index.php?title=API:Class/GlobalDataStore/UpdateAsync
https://scriptinghelpers.org/questions/6534/setasync-or-updateasync
####Any misinformation? Please help a man out by notifyng me in the comments.
This discussion is preserved as it was. New answers, comments, and votes are closed.
5 comments
UpdateAsync considers the previous value while SetAsync does not
So I should use UpdateAsync instead of SetAsync
it doesn't matter if you're not using a function for updateasync
SetAsync will override the existing data completely. And what Vulkarin said as well
So if you need to do something with the previous value it can be much easier with UpdateAsync