CS8803: top-level statements must precede namespace and type declarations

Question

1.00/5 (1 vote)

See more:

How do I solve this it shows assets\scripts\playercontroller.cs(13, 1): error CS8803: top-level statements must precede namespace and type declarations.

What I have tried:

C#

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

public class PlayerController : MonoBehaviour

{
    Rigidbody rb;
    public float jumpForce;
    bool canJump;
}
    
void Awake();
    {
        rb = GetComponent();
    }

    
    // Start is called before the first frame update
    void Start()
    {
        
    }

    // Update is called once per frame
    void Update()
    {
        if (Input.GetMouseButtonDown(0) && canJump)
        {
            //jump

            rb.AddForce(Vector3.up * jumpForce, ForceMode.Impulse);
            
        }

    }

    void OnCollisionEnter(Collision collision)
    {
            if(collision.gameObject.tag == "Ground")
        {
            canJump = true;
        }
    }

    void OnCollisionExit(Collision collision)
    {
        if(collision.gameObject.tag == "Ground")
        {
            canJump = false;
        }

}

Posted 5-Jun-23 3:21am

Aryan Jun2023

Updated 5-Jun-23 3:59am

Dave Kreskowiak

v2

Add a Solution

2 solutions

Add a Solution

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

Richard MacCutchan · Answer 1 · 2023-06-05T03:28:00

Solution 1

You have terminated the class definition before including the class methods:

C#

public class PlayerController : MonoBehaviour

{
Rigidbody rb;
public float jumpForce;
bool canJump;
// } ***** remove this closing brace so the remaining code is part of the class.

Also please remove all those repeated entries of "nothing" in the "What I have tried" section.

Posted 5-Jun-23 3:28am

Richard MacCutchan

Comments

Aryan Jun2023 5-Jun-23 12:02pm

still not working brother

Aryan Jun2023 5-Jun-23 12:03pm

when shoul i add } then

Richard MacCutchan 5-Jun-23 12:13pm

Try reading your code. Count the number of open braces and find their matching closures.

OriginalGriff · Answer 2 · 2023-06-05T03:59:00

To add to what Richard has said ... You should expect to get syntax errors every day, probably many times a day while you are coding - we all do regardless of how much experience we have! Sometimes, we misspell a variable, or a keyword; sometimes we forget to close a string or a code block. Sometimes the cat walks over your keyboard and types something really weird. Sometimes we just forget how many parameters a method call needs.

We all make mistakes.

And because we all do it, we all have to fix syntax errors - and it's a lot quicker to learn how and fix them yourself than to wait for someone else to fix them for you! So invest a little time in learning how to read error messages, and how to interpret your code as written in the light of what the compiler is telling you is wrong - it really is trying to be helpful!

So read this: How to Write Code to Solve a Problem, A Beginner's Guide Part 2: Syntax Errors[^] - it should help you next time you get a compilation error!

I'm not saying we don't want to help you fix them - sometimes I can't see my own errors because I read what I meant to write - but fixing syntax errors is part of the job, and if you can't do it for yourself people are going to look at you as a bit weird should you get a job in the industry!