UnityLesson 3418/09/2026Asceno

OnCollisionEnter and OnTriggerEnter in Unity

OnCollisionEnter and OnTriggerEnter report when two collision shapes begin interacting. They differ in callback data, Is Trigger requirements, and gameplay purpose. The examples log object name, tag, and contact point for a Collision, then log an object entering a Trigger. Context-rich logs make physics debugging faster.

ASCENO / UNITY STUDY NOTES · 37

OnCollisionEnter and OnTriggerEnter in Unity

OnCollisionEnter và OnTriggerEnter trong Unity

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 ontriggerenter 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.

OnCollisionEnter and OnTriggerEnter in Unity — native Unity practice — Figure 1/10 — Direct Unity screenshot: the starting point for the hands-on practice.

2. System illustration

OnCollisionEnter and OnTriggerEnter report when two collision shapes begin interacting. They differ in callback data, Is Trigger requirements, and gameplay purpose. The illustration below contains no language-specific text; read it together with this explanation and the concrete steps.

ontriggerenter 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

OnCollisionEnter and OnTriggerEnter in Unity — language-neutral system illustration — Figure 2/10 — Language-neutral system illustration; the explanation is carried by the text around it.

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.

Define the question
Build a small test Scene
Change one value or reference
Press Play / run the action
Read the correct panel
Compare with the prediction

OnCollisionEnter and OnTriggerEnter in Unity — language-neutral cause and result illustration — Figure 3/10 — Language-neutral cause → result illustration using symbols and arrows.

4. Sequence illustration

Open Unity, select Player/Ground, inspect the matching Rigidbody–Collider pair, then enter Play Mode to observe a collision or trigger.

OnCollisionEnter and OnTriggerEnter in Unity — language-neutral sequence illustration — Figure 4/10 — Language-neutral sequence illustration; window names and actions are explained in text.

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.

OnCollisionEnter and OnTriggerEnter in Unity — language-neutral object structure illustration — Figure 5/10 — Language-neutral illustration of parent/child structure and object selection.

6. Configuration illustration

Select the object representing ontriggerenter unity in the Hierarchy. Read Transform first, then find the relevant Component/field. Record the current value before changing it; Use Collision when you need ContactPoint and surface information

OnCollisionEnter and OnTriggerEnter in Unity — language-neutral configuration illustration — Figure 6/10 — Language-neutral configuration and reference illustration; exact locations are named in the text.

7. Result observation illustration

The Console is not decoration: use it to verify Check the method name, 2D/3D suffix, and layers before assuming a callback is not firing. If no log appears, check the active object, script compilation, and Console filters before adding more code.

OnCollisionEnter and OnTriggerEnter in Unity — language-neutral observation illustration — Figure 7/10 — Language-neutral illustration of input, log, state, and result.

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 UnityEngine;

public class ContactLogger : MonoBehaviour
{
    private void OnCollisionEnter(Collision collision)
    {
        Debug.Log($"Collision with {collision.gameObject.name}; contacts: {collision.contactCount}");
    }

    private void OnTriggerEnter(Collider other)
    {
        Debug.Log($"Trigger entered by {other.name}");
    }
}

OnCollisionEnter and OnTriggerEnter in Unity — language-neutral state illustration — Figure 8/10 — Language-neutral illustration of code, state, and output; real code is explained in text.

9. Experiment illustration

The examples log object name, tag, and contact point for a Collision, then log an object entering a Trigger. Context-rich logs make physics debugging faster.

Use Collision when you need ContactPoint and surface information.
Use Trigger to detect entering or leaving a region without a physical response.
Check the method name, 2D/3D suffix, and layers before assuming a callback is not firing.
Run again after reverting to check that the result is reproducible.
Record the input value, action, result, and reason for the change.

OnCollisionEnter and OnTriggerEnter in Unity — language-neutral experiment illustration — Figure 9/10 — Language-neutral experiment illustration: one change, one prediction, one piece of evidence.

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 ontriggerenter unity.

OnCollisionEnter and OnTriggerEnter in Unity — language-neutral correction illustration — Figure 10/10 — Language-neutral wrong path → check → correction illustration; the text names each failure.

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.