Prefabs and reusable objects in Unity - Step-by-Step Execution

Concept Flow - Prefabs and reusable objects

Create GameObject

↓

Configure GameObject

↓

Create Prefab from GameObject

↓

Use Prefab in Scene

↓

Modify Prefab

↓

Prefab Updates All Instances

You create a game object, turn it into a prefab, then reuse it many times. Changing the prefab updates all copies.

Execution Sample

Unity

GameObject enemy = new GameObject("Enemy");
// Add components and set properties
PrefabUtility.SaveAsPrefabAsset(enemy, "Assets/Resources/Prefabs/Enemy.prefab");

// Later in scene
GameObject enemyInstance = Instantiate(Resources.Load<GameObject>("Prefabs/Enemy"));

Create an enemy object, save it as a prefab, then create instances from that prefab in the scene.

Execution Table

Step	Action	Object State	Prefab State	Result
1	Create GameObject 'Enemy'	Enemy created, no prefab	No prefab yet	GameObject exists in scene
2	Configure Enemy (add components)	Enemy has components	No prefab yet	GameObject ready for prefab
3	Save as prefab 'Enemy.prefab'	Enemy linked to prefab	Prefab saved with Enemy data	Prefab asset created
4	Instantiate prefab in scene	New Enemy instance created	Prefab unchanged	Instance appears in scene
5	Modify prefab asset	Prefab updated	Prefab asset changed	All instances update automatically
6	Modify instance only	Instance changed	Prefab unchanged	Instance overrides prefab settings
7	Exit	-	-	No more actions

💡 No more actions to perform; prefab and instances are set up.

Variable Tracker

Variable	Start	After Step 1	After Step 3	After Step 4	After Step 5	Final
enemy (GameObject)	null	Created (no prefab)	Linked to prefab	Instance created	Prefab updated	Prefab and instances synced
prefab (Asset)	null	null	Created with enemy data	Unchanged	Updated	Updated prefab asset

Key Moments - 3 Insights

Why does changing the prefab update all instances automatically?

Because all instances are linked to the prefab asset, so when the prefab changes (see step 5 in execution_table), Unity updates all instances to match.

What happens if you change only one instance and not the prefab?

The instance overrides the prefab settings locally (step 6), so that instance looks different but the prefab and other instances stay the same.

Why do we create a prefab instead of just copying GameObjects?

Prefabs let you reuse objects easily and update all copies at once, unlike copies which are independent and need manual updates.

Visual Quiz - 3 Questions

Look at the execution_table, at which step is the prefab asset first created?

A Step 1

B Step 3

C Step 4

D Step 5

💡 Hint

Check the 'Prefab State' column in execution_table rows.

According to variable_tracker, what is the state of 'enemy' after step 4?

A Created but no prefab

B Linked to prefab

C Instance created

D Prefab updated

💡 Hint

Look at the 'enemy (GameObject)' row under 'After Step 4' in variable_tracker.

If you modify only one instance (step 6), what happens to the prefab asset?

A Prefab asset remains unchanged

B Prefab asset is deleted

C Prefab asset updates

D Prefab asset duplicates

💡 Hint

See 'Prefab State' column in execution_table at step 6.

Concept Snapshot

Prefabs are reusable game object templates.
Create a GameObject, configure it, then save as prefab.
Instantiate prefab copies in scenes.
Changing prefab updates all instances.
Instance changes override prefab locally.

Full Transcript

Prefabs in Unity let you create a game object once and reuse it many times. First, you create and set up a GameObject, then save it as a prefab asset. This prefab acts like a template. When you add prefab instances to your scene, they link back to the prefab. If you change the prefab asset, all instances update automatically. But if you change only one instance, it overrides the prefab locally without affecting others. This system helps keep your game organized and easy to update.

Practice

1. What is the main purpose of a prefab in Unity?

easy

A. To save a game object for reuse multiple times

B. To write scripts for game logic

C. To create animations for characters

D. To design user interface layouts

Solution

1. Step 1: Understand prefab concept

   A prefab stores a game object with all its components and settings.

2. Step 2: Identify prefab use

   Prefabs allow easy reuse of objects without recreating them from scratch.

3. Final Answer:

   To save a game object for reuse multiple times -> Option A

4. Quick Check:

   Prefab = reusable object [OK]

Hint: Prefabs store objects to reuse easily in your game [OK]

Common Mistakes:

• Confusing prefabs with scripts
• Thinking prefabs are only for animations
• Believing prefabs are UI elements

2. Which of the following is the correct way to create a copy of a prefab in a Unity script?

easy

A. Clone(prefab);

B. Copy(prefab);

C. Duplicate(prefab);

D. Instantiate(prefab);

Solution

