Assets\scrips\NewBehaviorScript.cs(7,35)_: error CS1003: Syntax error ',' expected

I`m new and I have that error with the following code, So this is my script: I have the error CS1003: Syntax error ',' expected. How can I fixed it?

Code (CSharp):

1. using System.Collections;
2.     using System.Collections.Generic;
3.     using UnityEngine;
4.  
5.     public class NewBehaviourScript : MonoBehaviour
6.     {
7.         private Rigidbody2D Rigidbody2D;
8.         private float Horizontal;
9.  
10.         void Start()
11.         {
12.             Rigidbody2D = GetComponent<Rigidbody2D>();
13.         }
14.  
15.         void Update()
16.         {
17.             Horizontal = input.GetAxisRaw("Horizontal"); // pulsa A=-1  D=1
18.         }
19.         private void FixedUpdate()
20.         {
21.             Rigidbody2D.velocity = new Vector2(Horizontal, Rigidbody20.velocity.y);
22.         }
23.     }
24.  

 

Hey!

As in the error suggests " CS1003: Syntax error ','" it is all about a missing ; somewhere. Keep in mind that C# needs to be compiled by unity so that Unity can show us the errors. For this to work you need to save the latest changes. It seems like your script is correct but the changes you have made were not saved.

If you are using Visual Studio 2019 as an IDE sometimes either Unity or Visual Studio looses connection and the new code is not compiled. In those cases restarting both applications always seems to help.

I hope it helps!

 

Additional things that are wrong or seems to be wrong are:

it's

Input

, not

input

. Class and type names usually start with a captial letter.

Another thing that is not right: The error in your title states that the error is in a file named

NewBehaviorScript.cs

, however your actual class is called

NewBehaviourScript

. That's not the same name. Script name and class name have to match. Apart from that you should give your classes and variables meaningful and descriptive names, don't be lazy.

While I agree that you should avoid naming a variable the same as a type, it is actually supported by C#. Though it can cause countless of headache, especially when you're inexperienced. Though, copying your code, fixing the "Input" and the "Rigidbody20" typo, your code compiles for me. So the error you mentioned in your title does not show up for me. So you either somehow made a mistake by copying your actual code into your forum post, or you somehow did not hit save before switching to Unity and the error may relate to an older version of your broken script? Really, you have to be more careful what you're doing. At least check it yourself at least once.

 

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

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.

Always start with the FIRST error in the console window, as sometimes that error causes or compounds some or all of the subsequent errors.

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)

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.