My triggers and colliders are not functioning
I used the following script to detect it. On has a rigidbody, one doesnt. one also has trigger enabled as well
private void onTriggerEnter(Collider other){
entered = true;
Debug.Log("Entered");
}
Please help, im so lost
Nothing happens when they trigger each other.
I am sure they touch
And it is happening with all my triggers
The spelling/capitalisation matters for all Unity messages: Unity - Scripting API: Collider.OnTriggerEnter(Collider)
Start with the docs. As Spiney points out, you’re just making typos. Don’t do that because the computer will REQUIRE you to fix them all.
While you’re in there seeing how that method is called, review all the different requirements that must be met in order for you to receive these messages. There are several and they are all specified in the documentation. If you do not meet any one of those requirements, you will not be called.
Oh my gosh im such an idiot
thank you for your help
Me too… but I’m a professional idiot and people pay me to write code. My secret is to plunge into the docs, check every little part, tell my dog what I’m doing (see over on the left?), and if something is too mysterious, set it aside, give my dog a treat and retype it afresh as a separate script, again checking every bit as I go.
It’s weird dance between the first time you go in the docs and see sheets of “whoa what is this stuff?” and then now when you go in it all sorta starts making sense even to an idiot like me. 
Check this process: it sounds tedious but the more you do it, it just gets faster because you can call so much stuff right to the front of your brain immediately:
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… just go fix your errors! Here’s how:
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:
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.
Look in the documentation. Every API you attempt to use is probably documented somewhere. Are you using it correctly? Are you spelling it correctly?
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.
Imphenzia: How Did I Learn To Make Games:
