Openblox (my OpenCloud wrapper written in typescript) now supports the new CreateUniverseSnapshot endpoint.
import "dotenv/config";
import { setConfig } from "openblox/config";
import { StandardDataStoresApi_V2 } from "openblox/cloud";
setConfig({ cloudKey: process.env.CLOUD_KEY })
;(async () => {
const { data:snapshot } = await StandardDataStoresApi_V2.createStandardDataStoreSnapshot({ universeId: 5097539509 })
console.log(snapshot)
})();
Is there a way to lower the hour limitation for new versions to save? I prefer the old behavior where it updates on each save because it helps when pinpointing where data loss occurs.
how do i start a new Universe? does it allow sharing DataStores between places?
long overdue,
glad it’s finally here! 
This new behavior will apply to all experiences. We do acknowledge that you lose a level of granularity when debugging issues, but this change is necessary to continue improving the versioning system.
By using snapshots when you update your experience, you can ensure you have the most recent pre-update data available to revert to if the update leads to data loss. If the data loss occurs outside of an update/snapshot, you will still have previous versions at most one hour “stale”.
We’re investigating how we can give creators more control over this system. If you have any other ideas or insights, please open up a feature request!
Yes! Data Stores share data across all places in an experience. Experiences are sometimes referred to as universes.
This article has more information on publishing multiple places to the same experience/universe.
Would it be possible to retain all versions for a key within 24-48 hours of a save? I imagine many of us could forget/may never know or understand the concept of making a data snapshot.
When will automatic retry finally get implemented?
For now, the one-version-per-hour rule will be applied. We’ll keep this feedback in mind for the future.
Even if you don’t use snapshots, you’ll still have access to one version each hour, including the most recent version.
Hi! Which method are you referring to? We do make recommendations for which errors to retry on in our error code reference.
This is great, but may I please ask if this is still planned for datastores and is there any release date for when this may be?
I don’t have access to feature requests, so I figure this thread would make the most sense to ask. Is there a possibility of an in house SQL like store? A lot of the times querying by just only one key isn’t feasible.
Is anyone else who uses Profile Service experiencing issues with this recent data stores update?
Save your player data with ProfileService! (DataStore Module) - Resources / Community Resources - Developer Forum | Roblox
I wonder if in the future profileservice would become the next datastore2 in the future, since roblox did say they were planning to add things like session locking and what not.
Hi! We designed these changes with packages like ProfileService in mind, so you shouldn’t face any related issues.
We appreciate all of this feedback about the future of Data Stores.
At this time we don’t have any updates to announce, but we’re continuously thinking about how we can enhance our data storage offerings. Stay tuned for more in the future!
I like the update. However, isn’t there still a concern that you may automatically save a faulty CreateUniverseSnapshot and have nothing to revert to?
Is the endpoint also easily accessible to retrieve data from and if I am correct keys are saved individually after creating your first snapshot, or saves a snapshot of the whole datastore at once?
CreateUniverseSnapshot always adds to the versions saved in your Data Stores. It does not delete or remove previously saved versions. It snapshots all of the Data Stores in an experience. See this reply for more information:
This topic was automatically closed 120 days after the last reply. New replies are no longer allowed.