Bugs In Code (CS1022 and CS8803) in Unity on Visual Studio 2019

Unity Engine
,
1

Hi, I’m making a locked door for my game following my tutorial and i encountered the bugs on the title. Any ideas?
Also, i do have indents, it just didn’t put it in. Edit: now it does.
My Code:

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

public class Door : MonoBehaviour
{
    public GameObject door_closed, door_opened, intText, lockedtext;
    public AudioSource open, close;
    public bool opened, locked;

    void OnTriggerStay(Collider other) {
        if (other.CompareTag("MainCamera")) {
            if (opened == false)
                if (locked == false)
                    intText.SetActive(true);
            if (Input.GetKeyDown(KeyCode.E)) {
                door_closed.SetActive(false);
                door_opened.SetActive(true);
                intText.SetActive(false);
                //open.Play();
                StartCoroutine(repeat());
                opened == true;
                    }
        }
        if (locked == true) {
            lockedtext.SetActive(true);
        }
    }
   }
}
    void OnTriggerExit(Collider other)
        {
            {
        if (Other.CompareTag("MainCamera"))
           {
               {
                intText.SetActive(false);
                lockedtext.SetActive(false);
            }
        }
        IEnumerator repeat()
        {
            yield return new WaitForSeconds(4.0f);
            opened = false;
            door_closed.SetActive(true);
            door_opened.SetActive(false);
            //close.Play()
        }
    }
}
2

Please post the line numbers the errors are on. It will tell you in the console when you highlight them.

3

alright

4

CS1022 is at 30, 1
CS8803 is at 31, 5

5

It looks like you have an extra } bracket on line 30. Edit: On second glance there might be 2 extras, lines 29 and 30.

6

kk ill fix that
(so i dont need the bracket?)
(Edit: yeah i dont :skull:)

7

now what next

8

Right. Also I ghost edited my previous post. I think you may have 2 extra brackets in there. The editor should show you what they’re enclosing, and proper indentation will help you see it as well.

9

also, no errors appear on the bracket in line 29, so ill play it safe.

10

Often an error of that sort will come after the extra bracket because the compiler sees that bracket as ending something and then the next line doesn’t make sense to it.

11

I looked, and yeah, 29 is not an extra bracket, it just ends the first one.

12

Anyways, what about CS8803?

13

You have another extra opening bracket after your OnTriggerExit. You should have an opening and closing bracket for the class as a whole, and a set for each function, and a set for each if statement.

14

Where?

15

No one remembers error codes. You have extra curly braces all over the script, compounded by how squashed together all your code is.

Space your code out, it should be easy to workout where the extra braces are and remove them.

Also forums aren’t a IRC channel. Don’t double post.

1 Like
16

That didn’t happen! You made typing mistakes, that’s all, and you don’t need us to fix them.

You’re even sticking functions inside of other functions and that won’t work here.

You can fix them all your sefl… check it out!

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.

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.

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… see above!

2 Likes
17

You have some rogue sets of curly braces. Delete the ones on 28, 29 and 32. You have another set you can delete on 36 and 39. They won’t cause you an error but they’re not doing anything so you can delete them.

On line 25 remove one = sign. == is to check if things are equal. = is to assign a value which is what you want.

Should probably rename repeat to Repeat too as per method naming conventions in C#.

18

Go through some beginning programming books/tutorials. Closed.