Collision detection script - How to destroy objects of a when a score reaches a certain number

Unity Engine
1

I have a script that I want to use to destroy a select objects with a specific tag when a score reaches the number zero. I know how to actually destroy the objects, but how would I put it so it works when something happens? I’m somewhat new at coding, and would like to learn more.

Here’s the script

public class UICollisionControl : MonoBehaviour
{
   
    public bool destroyEnemy;
    public Text scoreUI;
    public int increaseScore;
    public int decreaseScore;
    public int score;

    void Start()
    {
        audioSource = GetComponent<AudioSource>();
        score = 64;
    }

    void Update(){
        if(scoreUI != null){
            scoreUI.text = score.ToString();
        }
    }

    // only for GameObjects with a mesh, box, or other collider except for character controller and wheel colliders
    void OnCollisionEnter(Collision other)
    {
       

        if(audioSource != null && !audioSource.isPlaying){
            audioSource.PlayOneShot(collisionAudio, 0.5F);
        }

        if(destroyEnemy == true && other.gameObject.tag == "Enemy")
        {
            Destroy(other.gameObject);
        }


        if (scoreUI != null && decreaseScore != 0 && other.gameObject.tag == "Enemy")
        {
            score -= decreaseScore;
        }
    }

    // only for GameObjects with a character controller applied
    void OnControllerColliderHit(ControllerColliderHit hit)
    {
        Rigidbody body = hit.collider.attachedRigidbody;

        // if no rigidbody
        if (body == null || body.isKinematic)
        {
            return;
        }

        // don't push ground or platform GameObjects below player
        if (hit.moveDirection.y < -0.3)
        {
            return;
        }


        if(audioSource != null && !audioSource.isPlaying){
            audioSource.PlayOneShot(collisionAudio, 0.5F);
        }

        if(destroyEnemy == true && hit.gameObject.tag == "Enemy")
        {
            Destroy(hit.gameObject);
        }

        if (scoreUI != null && decreaseScore != 0 && hit.gameObject.tag == "Enemy")
        {
            score -= decreaseScore;
        }
    }
2

You’re going to have to elaborate. When what something happens?

3 
public GameObject exampleGO;
private int _score;

private void Update()
{
    if (_score == 100)
    {
        Destroy(exampleGO);
    }
}

or:

private GameObject exampleGO;
private int _score;

private void Start()
{
    exampleGO = GameObject.FindWithTag("Player");
}

private void Update()
{
    if (_score == 100)
    {
        Destroy(exampleGO);
    }
}

Although it would be more efficient to use events so the code is only called when the actual score is changed.

4

Welcome! You sound like exactly the kinda person we love to see around here! Check out this super-inspirational guide about how to expand your gamedev brain. Before long you will need to purchase a larger skull to fit it all in.

Imphenzia: How Did I Learn To Make Games:

https://www.youtube.com/watch?v=b3DOnigmLBY

Dive in! The water is fine.

Tutorials and example code are great, but keep this in mind to maximize your success and minimize your frustration:

How to do tutorials properly, two (2) simple steps to success:

Step 1. Follow the tutorial and do every single step of the tutorial 100% precisely the way it is shown. Even the slightest deviation (even a single character!) generally ends in disaster. That’s how software engineering works. Every step must be taken, every single letter must be spelled, capitalized, punctuated and spaced (or not spaced) properly, literally NOTHING can be omitted or skipped.

Fortunately this is the easiest part to get right: Be a robot. Don’t make any mistakes.
BE PERFECT IN EVERYTHING YOU DO HERE!!

If you get any errors, learn how to read the error code and fix your error. Google is your friend here. Do NOT continue until you fix your error. Your error will probably be somewhere near the parenthesis numbers (line and character position) in the file. It is almost CERTAINLY your typo causing the error, so look again and fix it.

Step 2. Go back and work through every part of the tutorial again, and this time explain it to your doggie. See how I am doing that in my avatar picture? If you have no dog, explain it to your house plant. If you are unable to explain any part of it, STOP. DO NOT PROCEED. Now go learn how that part works. Read the documentation on the functions involved. Go back to the tutorial and try to figure out WHY they did that. This is the part that takes a LOT of time when you are new. It might take days or weeks to work through a single 5-minute tutorial. Stick with it. You will learn.

Step 2 is the part everybody seems to miss. Without Step 2 you are simply a code-typing monkey and outside of the specific tutorial you did, you will be completely lost. If you want to learn, you MUST do Step 2.

Of course, all this presupposes no errors in the tutorial. For certain tutorial makers (like Unity, Brackeys, Imphenzia, Sebastian Lague) this is usually the case. For some other less-well-known content creators, this is less true. Read the comments on the video: did anyone have issues like you did? If there’s an error, you will NEVER be the first guy to find it.

Beyond that, Step 3, 4, 5 and 6 become easy because you already understand!