I expect that there are bugs I did not find during testing. I can only think of so many scenarios myself. If you encounter anything weird, please let me know!
I created a video “tutorial” that walks through the basics. Most of it is self-explanatory:
This is so useful for me. Once a week I get a message saying someone’s roadbux got taken but they didn’t get their product. Now I can edit in their stuff without hardcoding <3
Edit: Watched some more of the video. You should make more hints for some of the UI. I would never have thought to click the empty data to create new data.
Totally! That’s called a breadcrumb. I’ll add that to the list too. It already internally stores this full path, so it will be really easy to add it to the display.
There is a scrollbar. I’ve tested it with long strings and it’s worked. Is it not working for you?
The JSON thing is good though, but I guess I would encourage people to simply save tables directly, since why not. However, lots of people have done that, so perhaps I can figure out how to implement something that will decode JSON strings and throw it into a table view.
When I first created the datastore I was under the impression that it was going to run out of data pretty quickly, and someone in the scripting helpers told me to json encode it to save data, lol.
Interesting. That TextBox is set to wrap text. I wonder why it’s not being wrapped? I’ll look into it and see. Maybe it’s a limitation of how TextBoxes wrap text on ROBLOX?
JSON encoding a table is a valid option when you’re trying to manage save data of potentially large size. I do it on my boat saving to guarantee write to datastore works.
