Component communication in Unity - Practice Problems & Coding Challenges

Challenge - 5 Problems

❓ Predict Output

intermediate

What is the output of this Unity C# script?

Consider the following Unity C# script attached to a GameObject. What will be printed in the console when the game starts?

Unity

using UnityEngine;

public class Communicator : MonoBehaviour
{
    void Start()
    {
        var other = GetComponent<OtherComponent>();
        if (other != null)
        {
            Debug.Log(other.GetMessage());
        }
        else
        {
            Debug.Log("No OtherComponent found");
        }
    }
}

public class OtherComponent : MonoBehaviour
{
    public string GetMessage()
    {
        return "Hello from OtherComponent!";
    }
}

A No OtherComponent found

B Compilation error due to missing namespace

C NullReferenceException at runtime

D Hello from OtherComponent!

💡 Hint

Think about whether both components are on the same GameObject.

The GetComponent<OtherComponent>() call looks for the OtherComponent on the same GameObject. Since both scripts are attached, it finds it and calls GetMessage(), printing the returned string.

❓ Predict Output

intermediate

What does this code print when sending a message between components?

Given two components on the same GameObject, what will be printed when SendMessage is called?

Unity

using UnityEngine;

public class Sender : MonoBehaviour
{
    void Start()
    {
        SendMessage("ReceiveMessage", "Hi there!");
    }
}

public class Receiver : MonoBehaviour
{
    void ReceiveMessage(string msg)
    {
        Debug.Log("Received: " + msg);
    }
}

A Received: Hi there!

B No method ReceiveMessage found error

C NullReferenceException at runtime

D Compilation error due to wrong method signature

💡 Hint

SendMessage calls methods by name on the same GameObject's components.

SendMessage calls ReceiveMessage on all components attached to the same GameObject. The method exists and takes a string, so it prints the message.

🔧 Debug

advanced

Why does this code cause a NullReferenceException?

Examine the code below. Why does it throw a NullReferenceException at runtime?

Unity

using UnityEngine;

public class Finder : MonoBehaviour
{
    void Start()
    {
        var other = GameObject.Find("OtherObject").GetComponent<OtherComponent>();
        Debug.Log(other.GetData());
    }
}

public class OtherComponent : MonoBehaviour
{
    public string GetData() => "Data";
}

A GetComponent<OtherComponent>() returns null because OtherComponent is missing

B GameObject.Find("OtherObject") returns null because no GameObject named "OtherObject" exists

C GetData() method is private and inaccessible

D Compilation error due to missing semicolon

💡 Hint

Check if the GameObject with the given name exists in the scene.

If GameObject.Find("OtherObject") returns null, calling GetComponent on null causes a NullReferenceException. This happens if no GameObject named "OtherObject" is present.

📝 Syntax

advanced

Which option correctly gets a component from a child GameObject?

Choose the correct code to get a component of type ChildComponent from a child GameObject.

A var childComp = GetComponentInChildren<ChildComponent>();

B var childComp = GetComponent<ChildComponent>();

C var childComp = transform.Find("Child").GetComponent<ChildComponent>();

D var childComp = GameObject.Find("Child").GetComponentInChildren<ChildComponent>();

💡 Hint

Use transform.Find to locate a child by name, then get its component.

transform.Find("Child") finds the child Transform named "Child". Then GetComponent<ChildComponent>() gets the component from that child GameObject. Other options either get components from the current GameObject or search incorrectly.

🚀 Application

expert

How to safely communicate between components on different GameObjects?

You want to send a message from one component to another component on a different GameObject in the scene. Which approach is best to avoid runtime errors and ensure the message is received?

A Use <code>GameObject.Find</code> to get the other GameObject, then <code>GetComponent</code> to get the component, checking for null before calling methods.

B Use <code>SendMessage</code> with the target GameObject name as a string, assuming the method exists.

C Use <code>GetComponentInChildren</code> on the current GameObject to find the other component.

D Directly create a new instance of the other component class and call its methods.

💡 Hint

Think about how to find a GameObject safely and check for component presence.

Using GameObject.Find to locate the other GameObject, then GetComponent to get the component, and checking for null before calling methods is the safest way. It avoids null reference errors and ensures the component exists.