CS1513 EXPECTED (31,16)

Unity Engine
1

WHAT WRONG WITH THIS CODE I WRITED SAME AS A YOUTUBE TUTORIAL I STUCK FOR 2 DAY ABOUT THIS ERROR

PLZ HELP TO FIND

using System.Collections;
using System.Collections.Generic;
using UnityEngine;

public class sqaure : MonoBehaviour
{
public bool IJ;

// Start is called before the first frame update
void Start() {
IJ = false;

// Update is called once per frame
void Update() {
if(Input.GetKeyCode.Space) IJ==false;
{

GetComponent ().velocity = new Vector3 (0,4,0);
IJ= true;
}

void OnCollisionEnter2D(Collision2D Coll)
{
if(Coll.gameObject.tag==“finish”)

{
IJ = false;
}
}

2

First, please use code tags to make your code more readable on the forumn. Secondly, please post the entire error message.

using System.Collections;
using System.Collections.Generic;
using UnityEngine;

public class sqaure : MonoBehaviour
{
public bool IJ;

// Start is called before the first frame update
void Start() {
IJ = false;


// Update is called once per frame
void Update() {
if(Input.GetKeyCode.Space) IJ==false;
{


GetComponent<Rigidbody2D> ().velocity = new Vector3 (0,4,0);
IJ= true;
}


void OnCollisionEnter2D(Collision2D Coll)
{
if(Coll.gameObject.tag=="finish")

{
IJ = false;
}
}
3

Looks like you have not closing } for your start method.

1 Like
4

I believe you have an extra ; here and a misplaced closing paren

if(Input.GetKeyCode.Space) IJ==false;

1 Like
5

I took a look at the code you have here and I can see several Issues here. I will list the problems an the solution to your code below.

  • jbnwilliams1 have spotted a mistype where you are missing the closing bracket ( } ) on line 12 to close off the start function. This is a simple fix
// Your Code:
void Start() {
     IJ = false;
          // < You have { missing

// Solution:
void Start() {
     IJ = false;
}
  • On line 16, you have an if function that is not properly formatted. This will have a cascading error issue through the entire code, which is probably why, assuming if the log looked like this, looked to be 1 Million different errors. (Edit) This, in term, is also a simple fix by moving the closing parenthesis to the end and removing the semicolon ( ; ).
  • On Line 23, you forgot another closing bracket ( } ) to finished off the function on line 16. Similar fix to 1
  • Finally: you forgot to close off the entire class using a closing bracket ( } ) on the last line of code.

With all the solutions in place and a bit of styling, here is what your code would look like:

using System.Collections;
using System.Collections.Generic;
using UnityEngine;

public class sqaure : MonoBehaviour
{
public bool IJ;
     // Start is called before the first frame update
     void Start() {
          IJ = false; // IJ = In Jump
     }
     // Update is called once per frame
     void Update() {
          // Perform a jump if we are on the ground and pressed Spacebar
          if(Input.GetKeyCode.Space && IJ==false) {
               GetComponent<Rigidbody2D> ().velocity = new Vector3(0,4,0);
               IJ= true;
          }
     }
     void OnCollisionEnter2D(Collision2D Coll) {
          if(Coll.gameObject.tag=="finish") {
               //Enable the abillity to jump again
               IJ = false;
          }
     }
}

I hope this helps solve your issue. if you still have a problem. go ahead and post the problem again. I am fairly new, so It is possible that I made an error or two.

1 Like
6

Good lord, TWO DAYS?! You must learn how to read error messages, and learn how to type accurately. You will have a really hard time until you do.

Fortunately error messages are SUPER easy to read. Here is how:

Remember: NOBODY memorizes error codes. 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.

If you plan on mashing code into your keyboard, keep this in mind:

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!

2 Likes
7

I am trying to make a game and while trying to do the grounded check the error cs1513 appeared and i am struggling to find the problem. (it says the error is on 39,37)

using System.Collections;
using System.Collections.Generic;
using UnityEngine;
using UnityEngine.UI;

public class MInecraftMovement : MonoBehaviour
{
    public float Speed;
    public Rigidbody rb;
    public float distToGround = 1f;

    public Text debug;

    void Update()
    {
        PlayerMovement();
            if(Input.GetButtonDown("Jump") && cubeIsOnTheGround == true){
                rb.AddForce(new Vector3(0, 5, 0), ForceMode.Impulse);
            }
 
    }

    void PlayerMovement()
    {
        float hor = Input.GetAxis("Horizontal");
        float ver = Input.GetAxis("Vertical");
        Vector3 playerMovement = new Vector3(hor, 0f, ver) * Speed * Time.deltaTime;
        transform.Translate(playerMovement, Space.Self);
    }

    private void Start()
    {
     
    }
    private FixedUpdate()
    {
        if (Physics.Raycast(transform.position, Vector3.down, distToGround + 0.1f));
        {
            debug.text = "Grounded";
            else
                debug.text = "Not Grounded";
        }
    }
}
8

Often a compiler will highlight a problem because you made a mistake before it. You just need to open your eyes and look at the code in detail, preferably after a 10 minute break.

Take a look at line 37 where you’ve incorrectly added a semi-colon at the end.

1 Like
9

thank you i dint realist that the semi Colin doesn’t belong there