1. Step 1: Recall Unity method for prefab copies

   Unity uses the Instantiate() method to create copies of objects.

2. Step 2: Check method names

   Only Instantiate() is a valid Unity method for this purpose.

3. Final Answer:

   Instantiate(prefab); -> Option D

4. Quick Check:

   Instantiate() creates prefab copies [OK]

Hint: Use Instantiate() to copy prefabs in scripts [OK]

Common Mistakes:

• Using Copy() which does not exist
• Trying Clone() or Duplicate() which are invalid
• Forgetting parentheses after Instantiate

3. What will be the output of this Unity C# code snippet?

public GameObject prefab;
void Start() {
    GameObject obj = Instantiate(prefab);
    Debug.Log(obj.name);
}

medium

A. The name of the prefab with "(Clone)" appended

B. The original prefab name without changes

C. An error because prefab is not assigned

D. Nothing is printed

Solution

1. Step 1: Understand Instantiate behavior

   Instantiate creates a copy of the prefab and appends "(Clone)" to its name.

2. Step 2: Analyze Debug.Log output

   Debug.Log prints the name of the new object, which includes "(Clone)".

3. Final Answer:

   The name of the prefab with "(Clone)" appended -> Option A

4. Quick Check:

   Instantiate adds "(Clone)" to name [OK]

Hint: Instantiate adds "(Clone)" to copied prefab names [OK]

Common Mistakes:

• Expecting original prefab name without "(Clone)"
• Assuming no output is printed
• Forgetting prefab must be assigned in inspector

4. Identify the error in this Unity C# code that tries to instantiate a prefab:

public GameObject prefab;
void Start() {
    GameObject obj = Instantiate(prefab, new Vector3(0, 0, 0));
}

medium

A. Vector3 cannot be used as a position

B. prefab must be assigned in the inspector

C. Instantiate requires a rotation parameter when using position

D. Instantiate cannot be called in Start()

Solution

1. Step 1: Check Instantiate method overloads

   Instantiate with position requires both position and rotation parameters.

2. Step 2: Identify missing rotation argument

   The code misses the rotation argument, causing a compile error.

3. Final Answer:

   Instantiate requires a rotation parameter when using position -> Option C

4. Quick Check:

   Instantiate(position) needs rotation too [OK]

Hint: Instantiate with position needs rotation argument [OK]

Common Mistakes:

• Omitting rotation parameter
• Assuming Vector3 alone is enough
• Thinking Instantiate can't be used in Start()

5. You want to create 5 copies of a prefab at different positions along the X-axis, spaced 2 units apart, in Unity. Which code snippet correctly does this?

hard

A. for (int i = 0; i < 5; i++) {
Instantiate(prefab);
prefab.transform.position = new Vector3(i * 2, 0, 0);
}

B. for (int i = 0; i < 5; i++) {
Instantiate(prefab, new Vector3(i * 2, 0, 0), Quaternion.identity);
}

C. Instantiate(prefab, new Vector3(0, 0, 0), Quaternion.identity);
Instantiate(prefab, new Vector3(1, 0, 0), Quaternion.identity);
Instantiate(prefab, new Vector3(2, 0, 0), Quaternion.identity);
Instantiate(prefab, new Vector3(3, 0, 0), Quaternion.identity);
Instantiate(prefab, new Vector3(4, 0, 0), Quaternion.identity);

D. for (int i = 0; i < 5; i++) {
prefab.transform.position = new Vector3(i * 2, 0, 0);
Instantiate(prefab);
}

Solution

1. Step 1: Understand correct Instantiate usage with position

   Instantiate(prefab, position, rotation) creates a copy at the given position.

2. Step 2: Check loop for multiple copies

   for (int i = 0; i < 5; i++) { Instantiate(prefab, new Vector3(i * 2, 0, 0), Quaternion.identity); } uses a loop to create 5 copies spaced by 2 units on X-axis correctly.

3. Step 3: Identify errors in other options

   The loop that instantiates first then moves prefab results in clones at incorrect positions (0, 0, 2, 4, 6); the manual five Instantiate calls use 1-unit spacing (0,1,2,3,4) instead of 2 units and are repetitive; the loop that moves prefab before instantiating spawns all at (0,0,0) because no position parameter is passed.

4. Final Answer:

   for (int i = 0; i < 5; i++) { Instantiate(prefab, new Vector3(i * 2, 0, 0), Quaternion.identity); } -> Option B

5. Quick Check:

   Loop + Instantiate with position = multiple copies [OK]

Hint: Use loop with Instantiate(prefab, position, rotation) [OK]

Common Mistakes:

• Changing prefab position instead of copy
• Not providing rotation in Instantiate
• Writing repetitive Instantiate calls instead of loop