Master data management

General specification of master data to be set up in GS2 microservices.

definition of terms

Model Masterdata that does not change for each game player that is temporarily registered by the Master Data Editor
modeldata that does not change for each game player that is used from within the game
PropertiesData that is different for each game player created based on the model

Game elements include item parameters, quest composition data, and other data that does not change from player to player. There is data that does not change from one player to another, such as item parameters and quest composition data. Such data is called a model in GS2. The data that is transformed from models into data possessed by players is called properties.

General master data corresponds to a model in GS2, and there is a concept of a model master in GS2. The difference between a model and a model master is that the content of the data is the same, but the difference is whether or not the data is actually accessible by the game.

Data that can be edited on the GS2 administration screen is a model master, and when it is converted to a state that can actually be used in the game, it becomes a model. The reason this conversion process is necessary is so that all changes to the model master are reflected in the game at once. Without this process, data updated in the administration screen will be reflected in the game.

Create master data

This conversion process is a mechanism for exporting all model masters to JSON format files and uploading the JSON files to reflect them as models all at once. You can use the model masters by manipulating them on the GS2 Administration screen and exporting them to JSON format files, or you can create your own management tool, such as Excel, and reflect the data in models without registering any model masters on GS2.

You can also manage master data in GS2 Deploy templates. In this case, it will be easier to use version control tools such as git, so please consider this option as well.

Please manage master data in a way that is convenient for your organization.

GS2TemplateFormatVersion: "2019-05-01"
Description: GS2 master data template Version 2010-06-26

    NamespaceName: inventory

    Type: GS2::Inventory::Namespace
      Name: ${NamespaceName}

    Type: GS2::Inventory::CurrentItemModelMaster
      NamespaceName: ${NamespaceName}
      Settings: # The data from here down is originally specified in JSON, but can be written as yaml and reflected
        version: 2019-02-05
          - name: item
            metadata: ITEM
            initialCapacity: 40
            maxCapacity: 60
              - name: item-0001
                metadata: ITEM_0001
                maxCount: 99
                sortValue: 1
              - name: item-0002
                metadata: ITEM_0002
                maxCount: 99
                sortValue: 2
              - name: item-0003
                metadata: ITEM_0003
                maxCount: 99
                sortValue: 3
          - name: character
            metadata: CHARACTER
            initialCapacity: 30
            maxCapacity: 50
             - name: character-0001
               metadata: CHARACTER_0001
               maxCount: 1
               sortValue: 1

      - Namespace