Removing a datastore completly

Help and Feedback Scripting Support
1

so basically when i was testing the game’s datastore named “data” which i used to store player data

UNTIL i realized i should have put it in a global datastore since theres many places in my game and i want it to share across these too
so i did that

but now im stuck with an useless datastore roaming in my datastore manager which i dont need anymore

the problem is i dont exactly know how to wipe out a datastore from my game completly, or if you can even do that in the first place

i dont want the keys removed from the store i want the entire store wiped out

oh and also this other datastore “PlayerCodeStore” i also dont need

2

You can remove the players data, but once made you can’t remove the database or player.

1 Like
3

Won’t removing all of the datastore’s keys have the same effect as removing the datastore itself?

4

Roblox in general doesn’t like deleting things. If you notice, most if not all ways to “delete” things are related to archiving instead. Datastores are pretty similar, you can delete all the keys(debatable since they now have versioning), stop using that random datastore, but I doubt there’s an actual way to delete it completely.

5

I use the DataStoreEditor plugin. It lets you see and edit everything more clearly than usual. It cannot do it, so I believe it is not possible.

6

its 10 dollars tho so i dont think i will get it anytime soon

7

Just saying it has no option for that.

You got this

local DataStoreService = game:GetService("DataStoreService")
local playerDataStore = DataStoreService:GetDataStore("PlayerData")

local function removePlayerData(player)
    playerDataStore:RemoveAsync(player.UserId)
end

Not much help if you don’t know the IDs ..
Will not remove the player like it looks like, but it will remove their data.
Isn’t there still a free version?. At least you can get the IDs.

8

You cannot delete a data store once created via GetDataStore. If you no longer need/want a data store, then you can simply stop using it.

Since their names may cause clutter over time (especially when using plugins to browse data), it can be helpful to name your data stores in such a manner that allows you to quickly identify what is old/legacy. Many creators use sequential numbers for this purpose, e.g..: Production_v1.0, Production_v1.1, Production_v2.0. I am personally fond of using dates (e.g. `Production_2025-8-16_v1), but your preferences may vary.