MonoBehaviour lifecycle in Unity

Introduction

The MonoBehaviour lifecycle helps you control when your game code runs. It organizes your code to run at the right time during the game.

When you want to run code once at the start of a game or scene.

When you need to update something every frame, like moving a character.

When you want to react to physics updates in your game.

When you want to clean up or save data before the game or scene ends.

When you want to respond to user input or other events during gameplay.

Syntax

Unity

void Awake() { }
void Start() { }
void Update() { }
void FixedUpdate() { }
void LateUpdate() { }
void OnEnable() { }
void OnDisable() { }
void OnDestroy() { }

These are special methods in a MonoBehaviour script that Unity calls automatically.

You do not call these methods yourself; Unity manages when they run.

Examples

Awake runs first when the script instance is loaded.

Unity

void Awake() {
    Debug.Log("Awake called");
}

Start runs once before the first frame update, after Awake.

Unity

void Start() {
    Debug.Log("Start called");
}

Update runs every frame to handle regular updates like input or movement.

Unity

void Update() {
    Debug.Log("Update called every frame");
}

FixedUpdate runs on a fixed timer, good for physics calculations.

Unity

void FixedUpdate() {
    Debug.Log("FixedUpdate called on fixed time steps");
}

Sample Program

This script shows the main MonoBehaviour lifecycle methods. Unity calls them automatically in this order: Awake, Start, then Update every frame, FixedUpdate on fixed intervals, and OnDestroy when the object is removed.

Unity

using UnityEngine;

public class LifecycleExample : MonoBehaviour
{
    void Awake()
    {
        Debug.Log("Awake: Initialize variables");
    }

    void Start()
    {
        Debug.Log("Start: Setup before first frame");
    }

    void Update()
    {
        Debug.Log("Update: Runs every frame");
    }

    void FixedUpdate()
    {
        Debug.Log("FixedUpdate: Runs on fixed time steps");
    }

    void OnDestroy()
    {
        Debug.Log("OnDestroy: Cleanup before object is destroyed");
    }
}

Important Notes

Awake is called even if the script is disabled, but Start only runs if the script is enabled.

Update runs every frame, so keep code here efficient to avoid slowing the game.

FixedUpdate is best for physics-related code because it runs at consistent time steps.

Summary

MonoBehaviour lifecycle methods let you run code at specific times during the game.

Awake and Start run once at the beginning; Update and FixedUpdate run repeatedly.

Use OnDestroy to clean up before the object is removed.

Practice

1. Which MonoBehaviour method is called exactly once when the script instance is being loaded, before any Start methods?

easy

A. FixedUpdate()

B. Update()

C. Awake()

D. OnDestroy()

Solution

1. Step 1: Understand MonoBehaviour initialization order

   Awake() is called once when the script instance is loaded, before Start().

2. Step 2: Differentiate from other lifecycle methods

   Update() and FixedUpdate() run repeatedly, and OnDestroy() runs when the object is destroyed.

3. Final Answer:

   Awake() -> Option C

4. Quick Check:

   Awake runs once at load = Awake() [OK]

Hint: Awake runs once at load, before Start [OK]

Common Mistakes:

• Confusing Awake with Start
• Thinking Update runs once
• Mixing OnDestroy timing

2. Which of the following is the correct syntax to declare the Update method in a MonoBehaviour script?

easy

A. void Update() {}

B. public void Update() {}

C. private Update() {}

D. Update void() {}

Solution

1. Step 1: Recall method declaration rules in C# for Unity

   MonoBehaviour lifecycle methods like Update are usually declared as void Update() without access modifiers.

2. Step 2: Check each option's syntax

   void Update() {} is correct syntax. public void Update() {} is valid C# but Unity recommends no access modifier. private Update() {} is missing return type. Update void() {} has wrong order.

3. Final Answer:

   void Update() {} -> Option A

4. Quick Check:

   Correct method syntax = void Update() {} [OK]

Hint: Update method is always void Update() {} [OK]

Common Mistakes:

• Using wrong order of return type and name
• Omitting void return type
• Adding private keyword incorrectly

3. What will be the output of the following code attached to a GameObject?

using UnityEngine;

public class TestLifecycle : MonoBehaviour {
    void Awake() {
        Debug.Log("Awake called");
    }
    void Start() {
        Debug.Log("Start called");
    }
    void Update() {
        Debug.Log("Update called");
        enabled = false;
    }
}

Assuming the game runs for one frame, what messages appear in the Console?

medium

A. ["Awake called", "Start called", "Update called"]

B. ["Awake called", "Start called"]

C. ["Start called", "Update called"]

D. ["Awake called", "Update called"]

Solution

1. Step 1: Understand method call order on first frame

   On first frame, Awake() runs once at load, then Start() runs before first Update, then Update() runs.

2. Step 2: Analyze Update disabling script

   The Update() method disables the script after logging, so it runs once this frame only.

3. Final Answer:

   ["Awake called", "Start called", "Update called"] -> Option A

4. Quick Check:

   Awake, Start, Update run once first frame [OK]

Hint: Awake and Start run before first Update [OK]

Common Mistakes:

• Thinking Update disables before logging
• Missing Awake call
• Assuming Update runs multiple times first frame

4. Identify the error in this MonoBehaviour script:

using UnityEngine;

public class Example : MonoBehaviour {
    void Start() {
        Debug.Log("Start called");
    }

    void Update() {
        Debug.Log("Update called");
    }

    void OnDestroy() {
        Debug.Log("Destroying object");
    }

    void awake() {
        Debug.Log("Awake called");
    }
}

medium

A. Start method must be static

B. OnDestroy method must return a bool

C. Update method cannot have Debug.Log calls

D. Method awake() should be Awake() with capital A

Solution

1. Step 1: Check method names for correct casing

   Unity lifecycle methods are case-sensitive. awake() is incorrect; it must be Awake().

2. Step 2: Verify other method signatures

   OnDestroy() returns void, Update() can have Debug.Log, and Start() is instance method, not static.

3. Final Answer:

   Method awake() should be Awake() with capital A -> Option D

4. Quick Check:

   Method names are case-sensitive = Awake() [OK]

Hint: Unity method names must match exact case [OK]

Common Mistakes:

• Ignoring case sensitivity
• Thinking OnDestroy returns bool
• Assuming Start must be static

5. You want to ensure a GameObject cleans up resources before it is destroyed. Which MonoBehaviour method should you override, and what is the best practice to use it?

hard

A. Override Start() and release resources there.

B. Override OnDestroy() and release resources or unsubscribe from events there.

C. Override Update() and check if object is destroyed to release resources.

D. Override Awake() and release resources there.

Solution

1. Step 1: Identify the cleanup lifecycle method

   OnDestroy() is called just before the object is destroyed, ideal for cleanup.

2. Step 2: Understand best practice for resource management

   Release resources and unsubscribe from events inside OnDestroy() to avoid memory leaks or errors.

3. Final Answer:

   Override OnDestroy() and release resources or unsubscribe from events there. -> Option B

4. Quick Check:

   Cleanup happens in OnDestroy() [OK]

Hint: Use OnDestroy to clean up before object removal [OK]

Common Mistakes:

• Trying to clean up in Start or Awake
• Checking destruction inside Update
• Not unsubscribing from events