00_TryGetComponent.md

GetComponent<T>() vs TryGetComponent<T>()

This example showcases a PlayerController detecting collisions with an Enemy and retrieving its component. The bad practice uses GetComponent(), causing unnecessary memory allocations, while the good practice replaces it with TryGetComponent(), optimizing performance and reducing overhead in frequent collision checks. 🚀

BadPlayerController.cs

using UnityEngine;

public class BadPlayerController : MonoBehaviour
{
    private void OnCollisionEnter(Collision collision)
    {
        Enemy enemy = collision.gameObject.GetComponent<Enemy>();
        if (enemy != null)
        {
            TakeDamage(enemy.GetDamage());
        }
    }

    private void TakeDamage(int damage)
    {
        Debug.Log($"Player took {damage} damage!");
    }
}

public class Enemy : MonoBehaviour
{
    public int GetDamage() => 10;
}

GoodPlayerController.cs

using UnityEngine;

public class GoodPlayerController : MonoBehaviour
{
    private void OnCollisionEnter(Collision collision)
    {
        if (collision.gameObject.TryGetComponent<Enemy>(out Enemy enemy))
        {
            TakeDamage(enemy.GetDamage());
        }
    }

    private void TakeDamage(int damage)
    {
        Debug.Log($"Player took {damage} damage!");
    }
}

public class Enemy : MonoBehaviour
{
    public int GetDamage() => 10;
}