Data Saving Problems

[Deferend]

You might want to take a look at this post regarding SetAsync() vs. UpdateAsync().

Stop using SetAsync() to save player data

Helps to use the whole context and not just a select part of it to make a point. oldValue is indeed what would be passed from a GetAsync call, however the retrieval and transformation of that value is handled all with a single request from the budget. It’s the value, not the call. DataId is an example in this code, it’s nothing relevant. On top of the fact that UpdateAsync allows you to specify a transformation function and reject save attempts, you miss the merit when you use SetAsync Up…