Build settings configuration in Unity

Introduction

Build settings configuration helps you choose how and where your game or app will run. It sets up the platform, scenes, and options before making the final build.

When you want to create a version of your game for a specific device like PC, mobile, or console.

When you need to select which scenes should be included in the final game build.

When you want to change build options like development mode or compression.

When you want to switch between platforms to test your game on different devices.

When preparing your game for release or testing on a new platform.

Syntax

Unity

using UnityEditor;

// Set build target
EditorUserBuildSettings.SwitchActiveBuildTarget(BuildTargetGroup.Standalone, BuildTarget.StandaloneWindows64);

// Define scenes to include
string[] scenes = {"Assets/Scene1.unity", "Assets/Scene2.unity"};

// Build player
BuildPipeline.BuildPlayer(scenes, "Builds/MyGame.exe", BuildTarget.StandaloneWindows64, BuildOptions.None);

You use EditorUserBuildSettings to change the platform you want to build for.

BuildPipeline.BuildPlayer creates the final game with chosen scenes and options.

Examples

This switches the build target to Android platform.

Unity

EditorUserBuildSettings.SwitchActiveBuildTarget(BuildTargetGroup.Android, BuildTarget.Android);

This builds the Android app including only the MainScene.

Unity

string[] scenes = {"Assets/MainScene.unity"};
BuildPipeline.BuildPlayer(scenes, "Builds/MyGame.apk", BuildTarget.Android, BuildOptions.None);

This builds a Windows development version with debugging enabled.

Unity

BuildPipeline.BuildPlayer(scenes, "Builds/MyGame.exe", BuildTarget.StandaloneWindows64, BuildOptions.Development);

Sample Program

This script switches the build target to Windows 64-bit, includes two scenes, and builds the game executable. It then logs a message when done.

Unity

using UnityEditor;
using UnityEngine;

public class BuildScript
{
    public static void BuildWindowsGame()
    {
        // Switch to Windows 64-bit build target
        EditorUserBuildSettings.SwitchActiveBuildTarget(BuildTargetGroup.Standalone, BuildTarget.StandaloneWindows64);

        // Scenes to include in build
        string[] scenes = {"Assets/Scene1.unity", "Assets/Scene2.unity"};

        // Build the player
        BuildPipeline.BuildPlayer(scenes, "Builds/MyGame.exe", BuildTarget.StandaloneWindows64, BuildOptions.None);

        // Inform user
        Debug.Log("Build complete: MyGame.exe");
    }
}

Important Notes

Build scripts run inside the Unity Editor, not in the final game.

Make sure all scenes you want are added to the build scenes list.

Switching build targets can take some time as Unity reimports assets.

Summary

Build settings configure where and how your game is built.

You select platform, scenes, and options before building.

Use build scripts to automate building inside Unity Editor.

Practice

1. What is the main purpose of Unity's Build Settings window?

easy

A. To debug runtime errors in the game

B. To write game scripts and logic

C. To select the target platform and scenes for building the game

D. To design game UI elements

Solution

1. Step 1: Understand Build Settings role

   The Build Settings window is where you choose the platform (like Windows, Android) and which scenes to include in the build.

2. Step 2: Differentiate from other windows

   Writing scripts, designing UI, and debugging happen in other parts of Unity, not Build Settings.

3. Final Answer:

   To select the target platform and scenes for building the game -> Option C

4. Quick Check:

   Build Settings = platform + scenes selection [OK]

Hint: Build Settings = choose platform and scenes before building [OK]

Common Mistakes:

• Confusing Build Settings with script editor
• Thinking Build Settings is for debugging
• Assuming UI design happens here

2. Which of the following is the correct way to add a scene to the Build Settings scenes list in Unity Editor?

easy

A. Add the scene path in the Player Settings

B. Write the scene name in the Console window

C. Create a new script and reference the scene

D. Drag the scene file into the Scenes In Build list in Build Settings

Solution

1. Step 1: Identify how to add scenes in Build Settings

   In Unity Editor, you add scenes by dragging them into the Scenes In Build list inside the Build Settings window.

2. Step 2: Eliminate incorrect methods

   Writing scene names in Console, adding paths in Player Settings, or scripting references do not add scenes to the build list.

