Trigger vs collision detection in Unity

Introduction

Triggers and collisions help your game know when objects touch or overlap. They let your game react to these events, like opening a door or stopping a character.

When you want to detect if a player enters an area without blocking their movement.

When you want to know if two objects hit each other and should bounce or stop.

When you want to collect items by touching them without physical impact.

When you want to trigger animations or sounds when objects collide.

When you want to prevent objects from passing through walls by detecting collisions.

Syntax

Unity

public class Example : MonoBehaviour {
    void OnTriggerEnter(Collider other) {
        // Code runs when another object enters this trigger
    }

    void OnCollisionEnter(Collision collision) {
        // Code runs when this object collides with another
    }
}

OnTriggerEnter requires the collider to be set as a Is Trigger in Unity.

OnCollisionEnter requires both objects to have colliders and at least one to have a Rigidbody.

Examples

This runs when an object enters a trigger zone. The player can pass through without stopping.

Unity

void OnTriggerEnter(Collider other) {
    Debug.Log("Player entered the trigger area.");
}

This runs when the player physically hits a wall or object and cannot pass through.

Unity

void OnCollisionEnter(Collision collision) {
    Debug.Log("Player hit a wall.");
}

Detects when the player touches a collectible item without blocking movement.

Unity

void OnTriggerEnter(Collider other) {
    if (other.CompareTag("Collectible")) {
        Debug.Log("Collected an item!");
    }
}

Detects a physical collision with an enemy object.

Unity

void OnCollisionEnter(Collision collision) {
    if (collision.gameObject.CompareTag("Enemy")) {
        Debug.Log("Player bumped into an enemy!");
    }
}

Sample Program

This script prints messages when the object either triggers or collides with another object. Attach it to a GameObject with a Collider. Set the Collider's Is Trigger on to test triggers, or off to test collisions.

Unity

using UnityEngine;

public class TriggerVsCollisionExample : MonoBehaviour {
    void OnTriggerEnter(Collider other) {
        Debug.Log("Trigger detected with " + other.name);
    }

    void OnCollisionEnter(Collision collision) {
        Debug.Log("Collision detected with " + collision.gameObject.name);
    }
}

Important Notes

Time complexity: Both trigger and collision detection run efficiently within Unity's physics engine.

Common mistake: Forgetting to set Is Trigger for triggers or missing Rigidbody on objects for collisions.

Use triggers when you want to detect overlap without blocking movement. Use collisions when you want physical interaction and blocking.

Summary

Triggers detect when objects overlap without physical blocking.

Collisions detect physical contact and block movement.

Set Is Trigger for triggers; use Rigidbody and colliders for collisions.

Practice

1. What is the main difference between a trigger and a collision in Unity?

easy

A. Triggers detect overlaps without blocking movement, collisions detect physical contact and block movement.

B. Triggers block movement, collisions only detect overlaps.

C. Triggers require Rigidbody, collisions do not.

D. Triggers and collisions behave exactly the same.

Solution

1. Step 1: Understand trigger behavior

   Triggers detect when objects overlap but do not physically block each other.

2. Step 2: Understand collision behavior

   Collisions detect physical contact and prevent objects from passing through each other.

3. Final Answer:

   Triggers detect overlaps without blocking movement, collisions detect physical contact and block movement. -> Option A

4. Quick Check:

   Trigger = overlap, Collision = block [OK]

Hint: Triggers overlap only; collisions block movement [OK]

Common Mistakes:

• Confusing triggers with collisions as both blocking movement
• Thinking triggers require Rigidbody always
• Assuming collisions do not block movement

2. Which of the following is the correct way to make a collider act as a trigger in Unity?

easy

A. Add a Rigidbody component only.

B. Disable the collider component.

C. Set the collider's Is Trigger property to true.

D. Set the collider's material to None.

Solution

1. Step 1: Identify trigger setup

   In Unity, to make a collider a trigger, you must enable its Is Trigger checkbox.

