What Is a Coroutine in Unity? How Does WaitForSeconds Work?

ASCENO / UNITY STUDY NOTES · 55

What Is a Coroutine in Unity? How Does WaitForSeconds Work?

Coroutine trong Unity là gì? WaitForSeconds hoạt động thế nào?

The lesson starts with a direct Unity screenshot so the practical action is visible. The nine following figures are language-neutral illustrations; the bilingual text below them carries the explanation. The main topic is coroutine unity. Figure 1 is practical evidence; figures 2–10 use only shapes, symbols, and visual relationships so they can remain unchanged across languages.

Learning goals

• Explain the concept with a model or data flow.
• Know exactly which Unity window to open.
• Predict the result before pressing Play and find evidence.
• Rebuild a small experiment and debug it methodically.

1. Hands-on practice in Unity

Open the test Scene, select the relevant object, and perform the action described in the lesson. This is a native Unity screenshot that shows where to begin; the steps and meaning are explained in the text below.

2. System illustration

A Coroutine lets a method pause and resume on a later frame without blocking the whole game thread. WaitForSeconds is useful for cooldowns, sequences, UI messages, and timed effects. The illustration below contains no language-specific text; read it together with this explanation and the concrete steps.

• coroutine unity | the lesson concept | read the focus and hands-on example | do not infer it from object colours
• Input/setting | the input data or configuration | record the value before changing it | do not change several things at once
• Result/evidence | what must be observed in the Scene, Game, Inspector, or Console | capture the correct panel | a polished image is not evidence

3. Cause → result illustration

Read the arrow direction, relative position, and symbol changes as a causal relationship. The explanation below names each step in text rather than relying on words inside the image.

1. StartCoroutine
2. Yield
3. Wait
4. Resume
5. Stop
6. Result

4. Sequence illustration

Open Unity, select the correct GameObject in the Hierarchy, inspect the script Component, then open the Console to see whether the method actually runs.

5. Object structure illustration

Read the object name in the Hierarchy first. If the name does not communicate its role, rename it in the test Scene; a screenshot is useful only when the reader knows what is selected.

6. Configuration illustration

Select the object representing coroutine unity in the Hierarchy. Read Transform first, then find the relevant Component/field. Record the current value before changing it; Start with StartCoroutine and stop it when the object no longer needs it

7. Result observation illustration

The Console is not decoration: use it to verify Choose scaled or realtime waiting based on whether pause should affect the sequence. If no log appears, check the active object, script compilation, and Console filters before adding more code.

8. Code → state illustration

Do not copy code away from the Scene. Before each line, identify the input object/reference; after each line, identify the state or output that should change.

using System.Collections;
using UnityEngine;

public class Cooldown : MonoBehaviour
{
    private bool ready = true;

    public void TryUse()
    {
        if (!ready) return;
        ready = false;
        StartCoroutine(ResetAfter(1.5f));
    }

    private IEnumerator ResetAfter(float seconds)
    {
        yield return new WaitForSeconds(seconds);
        ready = true;
    }
}

9. Experiment illustration

The examples implement a cooldown and a door sequence, then compare yield return null, WaitForSeconds, and WaitForSecondsRealtime during pause.

1. Start with StartCoroutine and stop it when the object no longer needs it.
2. A coroutine is not a new thread; heavy work can still cause stutter.
3. Choose scaled or realtime waiting based on whether pause should affect the sequence.
4. Run again after reverting to check that the result is reproducible.
5. Record the input value, action, result, and reason for the change.

10. Failure → fix illustration

• Selecting the wrong object or asset means a correct edit appears to do nothing.
• Changing several fields at once hides the cause.
• Looking only at the Scene while ignoring the Inspector/Console.
• Skipping verification specific to coroutine unity.

The ASCENO perspective: A good figure must help the reader answer one concrete question. If it does not show what to select, where to look, what to change, or where the result appears, it is not ready for documentation.