Search Unity

  1. Unity 6 Preview is now available. To find out what's new, have a look at our Unity 6 Preview blog post.
    Dismiss Notice
  2. Unity is excited to announce that we will be collaborating with TheXPlace for a summer game jam from June 13 - June 19. Learn more.
    Dismiss Notice

Resolved Error CS1002 expected

Discussion in 'Scripting' started by FirecubeT, Oct 31, 2021.

  1. FirecubeT


    Dec 28, 2020
    I am learning Unity and was doing a Brackeys tutorial, when in my playerMovement script, I got this message: Assets/playerMovement.cs(37,54): error CS1002: ; expected. I can't find where the semicolon needs to be placed. If I place it at the end of line 37, I get other errors. Please help me.

    This is my code:
    Code (CSharp):
    1. using System.Collections;
    2. using System.Collections.Generic;
    3. using UnityEngine;
    5. public class playerMovement : MonoBehaviour
    6. {
    7.     public CharacterController controller;
    9.     public float speed = 12f;
    10.     public float gravity = -20f;
    11.     public float jumpHeight = 3f;
    13.     public Transform groundCheck;
    14.     public float groundDistance = 0.4f;
    15.     public LayerMask groundMask;
    17.     Vector3 velocity;
    18.     bool isGrounded;
    20.     // Update is called once per frame
    21.     void Update()
    22.     {
    23.         isGrounded = Physics.CheckSphere(groundCheck.position, groundDistance, groundMask);
    25.         if(isGrounded && velocity.y < 0)
    26.         {
    27.             velocity.y = -2f;
    28.         }
    30.         float x = Input.GetAxis("Horizontal");
    31.         float z = Input.GetAxis("Vertical");
    33.         Vector3 move = transform.right * x + transform.forward * z;
    35.         controller.Move(move * speed * Time.deltaTime);
    37.         If(Input.GetButtonDown("Jump") && isGrounded)
    38.         {
    39.             velocity.y = Mathf.Sqrt(jumpHeight * -2f * gravity);
    40.         }
    42.         velocity.y += gravity * Time.deltaTime;
    44.         controller.Move(velocity * Time.deltaTime);
    45.     }
    46. }
  2. exiguous


    Nov 21, 2010
    Code (csharp):
    2.         if(isGrounded && velocity.y < 0)
    3. versus
    4.         If(Input.GetButtonDown("Jump") && isGrounded)
    C# (and any programming language I'm aware off) is case sensitive. The compiler can't make sense of your statement and thus triggers this error. Syntax has to be correct when coding.
    FirecubeT likes this.
  3. FirecubeT


    Dec 28, 2020
    Oh! I didn't notice that at all. Thanks a lot! :)
    exiguous likes this.
  4. Kurt-Dekker


    Mar 16, 2013
    For future reference, 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.

    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:

    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. 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... see the top of this post.
  5. Fr0zenheartGuy


    Mar 8, 2023
    I have a problem too. i looked a video to programm a 2D Charakter. I thought i was writing 1:1 but as I´d go to Unity i couldnt start the game. in the Video he could. i searched for a problem but couldnt find it

    Assets\SunnyLand Artwork\PlayerMovement.cs(17,41): error CS1002: ; expected

    My Code:

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

    public class PlayerMovement : MonoBehaviour{

    public CharacterController2D controller;

    public float runSpeed - 40f;

    float horizontalMove - 0f;
    bool jump = false

    void Update(){
    horizontalMove - Input.GetAxisRaw("Horizontal") * runSpeed;

    if (Input.GetButtonDown("Jump"))
    jump = true;

    void FixedUpdate (){
    controller.Move(horizontalMove * Time.fixedDeltatime, false, jump);
    jump = false;

    please Help
  6. chemicalcrux


    Mar 16, 2017
    Double-clicking the error will open your IDE with the cursor placed on the source of the error. Examine that line carefully.

    Sometimes, the problem is on an earlier line, messing up the code and leading to what should be valid code becoming invalid. In this case, you should have a close look at the lines right before the error. Make sure that each one is reasonable (or try removing them, to see if the error goes away!)
  7. BABIA_GameStudio


    Mar 31, 2020
    Go back through your code and simply change where you have
    to be

    After all these types of lines are not valid C# code:
    public float runSpeed - 40f;

    float horizontalMove - 0f;

    Also, if you are following a tutorial online then make sure you can actually read the code that is in the video as otherwise you will just keep getting these issues where you are making typos.

    And as a couple of other notes:
    You should not be necroing a topic from 2 years ago because it is similar to your problem. You should have created your own topic.
    Whenever you post script code on the forum, make sure you use the code tags so that it gets formatted properly.
    chemicalcrux likes this.