Component communication in Unity - Mini Project: Build & Apply

Component communication

📖 Scenario: You are creating a simple Unity game where two components need to communicate. One component will keep track of the player's score, and another component will display the score on the screen.

🎯 Goal: Build two Unity components: ScoreManager to store and update the score, and ScoreDisplay to show the score in the console. Learn how to make these components communicate by accessing each other's data.

📋 What You'll Learn

Create a ScoreManager component with a public integer variable score initialized to 0

Create a ScoreDisplay component that accesses ScoreManager to read the current score

Update the score in ScoreManager by adding 10 points

Print the updated score from ScoreDisplay using Debug.Log

💡 Why This Matters

🌍 Real World

In many games, different parts of the game need to share information, like player health, score, or inventory. Learning component communication helps you build interactive and connected game systems.

💼 Career

Game developers often write components that must talk to each other. Understanding how to share data between components is a key skill for creating maintainable and scalable game code.

1

Create the ScoreManager component

Create a C# script called ScoreManager with a public integer variable score initialized to 0.

Unity

// Your code here

Hint

Remember to make the score variable public so other components can access it.

2

Create the ScoreDisplay component and reference ScoreManager

Create a C# script called ScoreDisplay. Inside it, create a public variable scoreManager of type ScoreManager to hold a reference to the ScoreManager component.

Unity

using UnityEngine;

public class ScoreManager : MonoBehaviour
{
    public int score = 0;
}

// Your code here

Hint

Declare a public variable of type ScoreManager so you can assign it in the Unity Editor.

3

Update the score in ScoreManager

In the ScoreManager class, add a public method AddPoints that takes an integer parameter points and adds it to score. Then call AddPoints(10) inside Start() to add 10 points when the game starts.

Unity

using UnityEngine;

public class ScoreManager : MonoBehaviour
{
    public int score = 0;

    // Your code here
}

public class ScoreDisplay : MonoBehaviour
{
    public ScoreManager scoreManager;
}

Hint

Use a method to change the score and call it in Start() to simulate adding points at the beginning.

4

Display the updated score in ScoreDisplay

In the ScoreDisplay class, add a Start() method that uses Debug.Log to print the current score from scoreManager.score.

Unity

using UnityEngine;

public class ScoreManager : MonoBehaviour
{
    public int score = 0;

    public void AddPoints(int points)
    {
        score += points;
    }

    void Start()
    {
        AddPoints(10);
    }
}

public class ScoreDisplay : MonoBehaviour
{
    public ScoreManager scoreManager;

    // Your code here
}

Hint

Use Debug.Log inside Start() to print the score from the scoreManager reference.

Practice

1. What is the primary method used in Unity to access another component attached to the same GameObject?

easy

A. GetComponent<Type>()

B. FindObjectOfType<Type>()

C. SendMessage()

D. Instantiate()

Solution

1. Step 1: Understand component access methods

   Unity provides several ways to access components, but GetComponent<Type>() is used to get a component on the same GameObject.

2. Step 2: Identify the correct method for same GameObject

   FindObjectOfType<Type>() searches the whole scene, SendMessage() calls methods by name, and Instantiate() creates new objects, so they are not for direct component access.

3. Final Answer:

   GetComponent<Type>() -> Option A

4. Quick Check:

   GetComponent<Type>() = Access same GameObject component [OK]

Hint: Use GetComponent<Type>() to get components on the same object [OK]

Common Mistakes:

• Confusing GetComponent with FindObjectOfType
• Using Instantiate instead of GetComponent
• Trying to access components without a reference

2. Which of the following is the correct syntax to get a Rigidbody component in a Unity C# script?

easy

A. Rigidbody rb = GetComponent(Rigidbody);

B. Rigidbody rb = GetComponent<Rigidbody>();

C. Rigidbody rb = GetComponent<Rigidbody>

D. Rigidbody rb = GetComponent<Rigidbody>();;

Solution

1. Step 1: Recall correct generic method syntax

   The correct syntax uses angle brackets with the type and parentheses: GetComponent<Type>().

