Executing Logic via OnTriggerEnter and OnTriggerExit

In this lesson, you will learn how to trigger game logic automatically when an object enters or leaves a designated physical space using Unity’s event callback system.

Understanding Trigger Callbacks

When you mark a Collider as a "Trigger" in the Inspector, it stops acting as a solid wall and instead becomes a detection zone. Unity provides two specific methods that automatically execute when this boundary is crossed: OnTriggerEnter and OnTriggerExit. These methods act as "hooks" that the physics engine calls whenever an interaction occurs, allowing your code to react instantly without needing to manually poll for the player's position in an Update loop.

Implementing the Logic

To use these, your script must be attached to a GameObject that contains a Collider (with "Is Trigger" checked) and, usually, a Rigidbody component. Here is how you structure the implementation:

using UnityEngine;

public class ZoneTrigger : MonoBehaviour
{
    private void OnTriggerEnter(Collider other)
    {
        // Executes the moment an object enters the zone
        Debug.Log(other.name + " has entered the area!");
    }

    private void OnTriggerExit(Collider other)
    {
        // Executes the moment an object leaves the zone
        Debug.Log(other.name + " has exited the area.");
    }
}

The other parameter represents the Collider component of the object that touched your trigger zone. You can use this to identify what entered the area—for instance, by checking other.CompareTag("Player") to ensure your logic only triggers for the character and not for stray debris or environment items.

Because these methods are handled directly by the physics engine, they are highly efficient. They essentially "listen" for the physics contact and fire your custom code only when the event happens, keeping your Update methods clean and focused on frame-by-frame movement or input handling. This approach is ideal for creating invisible zones like proximity-based lighting, enemy detection, or automated door systems.

Key Takeaway: Use OnTriggerEnter and OnTriggerExit to create event-driven interactions that respond automatically to spatial collisions, ensuring your code executes only when necessary.