Feedback on the instance saving feature in my datastore module?

Help and Feedback Creations Feedback
#21

Another complex thing is managing when users store objects within things like dictionaries and tables to be saved. I will have to traverse through and tables or dictonaries they save to determine if the object is an instance.

1 Like
#22

I dont understand the reply you provided, but it appears to be a somewhat unexpected string of words.

#23

He is saying that #development-discussion is not the place to promote your Easy Datastore V2 which is made up of others’ work

1 Like
#24

Thank you clarifying the reply they sent. I want to clarify some things:

  • this post is not designed to promote easy module. I understand however the biased nature of the background information section so I have gone ahead and removed traces of promotional word usage.

  • the modupe is completely original, using the best practices. It does not copy or even take inspiration from the work of others. I understand the confusion so I have gone ahead and adjusted the post for this too.

Lastly, with these adressed, do you have any recommendations for what this disucssion should be moved to?

#25

The topic is very confusing. the title sounds like a #help-and-feedback:scripting-support topic but the main post would sound like a #help-and-feedback:creations-feedback topic. I don’t know which one to be honest.

#26

i see. Here are the changes i made:

  • renamed the post
  • changed the topic
#27

I still find it confusing. It should be more like “Feedback on my instance saving feature on my datastore module?”

but to respond to the original post, I think it is a compact one since you are storing the name of the instance so that it doesn’t waste too much bytes on the data saving. I think it is good since you can’t store every property unless you do some hacky methods

#28

storing strings aren’t taking a lot of space unless you have stupid-long path names, which you shouldn’t. Your naming convention is important to create a fluid system that can communicate easily.

And it works great and is accurate too. If you have wall types for example, you can easily store what wall types a player has by its full name. any attributes related to the walls can easily be stored alongside the data in a table and it is always accurate unless you do something to cause it to be inaccurate.

When the player loads and you load the building you don’t have to deal with instances, you just use a function to basically use the path name to obtain the object and then you can do the rest of the code as follows. I use this method for storing complex customized data. When players join the game, their inventory is reloaded using full path to get the base object. Any customizations or added data is then re-applied.