For the complete documentation index, see llms.txt. This page is also available as Markdown.

Remote Config

You are reading the documentation for Bridge SDK v2. If you need the obsolete v1 documentation, see Documentation (v1).

Read game settings (difficulty, drop rates, feature flags, A/B values) from the platform at runtime. This lets you change behavior without shipping a new build. Available on a subset of platforms.

Fetch once at startup before gameplay, and always provide hardcoded defaults for every key. The request can fail, or the platform can return only part of your config.

Support

Check this before requesting remote values. If unsupported, use your local defaults.

bridge.remoteConfig.isSupported
Platform support · 1 of 26 platforms

Supports: yandex

Does not support: crazy_games, discord, dlightek, facebook, game_distribution, gamepush, gamesnacks, huawei, jio_games, lagged, microsoft_store, msn, ok, playdeck, playgama, poki, portal, reddit, samsung, telegram, tiktok, vk, xiaomi, y8, youtube

Set Context

Set dynamic game/player parameters used by the platform for config segmentation (for example, Yandex clientFeatures). Parameters accumulate across calls and are forwarded to the platform SDK on every get().

Call it before get() — for example, right after you know the player's segment.

bridge.remoteConfig.setContext({ segment: 'whales', level: 42 })

Load Values

Load remote values and merge them into your local defaults before gameplay starts. get() takes no arguments — pass segmentation parameters via setContext() beforehand.

Remote Config here is the platform feature (Yandex Remote Config). Bridge can also merge a remote copy of playgama-bridge-config.json over the local file on any platform — see the remoteConfigUrl option in Setup.

Last updated