Search Unity

Question My code have an error

Discussion in 'Scripting' started by P0loO, Nov 19, 2022.

  1. P0loO

    P0loO

    Joined:
    Nov 18, 2022
    Posts:
    2
    My code have this error: Assets/Déplacement.cs(33,72): error CS1002: ; expected , and : Assets/Déplacement.cs(40,71): error CS1002: ; expected. I cant resolve it so can you help me please?

    Theres my code:

    Code (CSharp):
    1. using System.Collections;
    2. using System.Collections.Generic;
    3. using UnityEngine;
    4.  
    5. public class Déplacement : MonoBehaviour
    6. {
    7.     //Animations du perso
    8.     Animation animations;
    9.  
    10.     // Vitesse de déplacement
    11.     public float walkSpeed;
    12.     public float runSpeed;
    13.     public float turnSpeed;
    14.  
    15.     // Inputs
    16.     public string inputFront;
    17.     public string inputBack;
    18.     public string inputLeft;
    19.     public string inputRight;
    20.  
    21.     public Vector3 jumpSpeed;
    22.     CapsuleCollider playerCollider;
    23.    
    24.     void Start()
    25.     {
    26.         animations = gameObject.GetComponent<Animation>();
    27.         playerCollider = gameObject.GetComponent<CapsuleCollider>();  
    28.     }
    29.  
    30.     void Update()
    31.     {  
    32.         //si on avance
    33.        if(Input.GetKey(inputFront)) & !Input.GetKey(KeyCode.LeftShift)
    34.         {  
    35.             transform.Translate(0,0, walkSpeed * Time.deltaTime);
    36.             animations.Play("walk");
    37.         }
    38.  
    39.         //si on sprinte
    40.        if(Input.GetKey(inputFront)) & Input.GetKey(KeyCode.LeftShift)
    41.         {  
    42.             transform.Translate(0,0, runSpeed * Time.deltaTime);
    43.             animations.Play("run");
    44.         }
    45.         //si on recule
    46.         if(Input.GetKey(inputBack))
    47.         {
    48.             transform.Translate(0,0, -(walkSpeed / 2) * Time.deltaTime);
    49.             animations.Play("walk");
    50.         }
    51.  
    52.         //rotation a gauche
    53.        if(Input.GetKey(inputLeft))
    54.         {  
    55.             transform.Rotate(0,-turnSpeed * Time.deltaTime,0);
    56.         }
    57.  
    58.      
    59.    
    60.         //rotation a droite
    61.        if(Input.GetKey(inputRight))
    62.         {  
    63.             transform.Rotate(0,turnSpeed * Time.deltaTime,0);
    64.         }
    65.     }    
    66. }
     
  2. MelvMay

    MelvMay

    Unity Technologies

    Joined:
    May 24, 2013
    Posts:
    11,497
    The error tells you the line and column numbers. All you have to do is look at those lines and check to see what you've typed wrong.

    (33, 72) Line 33, Column 72
    (40, 71) Line 40, Column 71

    Look at them, you've messed up the open/close brackets.
     
  3. Kurt-Dekker

    Kurt-Dekker

    Joined:
    Mar 16, 2013
    Posts:
    38,745
    You are simply making typing mistakes. You must make ZERO typing mistakes.

    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, 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.

    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.