Error Message

Hello so I have been getting an error message about an 'Invalid token' The full message is "Assets\Scripts\PlayerMovement.cs(29,3): error Cs1519:Invalid token 'if' in class, struct, or interface member declaration" If anyone knows what this error message can you help me fix it and here is my full script so you can see if I have gone wrong anywhere (Italics is the script)
using System.Collections;
using System.Collections.Generic;
using UnityEngine;
public class PlayerMovement : MonoBehaviour{
public float speed;
public Rigidbody rigid;
// Start is called before the first frame update
void Start() {

rigid = GetComponent<Rigidbody> ();
}
void Update() {
transform.Translate(Vector3.right * speed * Time.deltaTime);
}
// Update is called once per frame
void OnCollisionStay () {
}

if (Input.GetKeyDown (KeyCode.A)) {
rigid.velocity = new Vector3 (0, 2, 3);
}

if (Input.GetKeyDown (KeyCode.D)) {

rigid.velocity = new Vector3 (0, 2, -3);
}

 

Hello,
please use code tags :

[code=CSharp][/code]

so it could be readable.
Your ifs' are outside everything. They need to be into a method.
I'm not sure what you want exactly but it should be somewhere like that

Code (CSharp):

1. using System.Collections;
2. using System.Collections.Generic;
3. using UnityEngine;
4. public class PlayerMovement : MonoBehaviour{
5. public float speed;
6. public Rigidbody rigid;
7. // Start is called before the first frame update
8. void Start() {
9.  
10.    rigid = GetComponent<Rigidbody> ();
11. }
12.  
13. // Update is called once per frame
14. void Update() {
15.    transform.Translate(Vector3.right * speed * Time.deltaTime);
16.  
17.    if (Input.GetKeyDown (KeyCode.A)) {
18.       rigid.velocity = new Vector3 (0, 2, 3);
19.    }
20.  
21.    if (Input.GetKeyDown (KeyCode.D)) {
22.       rigid.velocity = new Vector3 (0, 2, -3);
23.    }
24. }
25. void OnCollisionStay () {
26. }
27.  

 

As I pointed out in your other thread, you cannot make even a single character mistake when monkey-hammer banging tutorial code in. That has to be PERFECT, 100% perfect in every way. That's the easy part.

Read on for some serious time-savers:

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.

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!

 

This is the tutorial Unity 5 Endless Runner Tutorial 4 | Dodging Obstacles Part 2 - YouTube

 

They are doing it so the block can only jump once so it doesn't go flying and no-one has commented on the video heres the video if you want to have a look Unity 5 Endless Runner Tutorial 4 | Dodging Obstacles Part 2 - YouTube

 

I don't know what code tags are I'm new

 

Welcome to the forum
https://forum.unity.com/threads/using-code-tags-properly.143875/