I know this too. I need to know if it counts towards that 1 MB limit or no.
In my case, Key will take roughly 30% of DataStore, and Value - 70% in a in-game report system.
as i know the 1mb for the value and the key does not take from the 1mb
does this limit also include previous versions of keys?
When will we be able to atomically update two datastore keys at once
when earth freezes over
[hello blockate]
Look, I get your point, but you are overreacting a little.
I have around ~900 worlds in my game right now, and people can build anything in said worlds. I have to extend them into multiple keys because I hit the 4MB key limit. The world with the most blocks has 200 keys [361k blocks] not including sub-instances. You can place unlimited blocks.
Check this out:
Thinking about it.
If Roblox is reducing data storage for keys from 4mb to 1mb, they should totally give us access to some common compression algorithms like what ZIP and 7-ZIP uses.
Even though not many games and experiences surpass the storage limit, I do notice here that some people separate their data across multiple keys as a result of data that doesn’t fit within the current 4mb or future 1mb limit.
With such limits in place I think it’s very important that we have some APIs and functions that let us read how much storage space is used/left over, see how large our keys are and utilize compression for strings, buffers and tables in-experience through Luau.
If I remember, the 7-ZIP compression algorithm is open-source and has a pretty permissive license that let’s you use it everywhere.
Not only that, it’s also one of the best compression algorithms that exists today for general data compression.
I’m going to write this here as it’s a more accurate topic:
I would like the cap to increase by 4 MB per player rather than 1 MB.
While this still isn’t ideal, allowing us to use the full DataStore per player would be a compromise that I can accept. It’s also odd that you give us 4 MB per DataStore but not 4 MB per player.
I go into this a bit more in this reply, and related quotes/replies: