Best Practice for Testing DataStores?

Help and Feedback Scripting Support
#1

I have a game with many features that utilize the DataStore service. When testing all the variations of things a player can unlock I end up just using filler names for datastore’s to reset my character’s data to default. Examples:

— I typically will do this up to 10 times----
local UnlockedDisplays = DataStoreService:GetDataStore(“UnlockedSwords”)
local UnlockedDisplays = DataStoreService:GetDataStore(“UnlockedSwords2”)
local UnlockedDisplays = DataStoreService:GetDataStore(“UnlockedSwordssss”)

I do this sporadically and was just wondering if this has any long term consequences, like filling up an experience’s data it has to pull from. Could this possibly cause things like lag or failing DataStores in my future, and if it does is there alternative practices to testing datastores?

#2

Well, I can’t imagine it being great for organization. I’m very curious how your game would look in any kind of datastore editor plugin.

You could always just run something like this in the command line:

game:GetService("DataStoreService"):GetDataStore("YOUR_DATA_STORE"):RemoveAsync("YOUR_KEY")
1 Like