error CS1003: Syntax error, '(' expected

Unity Engine
,
1

I am trying to make a enemy ai which follows the player, I am also making a spawner so I turned my enemy from a gameObject to a prefab ( dragged enemy from inspector to my assets )

anyways, i try the wave spawner and for some reason, the public reffrence to which game object to follow is gone

I tried many things, it didnt fix this issue

so i tried Hard coded the “target to follow” reffrence to a gameobject with a tag “player”

its giving me this error: error CS1003: Syntax error, ‘(’ expected
the error is in line 9

pls help i am really. really new in unity

8497967–1131293–EnemyFollowAI.cs (740 Bytes)

2

i dragged enemy from hierachy

3

Hi and welcome to the forum.
When you post code, post it on the forum using code tags. Few people are going to download your files.

First and foremost, when you take an object from the scene and turn it into a prefab, the references to any other gameobject in that scene are gone (unless contained within the prefab). Because, how would it reference those? They might not exist in their new context, and certainly dont exist in the context of the prefab itself.

So you would have to set the correct target manually when spawning the enemy. This can happen in the enemy script, as you appear to be attempting, but it might also simply happen where you instantiate this enemy. I would argue that this is cleaner, as it also does not require us to use Find() whenever we spawn an enemy.

Something along those lines of thought:

enemy = Instantiate(yourEnemyPrefab, yourEnemyPos, Quaternion.identity);
enemy.target = yourPlayerReference

So whatever script spawns the enemy simply needs a reference to the player, which it then can simply pass to the enemy.

Whatever you do, this is not valid C# code. At all. And even if it was, it alone would do nothing.

public GameObject gameObject.tag = "Player";

If you were to go that route, you would have to Find() the correct player gameobject (based on name, tag, …) in the Start() of your enemy. As the Find function and all of its variants are quite inefficient by design, i do not recommend using them outside of prototyping. Since you are clearly still learning Unity and C#, i would highly argue against getting in the habit of using Find()s at all. For mostly everything you will ever do, there is always a better way than to use Find - exceptions may occur in corner cases like writing your own editor scripts.

4

This means you are making typing mistakes.

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.

If you’re hammering this in from tutorial code, go back because you made mistakes.

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!

Finally, when you have errors… don’t post here… go back to the top of this post and fix your mistakes.