Chunks Used in Chat #78

**Introduction** In this page you’ll find… - The basics of Game Settings - Creating Overrides **Table of Contents** * * * # Getting Started with Game Settings Game Settings are the core of Game Server, and they are used to configure the game and distribute the settings to players using a set of Rules and Overrides.  # What are Game Settings? Game Settings are the basic configurations required to configure the game, such as: - Amount of initial coins - Coin reward for winning the Daily Challenge - Delay before hint animation - Onboarding Decks You can edit the settings using Game Server via Rules and Overrides, which we’ll explain below in this guide! # What’s Base Config? Base Config is the main configuration that includes all basic settings that are common for all users. Base Config, however, does **not** have rules enabled, and has a priority of zero by default. You can access the Basic Config for each game by selecting your application, and navigating to Game Settings. .gif?version=1&modificationDate=1656335401433&cacheVersion=1&api=v2&width=442&height=211) Inside Base Config, you’ll find the basic game settings per application categorised under tabs. The number next to each tab title shows the amount of settings enabled in each category. Base Config is editable, but if you want to send a specific set of values to a group of users, you’ll have to create an **Override**. **Enabled and Disabled Fields** All of the attributes in Game Settings can be enabled or disabled. In the page, there are two sections:  - **Enabled Fields:** when a field is enabled, it will send the setting to the client. - **Disabled Fields:** if disabled, the setting will not be sent to the client. To enable a field, click the **[green + button]**   and add your values. If a setting is enabled, but you’d like to disable it in your override, click the **[red - sign]** **.**  # What are Overrides? Overrides are used to customise the game settings for specific user groups. Overrides will **only** be applied to a user if the user complies with a set of rules that you will set up to differentiate groups of users. However, if the 2 overrides apply to different settings, the user can receive both overrides depending on the rules defined in each of them. ## When should you use overrides? Overrides are used when you want to send a different value from what it is established in Base Game for each setting. This means a user can receive settings both from Base Config and Overrides based on the rules you apply. ## How does Game Server determine what to send to the client when a player starts a game? 1. Game Server determines the list of configs (Base and Overrides) that match a specific user and **sorts them by priority from lowest to highest.** 2. Set all enabled attributes from Base Config 3. Set/Rewrite the attributes from overrides started from lowest and ending with highest priority. ### **Which values would a player get in response?** As the server sorts the configurations, the client will receive the attributes with higher priority first. If the attribute is disabled, then, Game Server moves onto the next attribute with higher priority. Let’s use the table below as an example configuration. In this case, we have overrides that have rules which overlap or target identical segment of players. Taking that into consideration, the client will receive the settings in Override #2 as the have the highest priority for Attributes #1 and #2, but as the Attribute #3 is disabled, Game Server resorts to Override #1. - Attribute 1 = 30 (from Override #2) - Attribute 2 = “60” (from Override #2) - Attribute 3 = 6.5 (from Override #1) |   | **Base Config** | **Override #1** | **Override #2** | | **Priority** | **0** | **1** | **2** | | **Attribute 1: Points for Placing** | 10 | 20 | 30 | | **Attribute 2: Points for Combos** | _disabled_ | 50 | 60 | | **Attribute 3: Points for Streaks** | 5.5 | 6.5 | _disabled_ | Now let’s try the same with overrides that target the same segment of users but… - There’s 3 overrides that have the same value. - Overrides are disabled for an attribute. - Some attributes are disabled in Base Config. **Which values would a player get in response?** - Attribute 1 from Override 3, because even though they all have the same value, override 3 has higher priority. - Attribute 2 from Override 2, as it is disabled in Override 3, which has higher priority. - Attribute 3 from Game Settings, as this attribute is disabled in all overrides, so Game Server will send the value configured in Base Config. |   | **Base Config** | **Override #1** | **Override #2** | **Override #3** | | **Priority** | **0** | **1** | **2** | **3** | | **Attribute 1: Points for Placing** | 20 | 20 | 20 | 20 | | **Attribute 2: Points for Combos** | _disabled_ | 50 | 60 | _disabled_ | | **Attribute 3: Points for Streaks** | 5.5 | _disabled_ | _disabled_ | _disabled_ | ### Example and Results of Settings Configuration In the table below, you’ll find an example configuration to better visualise the results of your configurations: | | **Configuration in Game Server** | **API response from Server** | **Result on Client** | | --- | --- | --- | --- | | **Base Config** |  | "settings": { "player_initial_balance": 2000, "catalogue_on": true, ... } |  .png?version=2&modificationDate=1658905707384&cacheVersion=1&api=v2&width=232&height=502) | | **Override** |  | "settings": { "player_initial_balance": 15000, "catalogue_on": false, ... } |   | * * *

4. Add rules to your experiment. Once you’re done, click **[Save]** on the upper right corner.  Remember that users are assigned to variants in a random way inside the weights specified in the variants. **How is priority established in A/B Experiments?** **A/B Experiments and overrides are not exclusive** , and it is possible for a user to receive a setting from an A/B Experiments, and another setting from an override depending on the rules established.    In terms of priority, A/B Experiments are assigned first, followed by overrides. After that, Game Server applies the settings configured in Game Settings. 1. A/B Experiments 2. Overrides 3. Base Config Rules follow the same logic used in Overrides. In A/B Experiments, they’ll help segment the user groups that will receive the experiments, and remember that one user can match multiple experiments depending on the rules you set up!

Which values will a player get if you set up A/B Experiments and Overrides? In many cases, you’ll set up both A/B Experiments and Overrides in your game. **** , but as they are not the same type of entity, their priorities are different. In the table below, you’ll see an example of a configuration with 2 A/B Experiments and 1 Override. The user will receive: - Attribute #1 = 50 (from A/B experiment #2) as it has the highest priority - Attribute #2 = “world” (from A/B experiment #1) - Attribute #3 = 6.5 (from Override #1) as it has more priority compared to Base Config | | **Base Config** | **Override #1** | **A/B experiment #1** | **A/B experiment #2** | | --- | --- | --- | --- | --- | | **Priority** | **0** | **1** | **1\*** | **2\*** | | Attribute #1 | 10 | 20 | 40 | 50 | | Attribute #2 | “test” | “hello” | “world” | not added | | Attribute #3 | 5.5 | 6.5 | not added | not added |