Working with Unity and C#

# CHAPTER 18

Working with Unity and C# #

1. Introduction #

2. Learning Objectives #

• Understand the MonoBehaviour base class and its requirement in Unity.

• Memorize the execution order of Unity's event functions (Awake, Start, Update).

• Use [SerializeField] to expose private C# variables to the visual Editor.

• Communicate between multiple C# scripts attached to GameObjects.

• Utilize the UnityEngine namespace for math and debugging.

3. The MonoBehaviour Class #

using UnityEngine; // This imports the Unity API

// By inheriting from MonoBehaviour, this script becomes a "Component"
public class PlayerController : MonoBehaviour
{
    // Script logic goes here
}

4. The Lifecycle (Execution Order) #

1. 1. Awake(): Runs instantly the moment the object is created. Use this to grab components (GetComponent).

1. 2. Start(): Runs right before the first frame update. Use this to initialize variables or find other objects in the scene.

1. 3. Update(): Runs once per frame (Graphics and Input).

1. 4. FixedUpdate(): Runs on a fixed timer (Physics).

1. 5. OnDestroy(): Runs the moment the object is deleted.

5. Exposing Variables to the Inspector #

• The Bad Way: Making the variable public. This exposes it to the Inspector, but it also ruins Encapsulation (any other script can change it).

• The Professional Way: Keep the variable private, but add the [SerializeField] attribute above it.

public class Enemy : MonoBehaviour
{
    // Appears in the Unity Editor for designers to tweak,
    // but remains completely hidden from other C# scripts!
    [SerializeField] private float speed = 5.0f; 
    [SerializeField] private GameObject lootPrefab;
}

6. Communicating Between Scripts (GetComponent) #

public class Player : MonoBehaviour
{
    private Health myHealthScript;

    void Awake()
    {
        // Search this GameObject for a script named 'Health'
        myHealthScript = GetComponent<Health>();
    }

    void OnCollisionEnter(Collision hit)
    {
        // Call the public method on the other script!
        myHealthScript.TakeDamage(10);
    }
}

7. Visual Learning: The Unity Script Connection #

[ Unity Editor ]
  GameObject: "Hero"
   |- Transform (Position/Rotation)
   |- Rigidbody (Physics)
   |- Player.cs (Your Script)  <-- [SerializeField] speed = 5.0
   |- Health.cs (Your Script)

*When Play is pressed:*
Unity reads Player.cs -> Calls Awake() -> Calls Start() -> Calls Update() 60x a sec

8. Best Practices #

• RequireComponent: If your PlayerMotor.cs script uses GetComponent<Rigidbody>(), the game will crash if you forget to add a Rigidbody in the editor. Add [RequireComponent(typeof(Rigidbody))] at the very top of your script. This forces Unity to automatically add a Rigidbody the moment you attach the script!

9. Common Mistakes #

• Naming Conflicts: Do not name your C# script Camera or Collider. Unity already has internal classes with those exact names. If you do this, the compiler will get confused, throwing hundreds of errors. Name your scripts descriptively: PlayerCamera.cs or DamageCollider.cs.

10. Mini Project: Build a Complete Unity Component #

using UnityEngine;

// Force the engine to add an AudioSource so we don't forget!
[RequireComponent(typeof(AudioSource))]
public class CoinPickup : MonoBehaviour
{
    [Header("Settings")]
    [SerializeField] private int coinValue = 10;
    [SerializeField] private AudioClip pingSound;

    private AudioSource audioSource;

    // 1. Grab references
    void Awake()
    {
        audioSource = GetComponent<AudioSource>();
    }

    // 2. Rotate the coin every frame
    void Update()
    {
        transform.Rotate(0, 90 * Time.deltaTime, 0);
    }

    // 3. Detect player collision
    void OnTriggerEnter(Collider other)
    {
        if (other.CompareTag("Player"))
        {
            // Update score, play sound, and destroy
            GameManager.Instance.AddScore(coinValue);
            audioSource.PlayOneShot(pingSound);
            Destroy(gameObject);
        }
    }
}

11. Practice Exercises #

1. 1. What is the difference between Awake() and Start() in the Unity lifecycle?

1. 2. What C# attribute allows a private variable to be modified inside the Unity visual Inspector?

12. MCQs with Answers #

13. Interview Questions #

• Q: Explain the purpose of the [SerializeField] attribute. Why is using this attribute vastly superior to making all your variables public just so game designers can see them in the Unity Inspector?

• Q: Walk me through the Unity MonoBehaviour execution order for the initialization phase. If you have two scripts interacting, why should you grab component references in Awake() but run setup logic in Start()?

• Q: What is the performance impact of calling GetComponent<T>() inside the Update() loop, and how is it properly mitigated?

14. FAQs #

15. Summary #

16. Next Chapter Recommendation #