Public vs SerializeField in Unity - Quick Revision & Key Differences

Recall & Review

beginner

What does the public keyword do in Unity scripts?

It makes a variable accessible from other scripts and also visible and editable in the Unity Inspector.

beginner

What is the purpose of the [SerializeField] attribute in Unity?

It makes a private variable visible and editable in the Unity Inspector without making it accessible from other scripts.

intermediate

Why might you use [SerializeField] instead of public for a variable?

To keep the variable private (hidden from other scripts) but still editable in the Inspector, helping to protect your code from unwanted changes.

beginner

Can a private variable without [SerializeField] be edited in the Unity Inspector?

No, private variables without [SerializeField] are hidden from the Inspector and cannot be edited there.

beginner

What happens if you make a variable public but do not use [SerializeField]?

The variable is visible and editable in the Inspector and accessible from other scripts.

Which keyword or attribute allows a private variable to be shown in the Unity Inspector?

A [SerializeField]

B public

C private

D readonly

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

What does making a variable public in Unity do?

A Only makes it visible in the Inspector but not accessible from other scripts

B Keeps it private and hidden in the Inspector

C Makes it accessible from other scripts and visible in the Inspector

D Prevents it from being serialized

Public variables are accessible from other scripts and visible in the Inspector.

Why use [SerializeField] on a private variable?

A To make it readonly

B To make it public

C To hide it from the Inspector

D To edit it in the Inspector but keep it private to other scripts

[SerializeField] lets you edit private variables in the Inspector without exposing them to other scripts.

If a variable is private and has no [SerializeField], can you edit it in the Inspector?

A No

B Yes

C Only if it is static

D Only if it is const

Private variables without [SerializeField] are hidden from the Inspector.

Which is a good reason to keep a variable private but serialized?

A To make it accessible everywhere

B To protect it from unwanted changes by other scripts but allow editing in Inspector

C To prevent it from being saved

D To make it readonly

Keeping variables private but serialized protects code while allowing easy editing in the Inspector.

Explain the difference between using public and [SerializeField] for variables in Unity.

Think about accessibility and Inspector visibility separately.

Why might a Unity developer prefer [SerializeField] over making variables public?

Consider code safety and ease of editing.

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]