Search Unity

Question Assets\script\playercontroller.cs(5,46): error CS1003: Syntax error, ',' expected help please

Discussion in 'Getting Started' started by dangerbog, Aug 23, 2023.

  1. dangerbog


    Aug 23, 2023
    using System.Collections;
    using System.Collections.Generic;
    using UnityEngine;

    public class playercontroller : MonoBehaviout;
    public float speed;
    public float jumpForce;
    private float moveInput;

    private RigitBody2d rb;

    private bool facingRight = true;

    private void Start()
    rb = GetComponent<Rigitbody20>();

    private void FixedUpdate()
    moveinput = input.GetAxis("Horizontal");
    rb.velocity = new Vector2(moveInput * speed, rb.velocity.y);
    if (facingRight == false && moveInput > 0);
    else if (facingRight == true && moveInput < 0)

    void flip()
    facingRight = !facingRight;
    Vector3 Scaler = transform.localScale;
    Scaler.x *= -1;
    transworm.localScale = Scaler;
  2. Kurt-Dekker


    Mar 16, 2013
    You're just making typos. Now go fix them. Here's how:

    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.

    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.

    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.
  3. MelvMay


    Unity Technologies

    May 24, 2013
    This isn't related to 2D nor 2D physics (removed the tag), it's typos. I'll move your post to the getting started forum for you.

    As above "(5,46)" means line 5, column 46. If you were to look on line 5 you should quickly see you typed "RigitBody2d" which clearly should be Rigidbody2D. Further down you typed "Rigitbody20". The forums should not be used to find typos for you so you're best to go back to the tutorial and scan the code line by line. :)

    Also, so you know, please edit your posts to use code-tags when posting code.

  4. BABIA_GameStudio


    Mar 31, 2020
    You have so many issues with this script you would be better starting from scratch.

    Other than what MelvMay has already mentioned, you have 2 mistakes on this earlier line:
    public class playercontroller : MonoBehaviout;

    1 - you should not have a
    at the end of that line.
    2 - it should be
    , not

    Further down your script, you call
    , yet you have actually named your method
    . Capitalisation matters just as much as spelling.

    You also have
    instead of

    You need to stop making spelling mistakes, otherwise you aren't going to get anywhere, and you will just keep coming back here for us to point them out to you.
    Ruslank100, MelvMay and bugfinders like this.