I need help

Unity Engine
,
1

assets\player.cs(13,25): error cs1002: ; expected

I got this error when i was trying to follow some tutorial of the internet
Here is the code:

using System.Collections;
using System.Collections.Generic;
using UnityEngine;
public class Player : MonoBehaviour
{
Rigidbody2D rb;
public float moveSpeed;
public float rotateAmount;
float rot;
private void Awake()
// Start is called before the first frame update
void Start()
{
rb = GetComponent();
}
// Update is called once per frame
void Update()
{
if (Input.GetMouseButton(0))
{
Vector3 mousePos = Camera.main.ScreenToWorldPoint(Input.mousePosition);
if(mousePos.x < 0)
{
rot = rotateAmount;
}
else
{
rot = -rotateAmount;
}
transform.Rotate(0, 0, rot);
}
}
private void FixedUpdate()
{
rb.velocity = transform.up * moveSpeed;
}
}

2

The error is telling you that you’re missing a semicolon in the player.cs file, at that position. All lines within your code that are stand alone lines require a semicolon line terminator. This means lines that are not in parenthesis or starting/closing braces.

Is the code snippet above the actual assets\player.cs? Did you save the file after editing it in your editor before running?

3

It says there is a error in the 10th line and in the 25th line
10th line: private void Awake()
25th line: }
Im a new developer and i don’t really understand C# so sorry if i don’t understand some things.

4

You’re just making typos. You cannot have ANY typos.

Go back and carefully work through it again, and when you do, keep these two steps in 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.
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…

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.

5

Please share a screenshot of the tutorial showing the code for Awake(). If it’s in a video, share the link in the video along with the time when the code is shown. So you know, it would probably be more like the following, you left out the { and } brackets.

Using code tags:

private void Awake()
{

}
6

Here is the youtube link:

https://www.youtube.com/watch?v=t-rdSI3-Hfk

the time is 6:35

7

Yes, look at his Awake(), it is not like yours. You put the code in Start() instead.