7. Remote config
What remote config is for
Remote config is a set of named values your game reads at runtime: prices, timers, feature switches, event dates. Change them on the dashboard and every player gets the new values at their next start, with no new build.
Set it up
Open the app on SDK Apps and choose Remote config.
- Under Config keys, choose Add key. Each key has:
- a Key, its name in code;
- a Type: string, int, float, bool or JSON;
- a Value.
- Optionally choose Add override for a different value on some platforms, or for a range of app versions (From version, To version). The first matching override wins.
- Turn on Server only — sent to game servers, never to players for values players must not see, such as a bot's difficulty or a secret event date.
- Changes are saved to a draft: while there is one, the page says Unpublished changes and which version games still get. Choose Publish to send them to players.
Every publish is a numbered version. Versions lists them, and Roll back publishes an older one again.
The version gate and maintenance
Version gate and maintenance, on the same page, is separate from the config keys: it doesn't use Publish. It goes live when you choose Save on its card, and games see it on their next config read. The card's Live now line always shows what games get at that moment (maintenance on or off, the minimum versions, whether a notice is set), so you can check a change took effect. Until you save, the card shows Unsaved changes and Live now still shows the old settings.
| Field | What it does |
|---|---|
| Minimum version (per platform) | A build older than this gets Gate.updateRequired, so it can show an update screen |
| Store link (per platform) | Comes back as Gate.storeUrl, for the update button |
| Maintenance | On: every client gets Gate.maintenance, with your Message shown to players and the time it Ends, UTC (optional). Game servers still get their config |
| Notice (optional, shown however the game chooses) | Comes back as Gate.notice |
Script 3.1 shows a client checking the gate at boot.
Read values in the game
McApp.StartAsync fetches config. After that, the getters answer at once from memory and work offline. The last fetched values are saved on the device, so an offline start uses real values rather than the fallbacks in your code.
Script 7.1: Read config values
using MultiConnect.App;
using UnityEngine;
public class ShopTuning : MonoBehaviour
{
private void OnEnable()
{
McAppConfig.Changed += Apply;
Apply();
}
private void OnDisable() => McAppConfig.Changed -= Apply;
private void Apply()
{
int dailyCoins = McAppConfig.GetInt("daily_coins", 100);
float botSpeed = McAppConfig.GetFloat("bot_speed", 1.0f);
bool eventOn = McAppConfig.GetBool("winter_event", false);
string banner = McAppConfig.GetString("banner_text", "");
Debug.Log($"Config v{McAppConfig.Version}: coins {dailyCoins}, bot {botSpeed}, event {eventOn}, banner '{banner}'");
}
}
Getters and events:
- The second argument of each getter is the fallback, used when the key doesn't exist.
GetJson(key)returns the raw JSON text of a JSON key, forJsonUtility.FromJson.McAppConfig.Changedis raised when a laterMcAppConfig.RefreshAsync()brings new values. CallRefreshAsyncwhen the game returns to the menu, so long sessions pick up changes.
On a server: McAppServer.GetConfigAsync() returns every key, including the server-only ones, as a dictionary.

