I had to snip this post coz snip

[binklaw (choy)]

snipsnipsnipsnipsnipsnipsnipsnipsnipsnipsnipsnipsnipsnipsnipsnipsnipsnipsnipsnipsnipsnipsnipsnipsnipsnipsnipsnipsnipsnip.

[Korvbagarens]

I switched from using DataStore to using DataStore2. It uses caching and is more fail proof.

You can read on how to use it here. It’s easier to use than DataStore and I’d recommend using it

How to use DataStore2 - Data Store caching and data loss prevention

DataStore2 Documentation | News | Source DataStore2 is an open source module that uses berezaa’s method of saving data that prevents data loss, caches, and verifies data before saving. DataStore2 has been used in my game visited by 120 million players with a constant concurrent player count of around 3,000 - 8,000 players, one time reaching 12,000 concurrent players. @AlreadyPro’s latest game Fairy World has 3 million visits and a consistent concurrent player count above 1,000, and a peak of 5…

[Ukendio (Marcus)]

You haven’t really shown us where you’re using datastore. Right now you have just stored a few values inside a global table…

[starmaq]

There is no problem if you store a table instead of a normal value, after all tables are just a some sort of complicated datatype. You can save them as usual.

datastore:SetAsync("the id", _G.Inventory)

And retrieve them however you want

local inventory = data:GetAsync("the id")

--and you can access what was in the table

local fedora = inventory["The Classic ROBLOX Fedora"]

if fedora.owned == true then
    print(fedora.rarity)
end

It’s really simple