Adjust game settings between releases.

 Manage configuration values outside your game binary. Update settings that your game already reads and applies, such as supported gameplay parameters or feature switches.
Review integrationExplore products
Value types and defaults
Retrieval and caching
Publishing workflow
Contextual draft · Release status, supported versions, and limits await owner review.

Plan the integration

Value types and defaults

 Define settings the client understands and safe defaults for every value, such as a supported reward multiplier.

Retrieval and caching

 Choose how the client retrieves settings, caches values, and behaves when it cannot reach the backend.

Publishing workflow

 Test a setting in a separate environment before publishing it. Keep client compatibility part of the review.
ILLUSTRATIVE GAME WORKFLOW

change a reward multiplier that the released client already supports.

 This example describes a game-team workflow. Service connections and game rules require explicit integration; it does not imply automatic bindings.

Scope and responsibilities

 Settings can change behavior already implemented in a released client. They cannot add arbitrary new client features. Supply safe offline defaults.

Related services

 Explore complementary services for your game, with integration details for each building block.
SERVICE 1

Cloud Script

 Run game logic behind your player experience. Explore Cloud Script
SERVICE 2

Analytics

 Understand what happens across the player journey. Explore Analytics

Setup prerequisites

A test workspace with access to Remote Config.
Step 1: pending
A confirmed API version and documented permissions for the workflow.
Step 2: pending
Client and backend tests for successful, invalid, repeated, and interrupted requests.
Step 3: pending
Review integration availability →
YOUR NEXT CHAPTER STARTS HERE

Build the backend for your next game.

 Explore the services and plan your first player experience.
Create GameIntegration overview