Help with data stores

[posatta (pasta)]

If you’re curious about why you might want to use UpdateAsync over SetAsync, there are a few topics people have already made about this:

SetAsync or UpdateAsync?

SetAsync does just what it says – it sets the value of the datastore regardless of the original value. UpdateAsync takes its second parameter as a function, which allows for the old value to be taken into account (the function is called with the old value as input and is expected to return the new value). If you’re not using the second parameter of UpdateAsync as a function, there’s no difference. If you don’t care about the old value, there’s no difference. This is only useful if you want to i…

How would I go about using UpdateAsync over SetAsync?

pre-edit so colbert's post still makes sense

UpdateAsync isn’t inherently a better function to use. You should only use it if you’re going to compare the old value to the new value. An example of this being useful is for values like levels and achievements that should never go down, only up. (This is assuming no rebirth system or similar; the exact examples of levels and achievements might not apply to your game.) You could compare the old value to make sure it’s less than the new value, and…

Datastore data loss

If you don’t want to use DataStore2 or an external database, there’s still some ways to make your system a bit more reliable. If distance is always an increasing number, UpdateAsync could be helpful here – even if it’s not in the way ClientScripts said. The good thing about UpdateAsync is that it will use the previously saved value instead of just getting rid of it. That means if your initial GetAsync fails, by the time the player leaves you could be able to increment their old data instead of …