I would like Build Profiles to help me discover and manage Scripting Defines

I’m testing the new Build Profiles feature in Unity 6 and I have some feedback. It’s great and I hope it gets expanded upon.

In a given profile, you can put multiple Scripting Defines. When your project is composed of multiple dozens of packages, it can be hard to discover, understand and manage every Scripting Define. I’d love it if the Build Profiles window could help me do that.

We have an in-house tool that helped us with Scripting Defines and I wanted to share how it works in the hope that the Build Profiles feature can be improved for everyone.

In our in-house tool, we have a catalog of Scripting Defines. Each entry is accompanied by a description that explains its purpose.


The Scripting Defines Descriptions can be added manually by the user (not great…) or they can be provided by the packages themselves! At the moment, assembly attributes are used to declare them.

[assembly: DeclareScriptDefineSymbol("UNITY_X_LOG_ASSERT", "Enables asserts with Log.Assert(..). If disabled, all calls to these methods are stripped from the build.")]

With the Defines catalogued, it becomes much easier for the user to configure build profile.

1 Like

Hi msfredb7,

Thanks for taking the time to share this feedback. It’s really interesting to see how customers were solving these issues before build profiles, and some of these tools you have here are similar to what other customers are doing. We’re looking at potential enhancements relating to build profiles for future versions of Unity right now and so I will make sure this feedback is captured and is reviewed before we plan future updates.

Thanks again.

1 Like