Unity - Scripting API: BuildOptions.BuildScriptsOnly (original) (raw)

Suggest a change

Success!

Thank you for helping us improve the quality of Unity Documentation. Although we cannot accept all submissions, we do read each suggested change from our users and will make updates where applicable.

Close

Submission failed

For some reason your suggested change could not be submitted. Please try again in a few minutes. And thank you for taking the time to help us improve the quality of Unity Documentation.

Close

Your name Your email Suggestion*

Cancel

Description

Only build the scripts in a project.

Before you can use BuildScriptsOnly, you need to build the whole Project. Then you can run builds that only have script changes. Rebuilding the player data will be skipped for faster iteration speed.

Platforms which support the incremental build pipeline will automatically run scripts only builds if Unity detects that the data files have not changed, even if BuildScriptsOnly is not used. You can still use BuildScriptsOnly to force a script only build and ignore any pending player data changes.

The following script example uses BuildScriptsOnly. The script builds the entire Project initially. After you've run the script for the first time, you can use the script to only compile any changes you make to the script. To try this out, add the following Editor script and the game script to your project.

Attach the following simple script to an empty GameObject in the scene:

Now run the Build/Build scripts example. This builds an executable. Run that executable and a dark blue window with the label appears. Next add some cubes and spheres to the Project. Make the following script changes:

Finally, swap the commented lines in the EditorExample script:

Use the Build/Build scripts to regenerate the application and then launch it. The application will now show random changes to the background color. However the added cubes and spheres are not visible.