I'm stumped, I get two errors but I don't know what I am missing!?

errors: Assets\charController.cs(31,28): error CS1002: ; expected
Assets\charController.cs(33,25): error CS1002: ; expected
I have tried to research my problem but to no end....Please help!

1. using System.Collections;
2. using System.Collections.Generic;
3. using UnityEngine;
4. 
   
5. public class CharController : MonoBehaviour {
7. [SerializeField]
8. float moveSpeed = 4f;
9. 
   
10. Vector3 forward, right;
11. 
    
12. void Start()
13. {
14. forward - Camera.main.transform.forward;
15. forward.y = 0;
16. forward - Vector3.Normalize(forward);
17. right = Quaternion.Euler(new Vector3(0, 90, 0)) * forward;
19. }
20. 
    
21. void Update()
22. {
23. if (Input.anyKey)
24. Move();
25. }
26. 
    
27. void Move()
28. {
29. Vector3 direction = new Vector3(Input.GetAxis("HorizontalKey"), 0, Input.GetAxis("VerticalKey"));
30. Vector3 rightMovement = right * moveSpeed * Time.deltaTime * Input.GetAxis("HorizontalKey");
31. Vector3 upMovement - forward * moveSpeed * Time.deltaTime * Input.GetAxis("VerticalKey");
32. 
    
33. Vector3 heading - Vector3.Normalize(rightMovement + upMovement);
34. 
    
35. transform.forward = heading;
36. transform.position += rightMovement;
37. transform.position += upMovement;
38. }
39. }

 

This
Vector3 upMovement - forward * moveSpeed * Time.deltaTime * Input.GetAxis("VerticalKey");
to
Vector3 upMovement = forward * moveSpeed * Time.deltaTime * Input.GetAxis("VerticalKey");

You need to understand basic c# before copy pasting.

 

Same for line 33

 

Use [ code ] [ /code] tags in the future, mate.

The error tells you the line (31) and (33) respectively. Analyze those lines. Look at how they're different from the lines around them. You need to be able to debug your own code for simple syntax errors like this or you're going to be spinning your wheels in frustration forever.

 

the whole script seem like a trolling
look at line 14 and 16
there are more error then the OP say in the post

 

The only research needed is to increase your typing accuracy to 100%.

Unfortunately as others above note, there's so much mistyped in your code above, I'd recommend restarting the tutorial.

When you do, keep this 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:

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