Configuring your Project for Unity Remote Config

Requirements

• Unity Remote Config requires Unity version 2018.3 or higher.
• Set your Editor scripting runtime to .NET 4.X Equivalent (or above).
  • Upgrading a project from Unity 2018 or pre LTS 2019; developers no longer need to set the Scripting Runtime in the Editor. The option to change the Scripting Runtime version was removed after Unity 2019.2 https://docs.unity.cn/Manual/UpgradeGuide2019LTS.html#NET
• Set your API Compatibility Level to .NET 4.x.
• Enable Unity Services for your Project.
• Install the Remote Config package (detailed below).

Installing the Remote Config package

See documentation on packages for more information on working with packages in a Project. These steps may vary depending on which version of the Unity Editor you’re using.

Verified Release

1. In the Unity Editor, select Window > Package Manager.
2. From the Package Manager Window find Remote Config in the Packages List View and select it
3. In the Package Specific Detail View select the version and install to import the package into your Project

Preview Release

1. In the Package Manager Window the Advanced button will allow you to toggle Preview Packages making them visible in the Package List View
2. Follow the instructions for the Verified Release Installation (directly above this section)

Beta Customers

Upon receiving the Remote Config package from your account manager, follow these steps:

1. Download and unzip the package.
2. In the Unity Editor, select Window > Package Manager.
3. Click the plus (+) button at the bottom of the Package Manager window to open the Add package from disk... dialog.
4. Locate the package.json file inside your unzipped copy of the Remote Config package.
5. Click Open to import the package into your Project.

See documentation on packages for more information on working with packages in a Project. These steps may vary depending on which version of the Unity Editor you’re using.

Remote Config Environments

To get started, create an environment and give it a name.

1. Go to the Web Dashboard.
2. Select the corresponding project.
3. Select Add Environment.
4. Enter a name for the environment and select Create.

Note environment names are immutable.

The first environment you create is set as the default environment. This is the environment which is requested unless otherwise specified by the client. You can assign the default environment to an EnvironmentID in the Web Dashboard, or via the REST API.

Once you’ve configured your project, configure your game overrides and settings in the Web Dashboard