Why coroutines handle time-based logic in Unity - Test Your Understanding

Practice - 5 Tasks

1fill in blank

easy

Complete the code to start a coroutine that waits for 2 seconds.

Unity

StartCoroutine([1]());

IEnumerator WaitAndPrint() {
    yield return new WaitForSeconds(2);
    Debug.Log("Waited 2 seconds");
}

Drag options to blanks, or click blank then click option'

AStart

BWaitForSeconds

CWaitAndPrint

DPrintAfterWait

Attempts:

3 left

💡 Hint

Common Mistakes

Passing the wrong method name that does not return IEnumerator.

Forgetting to use StartCoroutine to run the coroutine.

The coroutine method name WaitAndPrint is passed to StartCoroutine to begin the timed wait.

2fill in blank

medium

Complete the code to pause execution inside a coroutine for 3 seconds.

Unity

IEnumerator PauseCoroutine() {
    yield return new [1](3);
    Debug.Log("Paused for 3 seconds");
}

Drag options to blanks, or click blank then click option'

AWaitUntil

BWaitForEndOfFrame

CWaitForFixedUpdate

DWaitForSeconds

Attempts:

3 left

💡 Hint

Common Mistakes

Using WaitForEndOfFrame which waits only until the frame ends.

Using WaitUntil without a condition.

new WaitForSeconds(3) pauses the coroutine for 3 seconds before continuing.

3fill in blank

hard

Fix the error in the coroutine that should wait 1 second before printing.

Unity

IEnumerator PrintAfterDelay() {
    yield return new [1](1);
    Debug.Log("Printed after 1 second");
}

Drag options to blanks, or click blank then click option'

AWaitSeconds

BWaitForSeconds

CWaitSecond

DWaitForSecond

Attempts:

3 left

💡 Hint

Common Mistakes

Misspelling the class name causes compile errors.

Using a non-existent class like WaitSeconds.

The correct Unity class to wait is WaitForSeconds. The others are invalid.

4fill in blank

hard

Fill both blanks to create a coroutine that waits 5 seconds and then prints a message.

Unity

IEnumerator DelayedMessage() {
    yield return new [1](5);
    Debug.Log([2]);
}

Drag options to blanks, or click blank then click option'

AWaitForSeconds

B"Hello after delay"

C"Message sent"

DWaitForEndOfFrame

Attempts:

3 left

💡 Hint

Common Mistakes

Using WaitForEndOfFrame instead of WaitForSeconds for time delay.

Forgetting to put quotes around the message string.

The coroutine waits 5 seconds using WaitForSeconds and then prints the message Hello after delay.

5fill in blank

hard

Fill all three blanks to create a coroutine that waits 2 seconds, then waits until a condition is true, and finally prints a message.

Unity

IEnumerator WaitForCondition() {
    yield return new [1](2);
    yield return new [2](() => [3]);
    Debug.Log("Condition met!");
}

Drag options to blanks, or click blank then click option'

AWaitForSeconds

BWaitForEndOfFrame

CisReady

DWaitUntil

Attempts:

3 left

💡 Hint

Common Mistakes

Using WaitForEndOfFrame instead of WaitUntil for condition wait.

Passing a variable name without a lambda function to WaitUntil.

The coroutine first waits 2 seconds with WaitForSeconds, then waits until the boolean isReady is true using WaitUntil.

Practice

1. Why are coroutines useful for handling time-based logic in Unity?

easy

A. Because they run code faster than normal functions

B. Because they allow pausing code execution without freezing the game

C. Because they automatically optimize memory usage

D. Because they replace the Update method completely

Solution

1. Step 1: Understand coroutine behavior

   Coroutines can pause execution at certain points and resume later without stopping the whole game.

2. Step 2: Compare with other methods

   Normal functions run all at once, freezing the game if delayed. Coroutines avoid this by yielding control.

3. Final Answer:

   Because they allow pausing code execution without freezing the game -> Option B

4. Quick Check:

   Pause without freeze = A [OK]

Hint: Coroutines pause without freezing game flow [OK]

Common Mistakes:

• Thinking coroutines run code faster
• Believing coroutines replace Update method
• Assuming coroutines optimize memory automatically

2. Which of the following is the correct way to start a coroutine in Unity?

easy

