How would I get all keys in a datastore or a scope? [Datastore backup system]

Help and Feedback Scripting Support
#21

I get around this by making my backup tool a little obscure to get to (so I can direct players to it when they lose their data, but so they won’t find it on their own) and by only allowing them to use it once (which I reset whenever I accidently break someone’s data)

2 Likes
#22

A little off topic, but I noted you in my code for your backup algorithm.

image

1 Like
#23

Since we’re off-topic, I’m curious what is this meant to do?

image

#24

So my game is ran on my engine, “Dragon Engine”.

Basically, each service module is loaded into the engine, and the engine exposes itself to the service so the service can call engine methods inside of itsself, such as self:DebugLog().

Each service has server methods and client methods.

Client holds all the client-callable methods.
DataService.Client.Server=DataService basically gives the DataService.Client table access to the server methods.

It’s also used to prevent stack overflows from the __index metamethod.

Both server and client methods are ran server sided, but client methods can be called by clients via remotefunctions.

EDIT : For more info, you can view the framework by @Crazyman32 : GitHub - Sleitnick/AeroGameFramework: AeroGameFramework is a Roblox game framework that makes development easy and fun. The framework is designed to simplify the communication between modules and seamlessly bridge the gap between the server and client.

I took inspiration from this framework and wrote my engine from scratch based on the structure of the aeroframework.

4 Likes
#25

Ooh. I’m also making a backup/restore data option for my game right now which was part of a trigger for the creation of an earlier post. I can tell you what I’m doing.

local DataStoreName = "GameData_Build100"

local DataStoreService = game:GetService("DataStoreService")
local PrimaryDataStore = DataStoreService:GetDataStore(DataStoreName)
local BackupDataStore = DataStoreService:GetDataStore(DataStoreName, "Backup")
  • To backup, users must enter the recovery screen and upload a copy of their main data. I don’t want to automate the process because I fear throttling which is currently a major issue in my game, despite there being no reason why it is. From there, they can use it (which then flushes the backup store for them) or update it. Once per time they use the menu to prevent throttles as far as the menu goes.
  • When the user chooses to use their backup, I call GetAsync on the backup store (provided I don’t cache the result when they join to prevent using GetAsync again in the future). I then call SetAsync on the main store and use whatever was returned from the backup GetAsync as the value for the set.
1 Like
#26

If anyone wants an implemented version of @berezaa’s method, I have put it into my DataStore2 module (which also handles caching and player leave saving for you).

5 Likes