When I go in Data Stores Manager in my game configuration, I noticed that my datastores have a huge amount of keys. I am wondering if this is supposed to happen or not since 2 different games have different data systems and the same thing is happening.
Example:
I did make sure I followed all correct instructions on the datastore2 documentation, and my saving system works well in both games.
Are you certain that that is caused by Datastore2? Is there any code that accesses datastores that isn’t using DS2?
If you look at the contents of e.g. global/1000, what are the contents? (Check normal datastores and ordered datastores).
Why not just write direct datastore logic?
Its literally incredible simple
session locking requires very few lines of code
mostly utilizing metadata to set job id and update timestamp
Turns out it was datastore 2. One of my old games that use DataStoreService didn’t have this issue. I ended up converting my data module to ProfileStore which fixed the keys duplicating.
This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.
