Build settings and scene order in Unity - Interactive Code Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the code to load the first scene in the build settings by its index.

Unity

SceneManager.LoadScene([1]);

Drag options to blanks, or click blank then click option'

A0

B1

C"MainScene"

DSceneManager.GetActiveScene()

Attempts:

3 left

💡 Hint

Common Mistakes

Using 1 instead of 0 for the first scene index.

Trying to load scene by name without quotes.

Using the active scene instead of the build index.

The first scene in Unity's build settings has index 0. Using LoadScene(0) loads that scene.

2fill in blank

medium

Complete the code to add a scene named "Level2" to the build settings scenes list.

Unity

EditorBuildSettingsScene newScene = new EditorBuildSettingsScene("Assets/Scenes/[1].unity", true);

Drag options to blanks, or click blank then click option'

ALevel1

BMainMenu

CLevel2

DGameOver

Attempts:

3 left

💡 Hint

Common Mistakes

Using the wrong scene name that does not exist.

Forgetting the folder path "Assets/Scenes/".

Not including the .unity extension in the path.

To add a scene to build settings, specify its path. Here, "Level2" is the scene name.

3fill in blank

hard

Fix the error in the code to correctly get the total number of scenes in build settings.

Unity

int sceneCount = [1].Length;

Drag options to blanks, or click blank then click option'

ASceneManager.GetAllScenes()

BEditorBuildSettings.scenes

CBuildSettings.scenes

DSceneManager.sceneCountInBuildSettings

Attempts:

3 left

💡 Hint

Common Mistakes

Using EditorBuildSettings.scenes which is editor-only.

Trying to call a method that does not exist.

Using incorrect property names.

SceneManager.sceneCountInBuildSettings returns the total number of scenes in the build settings.

4fill in blank

hard

Fill both blanks to check if the current active scene is the last in build settings.

Unity

bool isLastScene = SceneManager.GetActiveScene().buildIndex [1] SceneManager.sceneCountInBuildSettings [2] 1;

Drag options to blanks, or click blank then click option'

A==

B-

C+

D!=

Attempts:

3 left

💡 Hint

Common Mistakes

Using + instead of - when adjusting scene count.

Using != instead of == for comparison.

Mixing up the order of operands.

The active scene's build index equals the total scenes minus 1 if it is the last scene.

5fill in blank

hard

Fill all three blanks to create a dictionary mapping scene names to their build indexes for all scenes in build settings.

Unity

var sceneDict = new Dictionary<string, int>() {
  { [1], [2] }
};
for (int i = 1; i < SceneManager.sceneCountInBuildSettings; i++) {
  sceneDict.Add(SceneUtility.GetScenePathByBuildIndex(i).Split('/').Last().Replace(".unity", ""), i);
}

Drag options to blanks, or click blank then click option'

ASceneUtility.GetScenePathByBuildIndex(0).Split('/').Last().Replace(".unity", "")

B0

CSceneUtility.GetBuildIndexByScenePath("Assets/Scenes/Main.unity")

D"Main"

Attempts:

3 left

💡 Hint

Common Mistakes

Using wrong index or scene name for the first dictionary entry.

Not removing the .unity extension from scene names.

Using SceneUtility.GetBuildIndexByScenePath incorrectly.

This code initializes the dictionary with the first scene's name and index 0. It uses SceneUtility.GetScenePathByBuildIndex(0) to get the path, extracts the name, and sets index 0. The string "Main" is the scene name for the first entry.

Practice

1. What does the Build Settings window in Unity control?

easy

A. Which scenes are included in the final game build

B. The resolution of the game window

C. The color scheme of the editor

D. The physics settings of the game

Solution

1. Step 1: Understand the purpose of Build Settings

   The Build Settings window lists scenes to include in the game build and their order.

2. Step 2: Identify what Build Settings controls

   It controls which scenes are packaged into the final game, not editor or physics settings.

3. Final Answer:

   Which scenes are included in the final game build -> Option A

