Our game uses downloadables to store level asset bundles. Every weeks we add about 10 new levels (which is 40 new downloadables per week) while we are live. So the only way I can see to update the live update is the following:
-add 40 new downloadables in the workspace (preview)
-test the game with the preview service
-create a new snapshot and publish it
-then I delete the previously live snapshot
Is it the right way to do it?
If it is, do all the data (users, leaderboards...) is kept or it is lost everytime I publish a new snapshot?
The "copy" or "revert" on the live snapshot doesn't seems to do the job for this scenario
Best Answer
C
Customer Support
said
over 8 years ago
Publishing the snapshot doesn't affect any of the runtime data for the game (the only mongo writing we do is we update any meta collections they have, as these are read-only)
The approach you describe is correct, change in preview, validate, publish to live is the flow we encourage.
Any users and data stored in already existing leaderboards will be kept, the snapshot is just the configuration of your game.
Shane
1 Comment
Customer Support
said
over 8 years ago
Answer
Publishing the snapshot doesn't affect any of the runtime data for the game (the only mongo writing we do is we update any meta collections they have, as these are read-only)
The approach you describe is correct, change in preview, validate, publish to live is the flow we encourage.
Any users and data stored in already existing leaderboards will be kept, the snapshot is just the configuration of your game.
Christian Gauthier
Our game uses downloadables to store level asset bundles. Every weeks we add about 10 new levels (which is 40 new downloadables per week) while we are live. So the only way I can see to update the live update is the following:
-add 40 new downloadables in the workspace (preview)
-test the game with the preview service
-create a new snapshot and publish it
-then I delete the previously live snapshot
Is it the right way to do it?
If it is, do all the data (users, leaderboards...) is kept or it is lost everytime I publish a new snapshot?
The "copy" or "revert" on the live snapshot doesn't seems to do the job for this scenario
Publishing the snapshot doesn't affect any of the runtime data for the game (the only mongo writing we do is we update any meta collections they have, as these are read-only)
The approach you describe is correct, change in preview, validate, publish to live is the flow we encourage.
Any users and data stored in already existing leaderboards will be kept, the snapshot is just the configuration of your game.
Shane
Customer Support
Publishing the snapshot doesn't affect any of the runtime data for the game (the only mongo writing we do is we update any meta collections they have, as these are read-only)
The approach you describe is correct, change in preview, validate, publish to live is the flow we encourage.
Any users and data stored in already existing leaderboards will be kept, the snapshot is just the configuration of your game.
Shane
-
Documentation Notes
-
Design issues with user events
-
Using NoSQL
-
Runtime Collections vs Metadata Collections
-
Anonymous authentication from browser app
-
Modules
-
Movement With Unity
-
Problem with url parameters for downloadables
-
Querying NoSql GameSparks database
-
Challenge accesType
See all 2487 topics