Tutorial Code Not Working

I follow the unity code tutorial, i literally copy paste the code and it looks exactly like the attached image, AND IT GIVES ME 2 ERRORS (CS1513:“}” expected in 9,6 and CS1022:type or namespace definition, or end-of-file expected in 18,1). When I somehow get rid of these errors, more errors spawn. What do I do? Please help D:

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

public class BallTransform : MonoBehaviour
{
    // Start is called before the first frame update
    void Start()
    {
        public Vector3 scaleChange;
    }

    // Update is called once per frame
    void Update()
    {
        transform.localScale += (scaleChange * Time.deltaTime);
    }
}

The best way to stop getting errors is to stop inputting them in the first place. See below.

In the code above, you have lines out of place completely, so go back now to wherever you got this from because you are missing a LOT of stuff.

But once you have errors, here is how to fix them:

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.

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!

1 Like

ill try deleting and creating the script to see if that works it probably wont but ill try anyways

here is the tutorial btw Change a GameObject with script - Unity Learn

You can do this but if you recreate the same mistake the computer will give you the same mistake.

You have at least TWO mistakes above. Fix your code as the post above describes. It’s not magic.

Edit: we here in the forusm are not doing tutorials for you. You need to do them. See above for the two-step solution.

See this is just… not true. Their code:

Does not look the same as your code. Make your code look exactly like theirs and it will work.

1 Like

i added the time.deltatime thing because of one of the next steps in the tutorial, if i remove it the same errors pop up

ye well, as above stated … your code doesnt look the same, would recommend to look at this again since there are only 2 lines of code and you copy them already wrong :confused:

to extend your code will not help

2 Likes

I notice you are resisting doing the actual steps that will fix your problem as I outlined above.

Remember: the longer you resist, the longer it takes before your code is running.

This is an extremely well-understood problem that only you can fix. We cannot make you copy the code correctly. Only you can do that.

Not only that, but if you think ultra-super-hard-crazy that you copied that code perfectly (as you state above “literally copy pasted”), that also does not fix the problem.

Again, it’s not magic.

2 Likes

That answer is nonsense since its not related to the problem stated above.

It is most likely a bot.

1 Like

Does the game run in the editor without console errors but the errors appear in Visual Studio? If it does then I’d recommend trying what @MarioEfrain99 suggested. Also (Editor/preferences/External tools/Regenerate project files). Sometimes Visual Studio isn’t set up correctly. I also need to use “Regenerate project files” sometimes when I switch branches, otherwise the visual studio errors prevent me from using breakpoints.

I’d also recommend trying the script on it’s own in a new Unity project.

Not in this case. The OP copied the code incorrectly.

1 Like

That’s embarrassing, I didn’t look at the obvious errors in the code that was posted and assumed it was a copy/paste from existing/working code. Thanks for the correction.