Should I use UpdateAsync or SetAsync?

[posatta (pasta)]

UpdateAsync has certain benefits over SetAsync, but you have to actually use them. Code that does not leverage the old data might as well be using SetAsync. There are threads explaining how to use UpdateAsync separately, such as the one below, but overall use SetAsync for quick and dirty saving and UpdateAsync for careful operations taking previous data into account.

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…

Never use UpdateAsync and have the transformFunction look like this:

whatever:UpdateAsync(whatever2, function(old)
	return {data = something new}
end)

If you aren’t using old, don’t use UpdateAsync.

Edit: UpdateAsync won’t help your issue here, though. The problem is that you’re saving too frequently. Try saving at set intervals (e.g. once a minute) or when a player leaves instead of every time the event fires.