I have a game where players within the game are able to purchase a house and customize the location of the furniture within the house. Additionally, placement of furnitures is not based on a grid-system. However, when a player leaves and rejoins, I want them to be able to load their floor plan on any house of the same template within the game.
My current saving system runs a loop through each parts and groups them into a singular model. Then the primary part of that model is the floorplan of the house. This model is then serialized into a table which then would be stored into the datastore. To load the floorplan, it would deserialize the model and sets the primary part’s cframe equivalent to the new floor’s cframe. However, I refuse to believe that my first attempt on a saving system is the most efficient way to store and load data.
How would you go about saving such a system? What do you think would be the most efficient way regarding a system like this?