Note: Unity Remote Config is now available as a preview package. Remote Config is an improved offering that allows you to change the behavior and appearance of your game without requiring a new binary. You can remotely enable or disable features, change the specifics of your game to target specific audiences, or run special events by scheduling new content releases.
While you can view the keys and values of both configurations in the Editor, Unity only loads one configuration at runtime. Unity uses the Development configuration in Play mode and in any builds created with the Development Build box checked on the Build Settings window. Unity uses the Release configuration in non-development builds.
Before testing Remote Settings, you must first create the settings and then either use the Remote Settings component or write the code necessary to map the settings to variables in your game or application.
To test with the Development configuration, click the Play button in the Editor or:
Go to File > Build Settings to open the Build Settings window.
Check the Development Build box.
Click the Build And Run button.
To test with the Release configuration:
Go to File > Build Settings to open the Build Settings window.
Uncheck the Development Build box.
Click the Build And Run button.
To test whether your game behaves as expected on first run when no local settings are present, you can clear the Application.persistentDataPath directory. If you are testing in the Unity Editor, you must exit from the Editor before clearing the directory.
2017–05–30 Page published
2018–08–13 - Service compatible with Unity 5.5 onwards at this date but version compatibility may be subject to change.
New feature in 2017.1