If you have been testing this in Studio you will need to allow Studio to access API requests in your Game Settings. Also, I suggest you wrap your datastore requests in a pcall since any API requests can error unexpectedly and without a pcall your whole script will stop.
Technically it would. The error here is that PlayerRemoving is never being fired. You can add a print statement and test it too you will see. Add a BindToClose Event to fix this. Also if you test on an actually server it will work.
First you should read the advice I gave you and then look at the devforum post I linked. It’ll help you decide if you want to use datastore2.
Here’s why i told you not to use datastore2 without knowing how it works:
Just joining the crowd without doing your own research is bad. I’m trying to prevent you from just using datastore2 without knowing what it does internally, because too many people use it without knowing how it works.
So it’s not a simple yes or no answer like you asked for. That’s why i’m not giving you a simple yes or no answer, and its why i linked the devforum post.
I believe limitations is the word you’re looking for, DataStore2 is just another DataStore system, I don’t see how it can have any detrimental effects . The post you linked is outdated by the way and DataStore2 now does support the usage of promises; GetAsync() and SaveAsync() exist now. Go see for yourself.
As for the topic, @dibblydubblydoo you’re doing several unnecessary things here: You don’t need to have separate DataStores for each different data type, try to save or essentially combine all your data under one dictionary instead , this will save your DataStore Get and Update/Set request budget significantly.
Now for an answer relevant to the contents of your post:
You asked for whether it is advisable or not to use DataStore2 to prevent errors, the answer could be any, only you can decide whether it meets your needs.
DataStore2 has received commendation from many, proper usage of it could lead to virtually no data loss, that’s what it’s built for. Quenty’s system is reliable too, use whatever system you feel has an easy to understand API and meets your needs.