You should be able to see your current usage and limit in the Creator Hub now, under the new “Data Stores Manager” section. I’m currently under the assumption that this will barely affect most developers and use cases, however a building game like this would be an exception to that.
Out of the top 55 million experiences, there is a very small number of experiences, less than 30 total, that are currently over the limit.
Given this quote, I imagine most games probably don’t have to think about these problems and limits unless they were being overly excessive.
I’m assuming you’re calculating based off visits, but Roblox calculates per unique player that has ever played your experience. This is unobtainable publicly as far as I’m aware.
We shouldn’t have to rely on the amount of players that randomly join the game and leave.
As much as it is nice to have 4MBs of data per key, the increment of 1mb per user is VERY low. Games that store in-game player creations such as buildings, recordings, items, even multiple slots (which means the player is able to play multiple characters in the same game and they all have to save…). I can easily see that getting to more than 1mb per serious player.
The limit shouldn’t need to exist in the first place, if nobody’s hitting the limit anyway, outside of a few fringe cases, whats the point of adding it? It feels like a non issue that Roblox is doing to please investors with the lie that it’ll cut costs (when it really wont).
I’m being realistic. My personal experience is with a game that has considered moving player data off to a custom solution due to data store limits per key - I’m familiar with the problem. We’ve had to implement inventory limits and manually handle problems of data loss because of select players reaching the data limit constantly.
Despite this however, we still barely scratch at our total limit:
I’m not arguing against an increase to this limit, but it is lifetime players and not CCU/DAU/MAU/etc.
I’d personally love to see an increase to both per-key and total storage. I’m just trying to help clarify the reality most people will face as there’s a lot of confusion.
Yeah it’s bad, Roblox is now implementing a maximum datastore size for all experiences. Whilst most probably won’t hit this limit, voxel / world generated games are basically not possible anymore.
With the current cut roblox takes from your revenue, and the constraints they set on developers. Also being behind as an engine compared to other engines but still focusing all their efforts into ai tools no one needs.
it is bad for custom creation games which is made by small/new developers , in conc there is now a limit for the data you store in your experience “not per data store but per experience” which is 100 mb + 1 mb * life time users
This situation isn’t great, but the idea that it will kill smaller games is just wrong. You don’t even need 1MB in most cases. Let me break down how much space that actually is, because some people clearly don’t get it.
1 Megabyte = 1,024 kilobytes = 1,048,576 bytes.
That’s over A MILLION characters per player. Most datastore keys don’t even hit ONE kilobyte which can store over 1,000 characters alone.
It’s frustrating to see Roblox’s corporate side taking over again, but it’s not as bad as everyone’s making it seem.
I think people in this thread are drastically overexaggerating the effect this will have on sandbox games.
4MB has always been extremely generous–given any kind of thoughtful architecturing that should support enormous builds.
The only reason it would be a problem is if the vast vast majority of your players are building things over 1MB. This is not the reality of what will happen–a large amount of unique players don’t stick around for long, or won’t build enough to hit 1MB, which should be quite a large barrier for a sandbox game.
I’m really interested in seeing the usage/limit for one of these types of games if a developer can provide it. A lot of it also comes down to data storage method - if you’re making a really serious building game, you’d probably use a binary format for storage over storing all the objects and properties as JSON.
