How to fix "Error CS1022: Type or namespace definition, or end-of-file expected"

Unity Engine
1

Hi,

As my first app, I’m trying to build a simple clicker game. However, when trying to write some code (even following a tutorial) I’m running into an error code which I can’t seem to solve.

Here’s the code:

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

public class AutoMoney : MonoBehaviour
{
    public bool CreatingMoney = false;
    public static int MoneyIncrease = 1;
    public int InternalIncrease;


    void Update()
    {
        InternalIncrease = MoneyIncrease;
        if (CreatingMoney == false)
        {
            CreatingMoney = true;
            StartCoroutine(SellTheCoffee);
        }
    }

    IEnumerator SellTheCoffee()
    {
        GlobalMoney.MoneyCount += InternalIncrease;
        yield return new WaitForSeconds(1);
        CreatingMoney = false;
    }
}

Does anyone know why this error occurs and how I should solve it?

Thanks in advance!

Blumerd

2

Get rid of the ]:

using UnityEngine;]
1 Like
3

Thank you, doing that got rid of the CS1022.
However, it introduced two new errors which say:

“[path].cs(18,39): error CS1002: ; expected”
“[path].cs(18,39): error CS1513: } expected”

Any idea why this happens?

4

It happened because it has errors.

When using StartCoroutine, you call the method as normal. So don’t forget the () after SellTheCoffee

Remember when coding, stuff has to be correct. Typos are some of your worst enemies.

1 Like
5

Aahhh, thank you so much! So I changed it to look like this:

StartCoroutine(SellCoffee());

and now it works perfectly.

Thanks a lot!

6

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 important parts of an 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.

How to understand compiler and other errors and even fix them yourself:

7

It keeps telling me I have an error on line (3,2) but I fail to see it.8015186--1031840--upload_2022-4-2_19-55-46.png

8

The opening { should come after your class declaration. It looks like you have two, one is in the wrong place and the other is mostly in the right place. Remove the wrong one.

9

Go look at ANY other script in the whole entire world. Seriously, it will be INSTANTLY obvious how yours differs.

And please don’t reply to old scripts for your own typos. Here’s how you can fix your typos without having to hassle with forum posting:

First, remember: at the beginner level, THE COMPILER IS ALWAYS CORRECT.

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.

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.

10
11

Porque utilizando unity engine ] ; que pasa con eso?

12

it’s my first time in unity and I get error Assets\Scripts\Camera\CameraLook.cs(40,1): error CS1022: Type or namespace definition, or expected end of file
but it is not solved, someone could help me?
this is the code:
using System.Collections;
using System.Collections.Generic;
using UnityEngine;

public class CameraLook : MonoBehaviour
{

public float mouseSensivity = 80f;

public Transform playerBody;

float xRotation = 0;

}//CAcapedodeunpis
void Start()
{

}

void Update()
{

float mouseX = Input.GetAxis(“Mouse X”) * mouseSensivity * Time.deltaTime;

float mouseY = Input.GetAxis(“Mouse Y”) * mouseSensivity * Time.deltaTime;

xRotation += mouseY;

xRotation = Mathf.Clamp(xRotation, -90f,90f);

transform.localrotation = Quaternion.Eulet(xRotation, 0, 0);

playerBody.Rotate(Vector3.up * mouseX);

}

}
}

13

You are just making typing errors. Don’t do that. Your code won’t work if you make typing errors.

I see at least THREE (3) typing errors, and that is just at a quick glance. There may be more.

Here is how to fix your typing errors:

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.

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!