'Collider2D' does not contain a definition for 'ComapareTag' and

Unity Engine
1

Hey guys,
so I am getting this very weird error that says:
KillPlayer.cs(12,19): error CS1061: ‘Collider2D’ does not contain a definition for ‘ComapareTag’ and no accessible extension method ‘ComapareTag’ accepting a first argument of type ‘Collider2D’ could be found (are you missing a using directive or an assembly reference?)

I am trying to resolve this issue for like an hour now and I am not able to figure it out. Can you please help? Here is the code I am using:

using System.Collections;
using System.Collections.Generic;
using UnityEngine;
using UnityEngine.SceneManagement;

public class KillPlayer : MonoBehaviour
{
    public int Respawn;

    void OnTriggerEnter2d(Collider2D other)
    {
        if (other.ComapareTag("Player"))
        {
            SceneManager.LoadScene(Respawn);
        }
    }
}

Thanks.

2

It’s telling you exactly what is wrong; “ComparaTag” doesn’t exist so a quick look at the API docs will show you what does exist and in this case, the correct spelling.

Also, “OnTriggerEnter2d” isn’t correct either. It’ll compile without error but Unity won’t call it because you need to spell things exactly AND use the correct case. It’s this.

1 Like
3

Oh I totally missed that! Thanks!

4

If you want to monkey-hammer-bang tutorial code in, it has to be 100% perfect. Keep these important steps in mind or else you risk wasting a LOT of your own time.

How to do tutorials properly:

Tutorials are a GREAT idea. Tutorials should be used this way:

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 single letter must be spelled, capitalized, punctuated and spaced (or not spaced) properly. 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 it. Google is your friend here. Do NOT continue until you fix the error. The 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.

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!

ALSO, if you EVER get an error,

Remember: NOBODY memorizes error codes. The error code is absolutely the least useful part of the error. It serves no purpose at all. Forget the error code. Put it out of your mind.

The complete error message contains everything you need to know to fix the error yourself.

Always start with the FIRST error in the list, as sometimes that error causes or compounds some or all of the subsequent errors.

The important parts of the error message are:

  • the description of the error itself (google this; you are NEVER the first one!)
  • the file it occurred in (critical!)
  • the line number and character position (the two numbers in parentheses)

All of that information is in the actual error message and you must pay attention to it. Learn how to identify it instantly so you don’t have to stop your progress and fiddle around with the forum.

5

why does this give me an error its stumprd me for the past to hours
void OnTriggerEnter2D(Collider2D collision)
{
if (Collision.CompareTag(“Player”))
{
}
}

6

i am a code monkey like kurt dekker said

7

What was mentioned was “EXACT” spelling, that includes capitals. With that knowledge, take another look at the code you posted.

8

also it is not a good idea to open an old post, better create a new one, or better, check your spelling first.

9

Don’t hijack/necro other posts. Please create your own.

1 Like