4. Quick Check:

   Build Settings = Scenes included [OK]

Hint: Build Settings = scenes included in game build [OK]

Common Mistakes:

• Confusing Build Settings with editor appearance
• Thinking it controls physics or resolution
• Assuming it sets scene start order only

2. Which of the following is the correct way to add a scene to the build in Unity?

easy

A. Drag the scene file into the Build Settings window's Scenes In Build list

B. Right-click the scene in Project and select 'Add to Build'

C. Open the scene and press Ctrl+B

D. Rename the scene file to include 'build' in its name

Solution

1. Step 1: Recall how to add scenes to build

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

2. Step 2: Evaluate the options

   Only dragging the scene file into Build Settings is correct; other options are invalid or do nothing.

3. Final Answer:

   Drag the scene file into the Build Settings window's Scenes In Build list -> Option A

4. Quick Check:

   Add scene = drag to Build Settings [OK]

Hint: Add scenes by dragging into Build Settings list [OK]

Common Mistakes:

• Trying to add scenes by renaming files
• Using keyboard shortcuts that don't add scenes
• Expecting context menu to add scenes automatically

3. Given the following scenes in Build Settings in order: ["Menu", "Level1", "Level2"], what will SceneManager.LoadScene(1) load?

medium

A. The scene named "Menu"

B. The scene named "Level1"

C. The scene named "Level2"

D. An error because index 1 is invalid

Solution

1. Step 1: Understand scene indexing in Build Settings

   Scenes are indexed starting at 0 in the order listed in Build Settings.

2. Step 2: Identify scene at index 1

   Index 0 = "Menu", index 1 = "Level1", index 2 = "Level2".

3. Final Answer:

   The scene named "Level1" -> Option B

4. Quick Check:

   Index 1 = second scene = Level1 [OK]

Hint: Scene index starts at 0 in Build Settings [OK]

Common Mistakes:

• Assuming index 1 is the first scene
• Confusing scene names with indexes
• Thinking index 1 causes an error

4. You try to load a scene by index using SceneManager.LoadScene(3), but get an error. What is the most likely cause?

medium

A. SceneManager.LoadScene only accepts strings

B. You must use scene names, not indexes

C. The scene file is missing from the Project folder

D. The scene at index 3 is not added to Build Settings

Solution

1. Step 1: Understand scene indexing and Build Settings

   Scene indexes correspond to the order in Build Settings; index 3 means the fourth scene.

2. Step 2: Identify cause of error

   If index 3 is out of range, it means fewer than 4 scenes are added to Build Settings.

3. Final Answer:

   The scene at index 3 is not added to Build Settings -> Option D

4. Quick Check:

   Index out of range = scene missing in Build Settings [OK]

Hint: Check Build Settings scene count before loading by index [OK]

Common Mistakes:

• Thinking indexes are unrelated to Build Settings
• Believing LoadScene only accepts names
• Assuming missing file causes this specific error

5. You want your game to start with the "Intro" scene, but currently the "MainMenu" scene is first in Build Settings. How can you fix this without renaming scenes?

hard

A. Call SceneManager.LoadScene("Intro") in the first scene's script

B. Change the scene file name to "00_Intro"

C. Drag the "Intro" scene to the top of the Scenes In Build list

D. Remove "MainMenu" from Build Settings

Solution

1. Step 1: Understand scene start order in Build Settings

   The first scene in the Scenes In Build list is the one that starts when the game runs.

2. Step 2: Adjust scene order without renaming

   Drag the "Intro" scene to the top of the list to make it the first scene loaded.

3. Final Answer:

   Drag the "Intro" scene to the top of the Scenes In Build list -> Option C

4. Quick Check:

   First scene in Build Settings = start scene [OK]

Hint: First scene in Build Settings list starts game [OK]

Common Mistakes:

• Renaming files instead of reordering scenes
• Removing scenes unnecessarily
• Relying only on script calls without build order