Public vs SerializeField in Unity - Interactive Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the code to make the variable visible in the Unity Inspector.

Unity

public class Player : MonoBehaviour {
    [1] int health = 100;
}

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

Aprivate

Bpublic

C[SerializeField]

Dprotected

Attempts:

3 left

💡 Hint

Common Mistakes

Using private without SerializeField hides the variable in the Inspector.

Using protected does not show the variable in the Inspector.

Using public makes the variable visible and editable in the Unity Inspector.

2fill in blank

medium

Complete the code to keep the variable private but still show it in the Unity Inspector.

Unity

public class Enemy : MonoBehaviour {
    [1] int damage = 50;
}

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

A[SerializeField]

Bpublic

Cprivate

Dprotected

Attempts:

3 left

💡 Hint

Common Mistakes

Using private alone hides the variable in the Inspector.

Using public exposes the variable but changes its access level.

The [SerializeField] attribute makes a private variable visible in the Inspector.

3fill in blank

hard

Fix the error in the code to correctly serialize a private variable.

Unity

public class Weapon : MonoBehaviour {
    [1] int ammoCount = 30;
}

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

A[SerializeField]

BSerializeField

Cpublic

Dprivate SerializeField

Attempts:

3 left

💡 Hint

Common Mistakes

Writing SerializeField without brackets causes a syntax error.

Combining private and SerializeField without brackets is invalid.

The [SerializeField] attribute must be placed in square brackets before the variable declaration.

4fill in blank

hard

Fill both blanks to declare a private variable visible in the Inspector and initialize it.

Unity

public class Shield : MonoBehaviour {
    [1] int [2] = 75;
}

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

A[SerializeField]

Bpublic

CshieldStrength

Dprivate

Attempts:

3 left

💡 Hint

Common Mistakes

Using public instead of SerializeField changes access level.

Using generic names like 'value' instead of descriptive names.

Use [SerializeField] to show the private variable shieldStrength in the Inspector.

5fill in blank

hard

Fill all three blanks to declare a private serialized float variable with a default value.

Unity

public class SpeedBoost : MonoBehaviour {
    [1] float [2] = [3];
}

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

A[SerializeField]

BboostSpeed

C5.5f

Dpublic

Attempts:

3 left

💡 Hint

Common Mistakes

Forgetting the 'f' suffix on float values causes errors.

Using public instead of SerializeField changes access level.

The variable boostSpeed is private but visible in the Inspector with [SerializeField] and initialized to 5.5f.

Practice

1. What is the main difference between a public variable and a [SerializeField] private variable in Unity?

easy

A. public variables are accessible by other scripts and visible in the Inspector, while [SerializeField] private variables are only visible in the Inspector but not accessible by other scripts.

B. public variables are hidden in the Inspector, but [SerializeField] private variables are accessible by all scripts.

C. public variables cannot be edited in the Inspector, but [SerializeField] private variables can be edited by other scripts.

D. public variables are only accessible inside the class, while [SerializeField] private variables are accessible everywhere.

Solution

1. Step 1: Understand public variable behavior

   A public variable is accessible by all scripts and also visible in the Unity Inspector for editing.

2. Step 2: Understand [SerializeField] with private

   A [SerializeField] private variable is hidden from other scripts but still visible and editable in the Inspector.

3. Final Answer:

   public variables are accessible by other scripts and visible in the Inspector, while [SerializeField] private variables are only visible in the Inspector but not accessible by other scripts. -> Option A

4. Quick Check:

   Access and visibility differ between public and [SerializeField] private [OK]

Hint: Public = accessible everywhere; SerializeField private = Inspector only [OK]

Common Mistakes:

• Thinking SerializeField makes variable public
• Assuming public variables are hidden in Inspector
• Confusing private and public accessibility

2. Which of the following is the correct way to make a private variable visible in the Unity Inspector?

easy

A. private int score; [SerializeField]

B. [SerializeField] private int score;