3. Final Answer:

   Drag the scene file into the Scenes In Build list in Build Settings -> Option D

4. Quick Check:

   Add scenes by dragging into Build Settings list [OK]

Hint: Drag scenes into Build Settings list to include them [OK]

Common Mistakes:

• Trying to add scenes via Console or Player Settings
• Assuming scripts add scenes automatically
• Not opening Build Settings before adding scenes

3. Given this C# build script snippet in Unity Editor:

using UnityEditor;
class BuildScript {
  static void BuildGame() {
    string[] scenes = {"Assets/Scene1.unity", "Assets/Scene2.unity"};
    BuildPipeline.BuildPlayer(scenes, "Builds/MyGame.exe", BuildTarget.StandaloneWindows64, BuildOptions.None);
  }
}

What will this script do when run inside the Editor?

medium

A. Build a Windows 64-bit executable including Scene1 and Scene2

B. Build a MacOS app ignoring the scenes

C. Throw a compile error due to missing namespace

D. Build an Android APK with default scenes

Solution

1. Step 1: Analyze BuildPipeline.BuildPlayer parameters

   The script specifies scenes array with two scenes, output path "Builds/MyGame.exe", target platform StandaloneWindows64, and no special options.

2. Step 2: Understand effect of parameters

   This means it builds a Windows 64-bit executable including the two scenes listed.

3. Final Answer:

   Build a Windows 64-bit executable including Scene1 and Scene2 -> Option A

4. Quick Check:

   BuildPlayer with Windows target = Windows exe build [OK]

Hint: Check BuildTarget and output path to identify build platform [OK]

Common Mistakes:

• Confusing BuildTarget platform
• Assuming scenes are ignored
• Thinking script causes compile error

4. You wrote this build script in Unity Editor:

using UnityEditor;
class BuildScript {
  static void BuildGame() {
    string[] scenes = {"Assets/Scene1.unity", "Assets/Scene2.unity"};
    BuildPipeline.BuildPlayer(scenes, "Builds/MyGame.exe", BuildTarget.Android, BuildOptions.None);
  }
}

But the build fails with an error about invalid output path. What is the likely cause?

medium

A. The output path "Builds/MyGame.exe" is invalid for Android builds

B. The scenes array is empty

C. BuildTarget.Android is not supported in Unity

D. BuildOptions.None disables building

Solution

1. Step 1: Check output path for Android build

   Android builds require output files with .apk or .aab extensions, not .exe files.

2. Step 2: Identify mismatch causing error

   Using "Builds/MyGame.exe" for Android causes invalid path error because .exe is for Windows builds.

3. Final Answer:

   The output path "Builds/MyGame.exe" is invalid for Android builds -> Option A

4. Quick Check:

   Android build needs .apk or .aab output [OK]

Hint: Match output file extension to platform (e.g., .apk for Android) [OK]

Common Mistakes:

• Using Windows .exe extension for Android builds
• Assuming BuildTarget.Android is unsupported
• Thinking BuildOptions.None disables building

5. You want to automate building your Unity game for both Windows and Android platforms using a single script. Which approach correctly handles setting the build target and output path for each platform inside the script?

hard

A. Use one BuildPipeline.BuildPlayer call with BuildTarget.StandaloneWindows64 and output .exe for both platforms

B. Use BuildPipeline.BuildPlayer twice with different BuildTarget and matching output paths (.exe for Windows, .apk for Android)

C. Use BuildPipeline.BuildPlayer with BuildTarget.Android and output .exe file

D. Change Player Settings manually before running the script

Solution

1. Step 1: Understand multi-platform build requirements

   Each platform requires a separate build call with correct BuildTarget and output file extension.

2. Step 2: Identify correct scripting approach

   Calling BuildPipeline.BuildPlayer twice, once for Windows with .exe output, once for Android with .apk output, automates both builds properly.

3. Final Answer:

   Use BuildPipeline.BuildPlayer twice with different BuildTarget and matching output paths (.exe for Windows, .apk for Android) -> Option B

4. Quick Check:

   Separate calls per platform with correct output = correct build [OK]

Hint: Build each platform separately with correct target and output file [OK]

Common Mistakes:

• Trying to build multiple platforms in one call
• Using wrong output file extensions
• Changing Player Settings manually instead of scripting