2. Step 2: Identify syntax errors in options

   Rigidbody rb = GetComponent(Rigidbody); misses angle brackets, Rigidbody rb = GetComponent<Rigidbody> misses parentheses, Rigidbody rb = GetComponent<Rigidbody>();; has double semicolon causing a syntax error.

3. Final Answer:

   Rigidbody rb = GetComponent<Rigidbody>(); -> Option B

4. Quick Check:

   Correct generic syntax = Rigidbody rb = GetComponent<Rigidbody>(); [OK]

Hint: Remember GetComponent<Type>() always uses angle brackets and parentheses [OK]

Common Mistakes:

• Omitting angle brackets <>
• Forgetting parentheses () after GetComponent
• Adding unnecessary semicolons inside method calls

3. Given the code below, what will be printed to the console?

public class Player : MonoBehaviour {
    private Rigidbody rb;
    void Start() {
        rb = GetComponent<Rigidbody>();
        if(rb != null) {
            Debug.Log("Rigidbody found");
        } else {
            Debug.Log("No Rigidbody");
        }
    }
}

medium

A. No Rigidbody

B. Nothing is printed

C. NullReferenceException error

D. Rigidbody found

Solution

1. Step 1: Understand GetComponent behavior

   If the GameObject has a Rigidbody component, GetComponent<Rigidbody>() returns it; otherwise, it returns null.

2. Step 2: Analyze the if condition and output

   The code checks if rb is not null and prints "Rigidbody found" if true, else "No Rigidbody".

3. Final Answer:

   Rigidbody found -> Option D

4. Quick Check:

   GetComponent returns component or null; here it finds Rigidbody [OK]

Hint: GetComponent returns null if component missing; check before use [OK]

Common Mistakes:

• Assuming GetComponent throws error if component missing
• Not checking for null before using component
• Confusing Debug.Log output with errors

4. What is wrong with the following code snippet?

public class Enemy : MonoBehaviour {
    void Start() {
        Player player = GetComponent<Player>();
        player.TakeDamage(10);
    }
}

medium

A. Player class cannot be accessed from Enemy class

B. GetComponent<Player>() is not a valid method

C. GetComponent<Player>() may return null causing a runtime error

D. TakeDamage method cannot be called inside Start()

Solution

1. Step 1: Check GetComponent usage and null safety

   GetComponent<Player>() looks for Player on the same GameObject. If Player is not attached, it returns null.

2. Step 2: Identify possible runtime error

   Calling player.TakeDamage(10) without checking if player is null will cause a NullReferenceException at runtime.

3. Final Answer:

   GetComponent<Player>() may return null causing a runtime error -> Option C

4. Quick Check:

   Always check GetComponent result for null before use [OK]

Hint: Always check if GetComponent returns null before calling methods [OK]

Common Mistakes:

• Not checking for null before method call
• Assuming GetComponent always finds the component
• Thinking method calls are restricted in Start()

5. You want a script on a GameObject to call a method on a component attached to a different GameObject in the scene. Which approach is best practice?

hard

A. Use GetComponent<Type>() on the other GameObject's reference

B. Use GetComponent<Type>() on the current GameObject

C. Use FindObjectOfType<Type>() every frame in Update()

D. Create a new instance of the component with new Type()

Solution

1. Step 1: Understand component communication between GameObjects

   To access a component on another GameObject, you first get a reference to that GameObject, then call GetComponent<Type>() on it.

2. Step 2: Evaluate other options for efficiency and correctness

   Using GetComponent<Type>() on current GameObject won't find other GameObject's components. Calling FindObjectOfType<Type>() every frame is inefficient. Creating components with new is invalid in Unity.

3. Final Answer:

   Use GetComponent<Type>() on the other GameObject's reference -> Option A

4. Quick Check:

   GetComponent on target GameObject = Best practice [OK]

Hint: GetComponent on referenced GameObject, not current one [OK]

Common Mistakes:

• Calling GetComponent on wrong GameObject
• Using FindObjectOfType too often causing lag
• Trying to instantiate components with new keyword