Hey, I made this script wchich is supposed to save the data of the currently edited world while a player leaves. Each world is supposed to be stored in its own DataStore instead of storing all of them in one because of the 4MB limit of data that can be stored in a DataStore. However for some reason the loop that adds all the blocks and their data to the blocksData table stops at some point. It only prints out names of a few blocks and then it stops. There are no erros in the output. Does anybody know why is this happening?
Here’s the part of my script responsible for saving data:
game.Players.PlayerRemoving:Connect(function(player)
local blocksAmount = #workspace.Blocks:GetDescendants()
local data = {}
data.Saves = {}
for i, v in pairs(player.Saves:GetChildren()) do
local saveData = {}
saveData.Name = v.Name
saveData.DateCreated = v.DateCreated.Value
saveData.Seed = v.Seed.Value
table.insert(data.Saves, saveData)
end
PlayerData:UpdateAsync(player.UserId, function()
return game.HttpService:JSONEncode(data)
end)
print("player data")
print(player.Saves:GetChildren())
for i, v in pairs(player.Saves:GetChildren()) do
local SaveBlocksData = DataStoreService:GetDataStore("SaveBlocks"..v.SaveId.Value)
print("SaveBlocks"..v.SaveId.Value)
local blocksData = {}
blocksData.Blocks = {}
for ii, vv in pairs(workspace.Blocks:GetDescendants()) do
if vv:IsA("Part") or vv:IsA("BasePart") then
print(vv.Name)
local blockInfo = {}
blockInfo.Name = vv.Name
blockInfo.XPosition = vv.Position.X
blockInfo.YPosition = vv.Position.Y
blockInfo.ZPosition = vv.Position.Z
blockInfo.XOrientation = vv.Orientation.X
blockInfo.YOrientation = vv.Orientation.Y
blockInfo.ZOrientation = vv.Orientation.Z
blockInfo.Anchored = vv.Anchored
table.insert(blocksData.Blocks, blockInfo)
end
end
print(blocksData)
SaveBlocksData:UpdateAsync(player.UserId, function()
return game.HttpService:JSONEncode(blocksData)
end)
print("updated data")
end
end)```
When the player leaves the game, the server removes the player object and anything attached to it running. Because DB calls take a long time (in computer time anyway, not human time), your best bet is to collect all the “player vital” data you need first, then collect all the block data, then have them both do the DB call to save it. That way, if the player object is gone it won’t matter since you already stored the important data somewhere else. Without knowing exactly how your game works, it might be best to create a separate function for saving the world blocks assuming those aren’t attached to the player object itself? That way you can save your player data first, then fire off a “separate” function to do the world block saving that won’t depend on the player being there at that very instant.