The saving-after-a-failed-load one got me once on a small project, defaults got written over a real save and I spent an evening wondering where the data went. Gating saves behind a loaded flag is such a simple fix. Also like that you moved the load into UpdateAsync, I was still doing GetAsync then SetAsync before reading this.
Glad it helped, that evening of hunting for missing data is exactly how most of us learn this one. One thing worth adding to the loaded flag: only set it after the load actually succeeded (pcall returned true), and leave it false on any error so the player just isn't saved that session instead of getting defaults written over their real data. If you later run into players joining a new server before the old one finishes saving, session locking is the next step.
Alex Yu
The saving-after-a-failed-load one got me once on a small project, defaults got written over a real save and I spent an evening wondering where the data went. Gating saves behind a loaded flag is such a simple fix. Also like that you moved the load into UpdateAsync, I was still doing GetAsync then SetAsync before reading this.