Adding and removing components in Unity - Practice Problems & Coding Challenges

Challenge - 5 Problems

❓ Predict Output

intermediate

What is the output of adding a Rigidbody component?

Consider the following Unity C# code snippet. What will be the output in the console after running this code attached to a GameObject?

Unity

using UnityEngine;

public class TestComponent : MonoBehaviour
{
    void Start()
    {
        Rigidbody rb = gameObject.AddComponent<Rigidbody>();
        Debug.Log(rb != null ? "Rigidbody added" : "Failed to add Rigidbody");
    }
}

A Failed to add Rigidbody

B Rigidbody added

C NullReferenceException at Debug.Log

D No output

💡 Hint

Adding a component returns the new component instance if successful.

The AddComponent() method adds a Rigidbody component to the GameObject and returns the instance. Since it is successful, the output is "Rigidbody added".

❓ Predict Output

intermediate

What happens when removing a component?

What will be the output of this Unity C# code snippet when attached to a GameObject that already has a BoxCollider component?

Unity

using UnityEngine;

public class RemoveComponentTest : MonoBehaviour
{
    void Start()
    {
        BoxCollider bc = gameObject.GetComponent<BoxCollider>();
        Destroy(bc);
        Debug.Log(gameObject.GetComponent<BoxCollider>() == null ? "BoxCollider removed" : "BoxCollider still present");
    }
}

A BoxCollider still present

B No output

C NullReferenceException at Destroy

D BoxCollider removed

💡 Hint

Destroy removes the component but only after the current frame ends.

Destroy schedules the component for removal at the end of the frame, so immediately after calling Destroy, the component still exists. Therefore, the output is "BoxCollider still present".

🔧 Debug

advanced

Why does this code throw an error when removing a component?

Examine the code below. It throws a runtime error when trying to remove a component. What is the cause?

Unity

using UnityEngine;

public class RemoveError : MonoBehaviour
{
    void Start()
    {
        Rigidbody rb = gameObject.GetComponent<Rigidbody>();
        Destroy(rb);
        Destroy(rb);
    }
}

A GetComponent<Rigidbody>() returns null causing Destroy(null) error

B Destroy requires a delay parameter

C Destroy cannot be called inside Start method

D Destroying the same component twice causes a NullReferenceException

💡 Hint

Check what happens after the first Destroy call to the component reference.

After the first Destroy call, the component is marked for removal and effectively null. Calling Destroy again on the same reference causes a NullReferenceException.

🧠 Conceptual

advanced

Which statement about AddComponent and Destroy is true?

Select the correct statement about adding and removing components in Unity.

A AddComponent immediately adds the component, but Destroy removes it only after the frame ends

B AddComponent and Destroy both immediately change the GameObject's components list

C Destroy immediately removes the component, but AddComponent delays adding until next frame

D AddComponent and Destroy both delay their operations until the next frame

💡 Hint

Think about when components become available or removed in the frame lifecycle.

AddComponent adds the component instantly so it can be used immediately. Destroy schedules removal at the end of the frame, so the component still exists until then.

❓ Predict Output

expert

What is the output after adding and removing components in sequence?

What will be printed to the console after running this Unity C# script attached to a GameObject with no Rigidbody initially?

Unity

using UnityEngine;

public class AddRemoveSequence : MonoBehaviour
{
    void Start()
    {
        Rigidbody rb = gameObject.AddComponent<Rigidbody>();
        Debug.Log(rb != null ? "Added" : "Not added");
        Destroy(rb);
        Rigidbody rbCheck = gameObject.GetComponent<Rigidbody>();
        Debug.Log(rbCheck != null ? "Still there" : "Removed");
    }
}

A Not added\nRemoved

B Added\nRemoved

C Added\nStill there

D Not added\nStill there

💡 Hint

Remember when Destroy actually removes the component.

AddComponent adds the Rigidbody immediately, so "Added" prints. Destroy schedules removal, so immediately after, the Rigidbody still exists, printing "Still there".