A. StartCoroutine(MyCoroutine());

B. RunCoroutine(MyCoroutine);

C. BeginCoroutine(MyCoroutine());

D. InvokeCoroutine(MyCoroutine);

Solution

1. Step 1: Recall Unity coroutine syntax

   Unity uses StartCoroutine with parentheses to start a coroutine method.

2. Step 2: Check each option

   Only StartCoroutine(MyCoroutine()); matches Unity's API exactly.

3. Final Answer:

   StartCoroutine(MyCoroutine()); -> Option A

4. Quick Check:

   StartCoroutine with parentheses = A [OK]

Hint: Use StartCoroutine with parentheses to run coroutine [OK]

Common Mistakes:

• Using wrong method names like RunCoroutine
• Omitting parentheses when calling coroutine
• Confusing Invoke with coroutine start

3. What will be the output of this coroutine code snippet?

IEnumerator PrintNumbers()
{
    for (int i = 1; i <= 3; i++)
    {
        Debug.Log(i);
        yield return new WaitForSeconds(1);
    }
}

StartCoroutine(PrintNumbers());

medium

A. Prints 1, then waits 1 second, prints 2, waits 1 second, then prints 3

B. Prints 3 three times with 1 second delay

C. Prints 1, 2, 3 immediately without delay

D. Does not print anything because coroutine is not started

Solution

1. Step 1: Analyze the loop and yield

   The loop prints i, then waits 1 second before continuing to next iteration.

2. Step 2: Understand coroutine timing

   Each Debug.Log happens with a 1 second pause between prints, so output is 1, wait, 2, wait, 3.

3. Final Answer:

   Prints 1, then waits 1 second, prints 2, waits 1 second, then prints 3 -> Option A

4. Quick Check:

   Yield WaitForSeconds causes delay between prints = C [OK]

Hint: Yield pauses loop iteration, causing timed output [OK]

Common Mistakes:

• Assuming all prints happen instantly
• Thinking it prints 3 repeatedly
• Forgetting to start the coroutine

4. Identify the error in this coroutine code:

IEnumerator WaitAndPrint()
{
    Debug.Log("Start");
    WaitForSeconds(2);
    Debug.Log("End");
}

StartCoroutine(WaitAndPrint());

medium

A. Coroutine method should return void

B. Debug.Log cannot be used inside coroutines

C. StartCoroutine cannot be used with IEnumerator

D. Missing yield before WaitForSeconds

Solution

1. Step 1: Check coroutine yield usage

   WaitForSeconds must be preceded by yield to pause execution properly.

2. Step 2: Verify method signature and usage

   Coroutine returns IEnumerator and StartCoroutine accepts it, Debug.Log works inside coroutines.

3. Final Answer:

   Missing yield before WaitForSeconds -> Option D

4. Quick Check:

   Always yield WaitForSeconds in coroutine = B [OK]

Hint: Always use 'yield' before WaitForSeconds in coroutines [OK]

Common Mistakes:

• Omitting yield keyword
• Changing return type to void
• Thinking Debug.Log is disallowed in coroutines

5. You want to create a blinking light effect that turns on and off every 0.5 seconds using a coroutine. Which approach correctly handles the timing without freezing the game?

IEnumerator BlinkLight()
{
    while(true)
    {
        light.enabled = !light.enabled;
        // What goes here?
    }
}

hard

A. InvokeRepeating("BlinkLight", 0, 0.5f);

B. Thread.Sleep(500);

C. yield return new WaitForSeconds(0.5f);

D. yield return null;

Solution

1. Step 1: Understand coroutine timing for blinking

   To wait 0.5 seconds between toggles without freezing, yield return WaitForSeconds(0.5f) is needed.

2. Step 2: Evaluate other options

   Thread.Sleep blocks the main thread (freezes game), yield return null waits only one frame, InvokeRepeating is a different method, not inside coroutine.

3. Final Answer:

   yield return new WaitForSeconds(0.5f); -> Option C

4. Quick Check:

   Use yield WaitForSeconds for timed pause in coroutine = D [OK]

Hint: Use yield WaitForSeconds for smooth timed waits [OK]

Common Mistakes:

• Using Thread.Sleep which freezes game
• Using yield return null which waits only one frame
• Confusing InvokeRepeating with coroutine yield