Sign In Register

How can we help you today?

Start a new topic
Answered

Runtime Collections vs Metadata Collections

Difference between runtime and metadata collections is unclear.

It seems to me that runtime collections can be changed in game while metadata collections can only be read.

However, metadata collections speak of snapshots and say "When you publish a game the data in the metadata collections will also be published". I am confused as to what this means. Can metadata collections be changed after publishing the game without having to update the game?

Did you mean that I need to make another snapshot and publish the snapshot?


Could you provide an explanation of what metadata collections and game snapshots actually are?


How would one go for creating collections that administrators updates relatively frequently and are then read inside the game, such as e.g. news? The game should, be able to read the newest news as they are put in the collection.

Should runtime collections be used or metadata collections?

If metadata collections are used does that mean a new snapshot has to be created for every new news entry?


Best Answer

A snapshot is a a version of your configuration, that includes everything you configure in the portal (except runtime collections). This allows you to save the configuration for publishing later, or just to keep if you are about to make some potentially dangerous changes and you want to be able to revert to a good configuration if you have an issue.


Metadata collections are better used for infrequently changed configuration that you want to be versioned with your game. If you want to change the data in a metadata collection you need to change the data in preview, then snapshot the config, and publish the game.


Publishing means pushing the configuration from our preview servers (which are limited to 100 concurrent users, and used for development / test) to our production servers. This approach allow you to make changes without affecting live players and allows you to test and check you changes before you push them to all.


For you use case, you could use a runtime collection and save new entries to it from the portal. However, this does not give you the ability to preview what the article will look like. If you want the security of testing the new article fully then a metadata collection along with a publish might be better for you. If you take the runtime approach, then rolling back would require manual deletion of the article. Not a big deal in your case, but probably not advisable for more complex scenarios.


Publishing the game does not require any client side updates, it's just moving configurations between servers, it's quick and painless, and adds some good safeguards IMO


Gabriel






Answer

A snapshot is a a version of your configuration, that includes everything you configure in the portal (except runtime collections). This allows you to save the configuration for publishing later, or just to keep if you are about to make some potentially dangerous changes and you want to be able to revert to a good configuration if you have an issue.


Metadata collections are better used for infrequently changed configuration that you want to be versioned with your game. If you want to change the data in a metadata collection you need to change the data in preview, then snapshot the config, and publish the game.


Publishing means pushing the configuration from our preview servers (which are limited to 100 concurrent users, and used for development / test) to our production servers. This approach allow you to make changes without affecting live players and allows you to test and check you changes before you push them to all.


For you use case, you could use a runtime collection and save new entries to it from the portal. However, this does not give you the ability to preview what the article will look like. If you want the security of testing the new article fully then a metadata collection along with a publish might be better for you. If you take the runtime approach, then rolling back would require manual deletion of the article. Not a big deal in your case, but probably not advisable for more complex scenarios.


Publishing the game does not require any client side updates, it's just moving configurations between servers, it's quick and painless, and adds some good safeguards IMO


Gabriel





Thank you for the info!

Things are much clearer now. Snapshot-publish mechanism is brilliant!          

Login to post a comment