Alright so, to start this off, I am using Datastores for a game I’m working on. I am also way too familiar with having experience in the industry where certain things are possible there but, aren’t here.
For instance as this thread suggests, there’s no viable way to reset a datastore. I have to fallback to changing a key to anything other than itself and while this does work to an extent, it also causes issues in a test setting. I do not think that changing a datastore or the key works or should even be encouraged because of how poor practice that is.
If I was doing a database test in the real world, I would not… under any circumstance allow the key and the value attached to remain persistent in database even after I don’t need it. Why? Because, it’s a complete and total waste of space and can overwrite data you actually need. In addition, if you were to look at it visually, the entire table would be cluttered with entries which makes it harder for me to actually get whatever it is I need, done.
This brings me to studio. Even after I press stop, it still retains the same data. This poses an annoyance since as a developer, I am much more likely to make a mistake, ruin the entry and then, have to start all over again with another datastore name simply because, it doesn’t reset.
I’d appreciate if there was an option to treat datastores in studio as a temporary store so this way, it can reset (given that the developer wants to) and I wouldn’t have to stack up a bunch of datastores simply because of something dumb. Testing in studio should allow for dumb mistakes whereas production really shouldn’t.
If I am missing something, please let me know. So far, after a bunch of searching, I came up empty with anything that is remotely viable and wouldn’t increase the amount of entries for no good reason.