walk function

Unity Engine
1

i have a function that tells how to walk but it has an error that I don’t know how to fix.

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

public class PlayerMovement : MonoBehaviour
{
void Move()
{
public float moveSpeed = 5f;

public Rigidbody2D rb;

Vector2 movement;
// Update is called once per frame
void Update()
{
movement.x = Input.GetAxisRaw(“Horizontal”);
movement.y = Input.GetAxisRaw(“Vertical”);
}

void FixedUpdate()
{
rb.MovePosition(rb.position + movement * moveSpeed * Time.fixedDeltaTime);
}
}
}

It says to put a close bracket after the big bracket for some reason. does anyone know how to fix this?

2

And since you have completely stripped 100% of all the useful information out of the error, not a single soul here can fix it either!

First of all, if you post a code snippet, ALWAYS USE CODE TAGS:

How to use code tags: https://discussions.unity.com/t/481379

Second of all, what is in an error matters. You can’t just summarize and say “Oh I had an error, help me.”

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 important parts of an 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)

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.

How to understand compiler and other errors and even fix them yourself:

https://discussions.unity.com/t/824586/8

How to report your problem productively in the Unity3D forums:

http://plbm.com/?p=220

3

ALSO: looks like you are probably banging your way through tutorials. Let me save you a LOT of time:

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

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!

4

I did explain what the error said it told me to close a function for no reason line (8,6)

5

You did not provide the error message, so we are working from your paraphrasing. Even if you think it has no reason to close the {, you are wrong. You have a Move() method, but then define public variables within that method - and you cannot do this.
If you posted using code tags, and with proper indentation you would see that everything in that class is sitting within the Move() method, and considering you are not even calling the Move() method in this script, you should probably remove the Move method and one of the } from the end of the script. Only once you need the Move method should you put it back in the script, and in the correct place (and not encapsulating everything within that method).