Is there anything that makes this different/better than Datastore2?
2 Likes
That’s not the point,
Additionally, makes the module more trustworthy before inserting.
2 Likes
ohh okay i get you now thanks for the feedback i will add a pastebin
2 Likes
imo its easier for beginners to understand does mostly the same thing
1 Like
No need to reinvent the wheel — assert exists.
assert(typeof(Player) == "Instance", string.format("bad argument #1 to LoadData (Instance<Player> expected, got %s)", typeof(Player)))
assert(typeof(ObjectsToLoad) == "table", string.format("bad argument #2 to LoadData (table expected, got %s)", typeof(ObjectsToLoad)))
8 Likes
I completely agree, I don’t see how this will be used more than datastore2, it’s programmed a bit inefficiently.
For example:
Datastore2 has bindtoclose and autosaving functions, which makes it significantly better than this module
Nice job, I will be looking to use this maybe.
1 Like
This module forces me to give it some sort of ValueBase instance (e.g. a StringValue) so I can save its Value.
What if I wanted to not do this? I am forced to create a new StringValue just for the sake of saving a string.
We should not be forced to use ValueBases just for the sake of saving data.
Also
Why does it use :UpdateAsync if you aren’t actually using the data parameter?
3 Likes
In what way does this differ from ROBLOX’s default datastores or an already existent module similar to what this does called DataStore2? (How to use DataStore2 - Data Store caching and data loss prevention)
1 Like
It doesn’t do the same thing, this module is really lack-luster.
Oh okay. Thanks for the quick response. 
Well a suggestion I have to your code is instead of making two separate methods for table data and normal data, combine it into one and simply check which type it is. OR perhaps create a class called datastore_value and allow users to put the data they want to store in there and use it for a saving method.
2 Likes
Wouldn’t UpdateAsync work better instead of SetAsync?
1 Like
yes this uses UpdateAsync im planing on updating it a bit to make it even better
Ive used this module for a bit now and Ive got a few things to mention.
1.) What makes this any better than Datastore2?
I know it is unique in its own way but why would people want to use this over DS2?
2.) Makes for easier saving and takes up less time to write an enitre Datastore.
It does cut some time off of making a completely new Datastore but it doesnt really make much of a difference.
3.) Maybe it should be possible to write some auto saving functions as mentioned by @recanman
Aside from this though, I think this is a really neat module and it could be used by more begginer programmers to give them a nice feeling to what a real datastore Should look like.
2 Likes
Hi.
I’m aware this is a VERY late reply, however, I’m curious about this system.
Does this bypass the rate-limits for datastores, similar to DataStore2? How secure is it? If you wish, we can get in contact over discord @ luc#8934
look at the source code, its pretty simple
What do I do if I’m trying to change a Value? Do I do Load_Table_Data each time I do?
Just change it normally! This module only loads and saves data!