Finally understood how to create a DataStructure after 6 hours of pure straight coding and debugging. so, how many keys would there need to be for me to switch over to an ordered DataStructure?
COMMUNITY QUESTION
At what point do you use an ordered DataStructure over a non ordered DataStructure?
1 answer
It's not about how many keys there are, it's about what you want to do with them. An ordered datastore is like having a giant list, which can be sorted, compared to a regular datastore which is just a key value database.
The difference in implementation is of course that the ordered datastore is good for stuff like leaderboards, but not things like storing specific details like the amount of coins a Player has or what stage they're on.
This discussion is preserved as it was. New answers, comments, and votes are closed.
6 comments
So if I have a list that contains 20 keys, I do not need to worry about switching over to Ordered dataStore?
It's not about how many keys there are, it's about what you want to do with them. I literally explained that in my answer.
they are data values what more can i explain/...
I don't know what more I can explain dude I've literally told you what the difference is and example use cases.
they are leaderboard stats set up. but it is not using a leaderboard it represents stats you gAain playing the game
You don't need to be using Ordered DataStores. Just stick with DataStores.