Not bad. I was actually wondering how to move off DataStore2 without too much hassle. Gonna try it on some of my heavier projects.
Iâm hoping this action will require 2-step verification and must be done by the owner of the game (or group owner) to prevent hackers from destroying a game with a few clicks. The deletion should also be delayed by a week or so and email the owner that a deletion is pending. Thank you for assuring us this is being worked on!
1 Like
I am one of those a bit confused. I have always just had one datastore per game (idk if its called an experience, or universe or whatever) And it was always keyed by playerid.
However recently I started to add leaderboards, and the way I learned to do that, is to have an ordered datastore per leaderboard, so if I am keeping track of 10 traits to put on leaderboards, would that mean I would be likely to hit the new limits? How would you do leaderboards?
Itâs highly unlikely that a mere 10 leaderboards would ever use up enough data to put you over the limits.
What is being talked about here is using an unbounded number of keys per player. One key for each version of the data. So the longer the player plays the more data they accumulate. Thatâs bad.
As long as youâre storing a fixed maximum amount of data per player youâre good.
this hasnât been the case since premium came out
edit: i was thinking of the paying/non-paying limit distinction