- Home /
Why the f**k do i have compile errors for no reason? Why do I have Compile errors when All of my scripts have no errors?
999+ errors showing on the console and when I click one, it leads me to one of my scripts. It says I have 0 errors in all of them so what the hell does this mean? Only happened when I was making a health bar system and everything before worked perfectly. I cant figure out why just now it happened. But nothing red shows and it still says 0 errors. :(
Feel your frustration. Hope you backed-up before you made changes. I've encountered situations like this before when some unity script is generating an error. In this case, it will show the line in $$anonymous$$Y script that invoked the unity function. In nearly all cases, so far, the error generated by the unity script, was because I had provided some incorrect data somewhere. $$anonymous$$gest using Debug.Log to confirm the runtime data and execution path.
are they actual errors ( the red stop sign) or the yellow yield sign ones? or even the cartoon bubble with a "!" in it? A screen grab would help a lot. Sometimes a yellow one is just telling you declare a variable you never use. The cartoon bubble could just be where a script says something like "print (hit.collider.gameObject.name);" for raycast and sometimes red could be also from a raycast that is sending a message to something you hit but has no receiver. Again, more info like a screen grab of the messages would help
Well how about posting the actual error so we can help you?
Answer by Bunny83 · Apr 16, 2018 at 07:07 PM
If you have 999+ errors they are most likely not compiler errors but runtime errors. If you have compiler errors you won't be able to even start your game. Runtime errors are either logical errors in yours scripts or just missing references. Logic errors can't be detected by the compiler since the compiler has no idea about what you actually want to do.
This question is way to abstract to get a clear answer since you did not mention a single error in your description.
Going off of this, you may want to look into your update loops. If you are seeing an error pop up 999+ times, it's likely because the error is being hit in every Update or FixedUpdate call.
Your answer

Follow this Question
Related Questions
Compile Error in XCode with Unity SplashScreenController/UnityViewControllerBase for IOS build 0 Answers
Unity 4.3.4 iOS Warnings - iAD and Asset Catalog 0 Answers
add two compile instruction into "smcs.rsp",lead to internal compile error! 2 Answers
im having a compile error 0 Answers
Cannot implicitly convert type UnityEngine.MeshRenderer to UnityEngine.Material. 1 Answer