I tried following some simple tutorial for character movement and I can’t even manage to make it work when copying the script…
“Script.cs(12,19): error CS1519: Invalid token ‘=’ in class, struct, or interface member declaration”
You 100% did not copy the script correctly. You can’t have code just floating outside of any methods like that (not to mention the use of undeclared variables, etc…)
Go back and copy it more carefully.
1 Like
As Praetor said, it really doesn’t look like you’ve copied your code.
This is if you ‘copied’ the code from the source, cause I’m not sure if you actually wrote it out, and saying copied, or actually copied it
A couple personnel tips from me are do not copy and paste code, your not really learning anything except how to use ctrl + c and ctrl + v, Go through the tutorial carefully and type it out according. Thats a much better idea!
No, I did not copy and paste it. I did actually type it out and I checked multiple time but apparently I did something wrong and I cannot figure out what it is…I watched the tutorial 3 times by now. 
If that tutorial has told you to do the code you posted above, get away from that tutorial maker, dislike that video and do not go near ANYTHING he has ever done with Unity. Just forget that person.
Here’s some really good people:
Imphenzia / imphenzia - super-basic Unity tutorial:
https://www.youtube.com/watch?v=pwZpJzpE2lQ
Jason Weimann:
https://www.youtube.com/watch?v=OR0e-1UBEOU
Brackeys super-basic Unity Tutorial series:
https://www.youtube.com/watch?v=IlKaB1etrik
Sebastian Lague Intro to Game Development with Unity and C#:
https://www.youtube.com/watch?v=_cCGBMmMOFw
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.