Is It Possible To Data Save For An Entire Game, Not Player

[RobloxianFreedom]

I’m trying to make a game where players are able to purchase/rent property (businesses, homes, etc.) however I want it to function over a long period of time. For example, if I buy a store, I want to be able to rent it for let’s just say 2 days where no one else can purchase it. Is this possible? If so how can I go about saving stuff for a game? I tried looking it up but could only find posts about saving data for players.

[Eternalove_fan32 (FrostDracony)]

You could save a string (e.g. you save a “Store Model NoobStore” string variable) and if you need to load the store, just check what you have as a store and load that store (yes, sounds confusing, in other words:

if StoreModel == "NoobStore" then
    --load the NoobStore
end

). But if you can customize the loading like BloxBurg itself, then you better choose serialization.

How to save parts, and the idea of Serialization

This article is the answer to the famous question “How to save objects using Datastore” and many other ways to word it. If you played with Datastore for enough time, I think you already know that Instances such as parts and models ect. can’t be simply saved using :SetAsync(), which makes it hard to save objects. Most people, with games that are supposed to have slots and stuff on them that you want to save, get stuck when doing this, although, I think finding a way to go over this is quite eas…

But can’t you save a whole game directly instead of making such a complicated detour? No, you cannot. Or you learn decent programming, or not.

Hope this helps

[RobloxianFreedom]

It does but the issue with that it would neglect other active servers right? Like is there a way to universally do something so that way it cross-interacts with other servers too to make sure two people don’t purchase the same store on different servers.

[VegetationBush (FartedWayTooHard)]

You just have to retrieve the DataStore with the same key:

local Data = DS:GetAsync("GlobalKey")

The key is where your data is stored, in this case, GlobalKey will be a datastore for all players. The reason we have keys is because we need to differentiate between 2 players data. For example, if you saved data with UserIds, and you load let’s say, your UserId to Player1, then player one will be able to see your data. Same thing for this, if you load with the same key, you get the same data.

[RobloxianFreedom]

I’m tad confused by that. But in the end it’s possible to have stores have a value distinguishing who owns it and update it live time across multiple servers correct?

[VegetationBush (FartedWayTooHard)]

Yes, if you were to save the data in "GlobalKey", and you load "GlobalKey" to every player, every player would be able to see the data in it(meaning that they can see if it is owned or not.