Chat #4

# Base Configs and Overrides in Game Settings This information is drawn from the **Game Settings Configuration** documentation. ## What are Game Settings? Game Settings are the core configurations used to set up your game and distribute those settings to players through a system of Rules and Overrides. Common examples include: - Amount of initial coins - Coin reward for winning the Daily Challenge - Delay before hint animation - Onboarding Decks --- ## Base Config Explained **Base Config** is the main configuration that serves as the foundation for all game settings. Here are its key characteristics: | Aspect | Details | |--------|---------| | **Purpose** | Contains all basic settings common to all users | | **Priority** | 0 (lowest priority by default) | | **Rules** | Does **not** have rules enabled | | **Enabled/Disabled Fields** | Can have individual fields enabled or disabled | | **Editability** | Fully editable | ### How to Access Base Config Navigate to your application and select **Game Settings** to access the Base Config for each game. Settings are organized under tabs, with a number next to each tab title showing how many settings are enabled in that category. .gif?version=1&modificationDate=1656335401433&cacheVersion=1&api=v2&width=442&height=211) ### Field States in Base Config - **Enabled Fields**: When a field is enabled, the setting will be sent to the client - **Disabled Fields**: When disabled, the setting will **not** be sent to the client To enable a field, click the **green + button**. To disable an enabled field, click the **red - sign**. --- ## Overrides Explained **Overrides** allow you to customize game settings for specific user groups. They provide a way to send different values than what's established in Base Config to targeted players. ### Key Characteristics of Overrides | Aspect | Details | |--------|---------| | **Purpose** | Customize settings for specific user groups | | **Application** | Only applied to users who match defined rules | | **Multiple Overrides** | A user can receive settings from both Base Config and multiple Overrides if rules are met | | **Priority** | Can range from 1 to any higher number (higher = takes precedence) | | **Availability** | Can be set to **Test** (test devices only) or **Live** (all users, or test devices only in Staging) | ### When to Use Overrides Use Overrides when you want to: - Send different values to specific player segments - Test new configurations with a subset of users - A/B test different game mechanics - Distribute regional or time-based configurations --- ## How Game Server Determines What Settings to Send When a player starts a game, Game Server follows this process: 1. **Identifies matching configurations**: Determines which Base Config and Overrides apply to that specific user based on their rules 2. **Sorts by priority**: Arranges all matching configurations from lowest to highest priority 3. **Sets Base Config values**: Applies all enabled attributes from Base Config first 4. **Applies Overrides**: Sequentially applies Override settings, starting with lowest priority and ending with highest priority, **overwriting** any previous values **Important**: If an attribute is disabled in a higher-priority override, Game Server falls back to the next highest priority configuration that has that attribute enabled. --- ## Practical Example: Priority and Attribute Resolution Here's how Game Server handles overlapping configurations: | Configuration | Priority | Attribute 1: Points for Placing | Attribute 2: Points for Combos | Attribute 3: Points for Streaks | |---|---|---|---|---| | **Base Config** | 0 | 10 | *disabled* | 5.5 | | **Override #1** | 1 | 20 | 50 | 6.5 | | **Override #2** | 2 | 30 | 60 | *disabled* | **What a player receives:** - **Attribute 1**: 30 (from Override #2 - highest priority) - **Attribute 2**: 60 (from Override #2 - highest priority) - **Attribute 3**: 6.5 (from Override #1 - disabled in Override #2, so falls back) ### Configuration-to-Client Example  When Base Config is set with specific values, the API response sends them to the client: ```json "settings": { "player_initial_balance": 2000, "catalogue_on": true } ``` This translates to the visual settings displayed in-game.  When an Override applies to a matching user, it overwrites the Base Config values: ```json "settings": { "player_initial_balance": 15000, "catalogue_on": false } ``` --- ## Creating an Override To set up an Override: 1. Click the green **[New]** button in the Overrides section 2. Configure the Override with: - **Name**: Descriptive identifier - **Status**: Active/Inactive - **Priority**: Numeric value (higher = takes precedence) - **Availability**: Test or Live - **Labels**: Optional tags for tracking 3. Enable fields using the **green + sign** and set values 4. Define **Rules** to specify which users receive this Override 5. Click **[Save]** to complete ### Optional Override Features - **Start At / End At**: Schedule when an Override becomes active and when it expires (Note: the system does not automatically deactivate at End At date) - **Override A/B Experiments**: Check this box to bypass ongoing A/B experiments (useful for emergencies). This moves the override to the top of the list with higher priority than OFF-toggle overrides - **Notes**: Add internal comments for context and traceability - **Find Setting**: Link the configuration to a specific game setting --- ## Key Differences: Base Config vs. Overrides | Feature | Base Config | Overrides | |---------|------------|-----------| | **Scope** | All users | Specific user segments (rules-based) | | **Priority** | 0 (fixed) | 1+ (customizable) | | **Rules** | No rules | Required to define target users | | **Primary Use** | Default game settings | A/B testing, regional variations, special events | | **Multiple per Game** | One Base Config | Multiple Overrides allowed | --- For more information on defining rules to target specific player groups, refer to the Rules documentation linked in the Game Settings guide.