Save a lot of data with datastore

[BlackBooks (KecapSosro)]

I have a problem with saving in datastore. So basically i have followed a tutorial on youtube. so here’s the sample of script that i got

local DataStoreService = game:GetService("DataStoreService")
local myDataStore = DataStoreService:GetDataStore("DataStores")
game.Players.PlayerAdded:Connect(function(player)
    local Id = "Player_"..player.UserId
    local uang = player.leaderstats.Uang
    local makan = player.leaderstats.Makan
    local data
    local success, errormessage = pcall(function()
        data = myDataStore:GetAsync(Id)
    end)
    
    if success then
        -- Set data 
        uang.Value = data.uang
        makan.Value = data.makan
    end
end)

game.Players.PlayerRemoving:Connect(function(player)
    local Id = "Player_"..player.UserId
    local data = {
        uang = leaderstats.Uang.Value;
        makan = leaderstats.Makan.Value;
}
    local success, errormessage = pcall(function()
        myDataStore:SetAsync(Id, data)
    end)
    
end)

My question is how to save a lot of data, because i need to wrote the data manually. Or is there any technique to make it simpler ?

[JackscarIitt (Jackscarlett)]

Sir this belongs in the #help-and-feedback:scripting-support category, this is #help-and-feedback:cool-creations

For your issue, try using a ModuleScript, creating a Table inside that holds all of your Dictionaries/Values, or a RemoteEvent to save huge amounts of data?

How would I save a lot of data efficiently

Either use a remote to send relevant information to the client, or have a module in ReplicatedStorage which would contain the retrieved data for every player, just access data from there for the client. -- on player added local data = -- retrieve data Remote:FireClient(player, data) -- client local settings Remote.OnClientEvent:Connect(function(data) settings = data end) print(settings.AimSensitivity) -- etc. Or use a module -- module return {} -- on player added local module…

Saving massive amounts of data

I’ve noticed having a knockout amount like # of retries causes data failure. So literally keep trying until it saves, but as for storing the data use one big table holding a bunch of other tables or values.