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

Config

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

playgama-bridge-config.json is the SDK configuration file. It stores platform identifiers, ad placements, the product catalog, leaderboards, and other SDK settings. One file is shared by every platform: top-level values apply everywhere, and the platforms block overrides them per platform.

Use the config editor to create and update the file — it is the most convenient way to keep the structure valid.

File location

Place playgama-bridge-config.json next to your index.html — Bridge loads it from ./playgama-bridge-config.json, relative to the page.

WebGLTemplates/Bridge/playgama-bridge-config.json

Import the file into the Files folder of your project.

There is no separate file — the configuration is stored inside the extension. Open the Playgama Bridge extension in the editor, select the onFirstSceneLoaded function, and set the configuration there.

addons/playgama_bridge/template/playgama-bridge-config.json
datafiles/playgama-bridge-config.json

Import the file into res/web and add the /res folder to Bundle Resources.

Add playgama-bridge-config.json to your project files.

Example

{
    "platforms": {
        "game_distribution": {
            "gameId": "game_id"
        }
    },
    "advertisement": {
        "minimumDelayBetweenInterstitial": 60,
        "interstitial": {
            "placements": [
                {
                    "id": "level_completed"
                }
            ]
        }
    },
    "payments": [
        {
            "id": "coins_pack"
        }
    ],
    "leaderboards": [
        {
            "id": "main"
        }
    ],
    "achievements": [
        {
            "id": "first_win"
        }
    ]
}

Platform settings

The platforms block holds platform identifiers and per-platform overrides, keyed by platform id. When the game runs on a platform, the values from platforms.<id> are deep-merged over the top-level values — so any setting, including module sections, can be overridden for one platform only:

Last updated