Ya, but in the major part of cases , there’s no documentation, and u’ve to learn someone else scripts. So what I’ve learned is that it’s better to have self made scripts/DataStore and know how to solve issues, add new things, instead of having something unknown, and if a person wants to add a new function to the DataStore system, it’s not possible just cause that person doesn’t know anything about datastores…
DataStore v2.0 has an build in “Backup” system called Versioning so you don’t have to worry that much about data loss
You still have to script a system that deals with those backups… And ideally, you wouldn’t want to rely on backups for preventing data loss, you want the data to not be lost in the first place…
Both modules cover the same functions.
But not in the same way, Suphi’s Datastore Module does some functions in a safer and faster way.
I said they cover the same functions not the same methods
A retry system isn’t that hard to code
The whole debate is about the fact that some people make dataStore modules to improve upon older modules using different methods, not that they’re functionally the same.
Usually modules either cover the general use cases or are self contained (ie they do something specific and you don’t really have to interact with them)
For the modules I have made, I usually give a decent explanation of how to use it, I don’t think there is much of a problem there?
It is a valid point though, but not a deal breaker in my opinion. I don’t know the situation for datastore modules or even other modules since I don’t really use them, but if a module can save time to someone, then it has some worth. You might not learn from it, but many people don’t want to have to learn it or use them to save time rather than from a lack of skill
Many people would disagree with you (well the retry system alone might not be hard, but it’s the combination of all the things)
Maybe you should consider making your own datastore module if you can make it so simple and easily 
Do you really think that every Datastore Module is faster than his predecessor?
No? What makes you think that I said that?
I already got my own methods, but I will not create a Datastore Module. People should start learning how things work and not just using modules everywhere.
Then why should I use one of the 200 existing modules?
who asked
Fair point
ok
who asked
ok, then I guess it’s solved here
no way you continued
what are you doing in #resources:community-resources
totally haven’t heard that before
nobody’s trying to convince you lol
Congratulations, you have hereby contributed absolutely nothing to this topic.
8 Likes
Hey there,
Thanks for the (1) nice message on this post. I would like to point out I am completely rewriting the system to be “Nicer”, “More Optimized”, and “Better”. I am heavily redesigning it to be much much better. stay tuned (i think 
)
1 Like
Hey there,
Currently this project i wrote was just something simple for people to use… Didn’t know someone could get so hostile on the topic. Currently, we use it because it uses SubReq (a “connector”).
Over the next few months, I will be heavily overhauling the system to be much much easier.
Don’t get discouraged from posting more modules in #resources:community-resources, keep up the good work
If there are three types of modules you should probably avoid posting here, it would be anitcheats (especially client sided), signal libraries and datastore modules. Otherwise, if you make a more unique module that is useful, you shouldn’t encounter this…
Not to discourage you from improving your datastore module though, but yeah
1 Like
Do you have any ideas for a better module? I just make random modules for fun and hope it does decent
Oh buddy I think you have a lot to learn.
3 Likes