Implement this interface to execute code at the start of the Player build process.
At the start of a Player build, Unity uses the IOrderedCallback.callbackOrder property on each implementation to determine the order in which to invoke the callbacks.
This callback can be useful for automated tasks and ensuring your build environment is correctly configured.
Example usages include:
Note: Build callbacks are a powerful feature, but it is strongly recommended that their implementations maintain deterministic build outputs.
The result of a build should be predictable and reproducible, based on the project’s content, the Unity version, and installed packages.
Introducing environment-specific behavior, external dependencies, randomness, or other non-deterministic elements can lead to outcomes
that are challenging to debug or reproduce. This unpredictability may also compromise the efficiency and accuracy of incremental builds or incremental upgrades.
Additional resources: BuildPlayerProcessor.PrepareForBuild, IPostprocessBuildWithReport, BuildPlayerProcessor, BuildPipeline.BuildPlayer.
using System; using UnityEditor.Build; using UnityEditor.Build.Reporting;
class BuildScheduleEnforcer : IPreprocessBuildWithReport { public int callbackOrder { get { return 100; } } public void OnPreprocessBuild(BuildReport report) { if (DateTime.Now.DayOfWeek == DayOfWeek.Thursday) // Force the build to fail. This message will appear in the console and Editor log. throw new BuildFailedException("No builds are allowed on Thursdays"); } }
OnPreprocessBuild | Implement this method to receive a callback before the build is started. |