Bug I have a problem that it name is cs0246

what is the problem here?
using UnityEngine;

public class scr_bala : MonoBehaviour
{
public float velocidad;

// Start is called before the first frame update
void Start()
{
Destroy(gameObject, 3f);
}

// Update is called once per frame
void Update()
{
transform.position += new Vector3(0, velocidad * Time.deltaTime, 0);
}

private void OnCollisionEnter2D(Collision2D collision)
{
if (collision.gameObject.name == "enemigo")
{
collision.gameObject.GetComponentInParent<scr_enemigo>().vida -= 1;
Destroy(gameObject);
}
}
}

 

You're probably just making typing mistakes and you need to fix them yourself. Here's how:

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

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)
- also possibly useful is the stack trace (all the lines of text in the lower console window)

Always start with the FIRST error in the console window, as sometimes that error causes or compounds some or all of the subsequent errors. Often the error will be immediately prior to the indicated line, so make sure to check there as well.

Look in the documentation. Every API you attempt to use is probably documented somewhere. Are you using it correctly? Are you spelling it correctly?

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.

Remember: NOBODY here memorizes error codes. That's not a thing. 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.

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!

Finally, when you have errors, don't post here... just go fix your errors! Start back up at the top of this message!

For future reference when you have an ACTUAL problem, if you post a code snippet, ALWAYS USE CODE TAGS:

How to use code tags: https://forum.unity.com/threads/using-code-tags-properly.143875/

 

What's the contents of the error message that came with that error code?

 

As others said, the actual contents of the error message are important. Nobody remembers the error codes. Also, please use code tags when posting code examples. Combining the two you cant really expect anybody to look through unformatted code for an unknown issue.

That said, i would like to add that you may want to code in english. Unless you are the only person to ever work with that code, variables and comments should all be in english. And if you (even just potentially, ever) are gonna post the code online to ask for help, you are not the only one who has to read it. Further, the APIs you are using are all in english, so using another language just introduces inconsistencies. I know it may be tempting to code using variable names in your own language, but to anybody who does not understand your language, these variables may as well be called "a", "b", "c" and so on, completely removing any easy context from any of the code written. This is somewhat fine for trivial and super short code, but when complexity or length grows, people wont read it and thus wont reply, even if they otherwise would have been able to help you. This is just something to consider and a well meant warning for the future, if you ever happen to post longer non-english code segments and wonder about why noone will help you.

Regarding your problem, you probably misspelled a type, likely one of your own. And yes. For this simple statement i went through the effort of formatting your code, translating the variable names, looking up the error code, and checking if i see any obvious mistakes. Make sure these scripts are called that, have matching names between file and class name, and are attached to the objects you think they are. While you are at it also make sure that public variables you are accessing (such as 'vida') actually exist, and are public, in those scripts.