Strongly consider merging GlobalService into their easy loaded modules
This will allow for the modules to be easy loaded which is important for other services/modules (such as commands) which wish to initialise right away
[x] rename Sender to GlobalSender and Receiver to GlobalReceiver or just one Global object with all methods/props
[x] merge
[x] strongly consider returning a Promise for all asynchronous calls
[x] update comment examples
[x] test thoroughly
DataStore service
Consider stripping it completely and converting it into a wrapper for profileservice and utilise promises
Support for server-wide data would have to be considered (maybe this is where the new cloud scripts come into play)
[x] IMPORTANT: Ensure Nanoblox works even when datastores fail
[x] have saveasync, loadasync, etc renamed to just save, load, etc and return promises with relevant error messages
[x] if datastoreapi access is restricted (https://i.imgur.com/CzXC572.png) then have a single warning in the console instead of multiple from different sources
[x] update internals such as :grabData to utilise promises and with with the new methods
[x] ensure nanoblox works smoothly even with api services disabled
System
With this System can maybe simplified a lot?
GDPR
[x] Ensure Private and Reserved Server environments utilise the new datastore-key-player association to be GDPR compliant
[x] Have systems and users utilise new association
[x] When a user is wiped, make sure to wipe all their associated environments (reserved, private, etc) too
GlobalService
This will allow for the modules to be easy loaded which is important for other services/modules (such as commands) which wish to initialise right away
[x] test thoroughly
DataStore service
Support for server-wide data would have to be considered (maybe this is where the new cloud scripts come into play)
[x] ensure nanoblox works smoothly even with api services disabled
System
With this System can maybe simplified a lot?
GDPR