We are adding the ability to create and manage Environments in Unity Remote Config. Environments are a collection of configs and rules in Remote Config that are served to the Unity runtime. Developers can now manage multiple Environments with their Remote Config projects. Previously the Remote Config service included only two build environments: Release and Development. Starting with version 1.1.0, developers can create, update, and delete environments, choose the environment used in a build, and set a default environment (note: the Environment named “Development” is a reserved name). Note: for existing customers of Remote Config, the current behavior of the Development environment will change if you decide to upgrade to the new package 1.1.0. Previously, the Development environment is delivered automatically at runtime in the Editor and on debug builds. This will no longer be the case with the new package, and instead you will have to explicitly fetch the Development environment. This feature provides additional flexibility to our customers on managing projects with multiple contributors making changes to their Remote Config implementation. You can now create custom development workflows tailor-fit to your needs Some use cases include: The ability to create custom sandbox environments for your employees to avoid issues relating to collisions across each other’s rules/configs Used as a method of version control, where a specific environment can be designated for each breaking release of your game Custom client configuration where separate environments are distributed to separate versions of the app that is distributed to different clients For more information, refer to the updated Remote Config API docs or the package documentation. You can reach us directly with any support questions or needs at firstname.lastname@example.org.