C. public [SerializeField] int score;

D. int [SerializeField] private score;

Solution

1. Step 1: Recall correct attribute placement

   The [SerializeField] attribute must be placed before the variable declaration.

2. Step 2: Check variable declaration syntax

   The correct syntax is [SerializeField] private int score; to make a private variable visible in Inspector.

3. Final Answer:

   [SerializeField] private int score; -> Option B

4. Quick Check:

   Attribute before private variable declaration [OK]

Hint: Put [SerializeField] before private variable declaration [OK]

Common Mistakes:

• Placing [SerializeField] after variable
• Mixing public and [SerializeField] incorrectly
• Wrong order of keywords

3. Consider this Unity C# script snippet:

public class Player : MonoBehaviour {
    [SerializeField] private int health = 100;
    public int score = 0;

    void Start() {
        Debug.Log(health);
        Debug.Log(score);
    }
}

What will be printed in the Unity Console when the game starts?

medium

A. Error: health is private and cannot be accessed

B. 0 and 100

C. 100 and 0

D. Nothing will print

Solution

1. Step 1: Understand variable values and accessibility

   The private variable health is serialized and initialized to 100, so it is accessible inside the class and prints 100. The public variable score is initialized to 0 and prints 0.

2. Step 2: Check Debug.Log outputs

   Both Debug.Log(health) and Debug.Log(score) print their current values: 100 and 0 respectively.

3. Final Answer:

   100 and 0 -> Option C

4. Quick Check:

   Private serialized variables accessible inside class [OK]

Hint: Private serialized variables print normally inside class [OK]

Common Mistakes:

• Thinking private variables can't be accessed inside class
• Confusing initialization values
• Assuming serialization affects runtime access

4. You have this code in Unity:

public class Enemy : MonoBehaviour {
    [SerializeField] private int damage = 10;
}

But in the Inspector, the damage value stays at 0 even after you press Play. What is the likely problem?

medium

A. The damage variable is private and cannot be changed at runtime.

B. The [SerializeField] attribute is only for public variables.

C. You forgot to make damage public to change it in code.

D. The Inspector value overrides the code assignment, so damage stays at 0.

Solution

1. Step 1: Understand Inspector and code value interaction

   If a serialized field has a value set in the Inspector, Unity uses that value at runtime, overriding the code default initialization.

2. Step 2: Explain why damage stays 0

   The Inspector value for damage is 0, so even though code initializes it to 10, the Inspector value overrides it.

3. Final Answer:

   The Inspector value overrides the code assignment, so damage stays at 0. -> Option D

4. Quick Check:

   Inspector values override code assignments at runtime [OK]

Hint: Inspector values override code assignments on serialized fields [OK]

Common Mistakes:

• Assuming private variables can't be changed in code
• Thinking [SerializeField] only works on public variables
• Ignoring Inspector value overrides

5. You want to keep a variable speed editable in the Unity Inspector but prevent other scripts from modifying it directly. Which is the best way to declare it?

hard

A. [SerializeField] private float speed;

B. private float speed; // no attribute

C. public float speed;

D. public float speed { get; private set; }

Solution

1. Step 1: Identify requirement for Inspector editing and script protection

   The variable must be editable in Inspector but not accessible publicly by other scripts.

2. Step 2: Evaluate options

   public float speed; makes it public, so other scripts can modify it. private float speed; // no attribute hides it from Inspector. [SerializeField] private float speed; uses [SerializeField] with private, making it editable in Inspector but hidden from other scripts. public float speed { get; private set; } uses a public property with private setter, which is not visible in Inspector by default.

3. Final Answer:

   [SerializeField] private float speed; -> Option A

4. Quick Check:

   SerializeField + private = Inspector editable, script protected [OK]

Hint: Use [SerializeField] private for Inspector edit, no public access [OK]

Common Mistakes:

• Making variable public and exposing it
• Using property without SerializeField
• Forgetting to add [SerializeField]