2. Step 2: Verify other options

   Adding Rigidbody or disabling collider does not make it a trigger; setting material to None affects physics but not trigger behavior.

3. Final Answer:

   Set the collider's Is Trigger property to true. -> Option C

4. Quick Check:

   Is Trigger = true for triggers [OK]

Hint: Enable Is Trigger checkbox on collider [OK]

Common Mistakes:

• Adding Rigidbody alone to make trigger
• Disabling collider thinking it triggers events
• Changing material instead of Is Trigger

3. Consider this Unity C# code snippet:

void OnTriggerEnter(Collider other) {
    Debug.Log("Triggered by " + other.name);
}

void OnCollisionEnter(Collision collision) {
    Debug.Log("Collided with " + collision.gameObject.name);
}

What will be printed if an object with a collider marked as trigger overlaps another object with a collider and Rigidbody?

medium

A. No message will print.

B. Only "Collided with [object name]" will print.

C. Both messages will print.

D. Only "Triggered by [object name]" will print.

Solution

1. Step 1: Analyze trigger event

   When a collider marked as trigger overlaps another collider with Rigidbody, OnTriggerEnter is called.

2. Step 2: Analyze collision event

   OnCollisionEnter is called only when colliders physically collide (not triggers).

3. Final Answer:

   Only "Triggered by [object name]" will print. -> Option D

4. Quick Check:

   Trigger collider calls OnTriggerEnter only [OK]

Hint: Trigger collider calls OnTriggerEnter, not OnCollisionEnter [OK]

Common Mistakes:

• Expecting both trigger and collision messages
• Thinking OnCollisionEnter triggers on overlap
• Confusing collider types for events

4. You wrote this code but OnTriggerEnter is never called:

void OnTriggerEnter(Collider other) {
    Debug.Log("Triggered");
}

What is the most likely reason?

medium

A. The collider is disabled.

B. The collider's Is Trigger property is not enabled.

C. The method name is misspelled.

D. The object has no Rigidbody component.

Solution

1. Step 1: Check trigger setup

   OnTriggerEnter only fires if the collider has Is Trigger enabled.

2. Step 2: Verify other conditions

   Rigidbody is needed on one object but missing Rigidbody alone won't prevent OnTriggerEnter if Is Trigger is off; method name is correct; collider disabled would prevent all events.

3. Final Answer:

   The collider's Is Trigger property is not enabled. -> Option B

4. Quick Check:

   Is Trigger must be true for OnTriggerEnter [OK]

Hint: Enable Is Trigger to get OnTriggerEnter calls [OK]

Common Mistakes:

• Forgetting to enable Is Trigger
• Assuming Rigidbody absence blocks trigger
• Misspelling method name
• Not enabling collider component

5. You want to detect when a player enters a zone without blocking their movement, but also detect when the player physically hits a wall. How should you set up the colliders and Rigidbody components?

hard

A. Set the zone collider as trigger (Is Trigger = true), the wall collider as non-trigger, and add Rigidbody to the player.

B. Set both zone and wall colliders as triggers, add Rigidbody to the player.

C. Set the zone collider as non-trigger, wall collider as trigger, and add Rigidbody to the player.

D. Remove Rigidbody from player and set all colliders as non-trigger.

Solution

1. Step 1: Configure zone for overlap detection

   Set the zone collider's Is Trigger to true so it detects player entering without blocking movement.

2. Step 2: Configure wall for physical collision

   Set the wall collider as non-trigger to physically block the player.

3. Step 3: Rigidbody requirement

   Add Rigidbody to the player so physics and trigger events work properly.

4. Final Answer:

   Set the zone collider as trigger (Is Trigger = true), the wall collider as non-trigger, and add Rigidbody to the player. -> Option A

5. Quick Check:

   Trigger zone + Rigidbody player + solid wall = correct setup [OK]

Hint: Trigger zone collider, solid wall collider, Rigidbody on player [OK]

Common Mistakes:

• Making wall a trigger so player passes through
• Not adding Rigidbody to player
• Setting zone collider as non-trigger blocking player