Few Questions on dataStore

[batteryday]

@anon25856735

(Its a single player game so i feel SetAsync is more appropriate than UpdateAsync).

SetAsync is never more appropriate than UpdateAsync, has nothing to do with single or multi player.

@anon25856735

My question is should i be SetAsyncing this dictionary every time its updated and risk the final saves not saving because of the length of the queue. Or save it like every 6 seconds

You should never save based on an action (table updates, player dies) as that can happen many times quickly and overflow the queue.

You should for multiple reasons always have a cache and save periodically.

1. you’ll never run into request overflow and potential data loss
2. if you use getasync when you want a value you can run into serious race condition bugs, that can be exploited (e.g. duplicating items)

@anon25856735

So I’ve just created a copy of the dictionary from GetAsync.

I’m not sure what the copy is about you don’t need a copy, just use the table GetAsync returns

@anon25856735

Also can the server shutdown before my player removing event function can finish?

You use game:BindToClose, to run code before the server shuts down

---

personal recommendation

I use and recommend other people use ProfileService by loleris, it’s an extremely robust, nice abstraction for storing data, has full support from loleris (constantly being updated), easy solves things like race conditions because it’s session locked. I think most pros use it.