I dont know why but the bomb just dosent do damage to the player even though the player colides with the bomb and the bomb object gets destroyed.
7617694–947002–Bomb.cs (447 Bytes)
7617694–947005–Player.cs (2.13 KB)
I dont know why but the bomb just dosent do damage to the player even though the player colides with the bomb and the bomb object gets destroyed.
7617694–947002–Bomb.cs (447 Bytes)
7617694–947005–Player.cs (2.13 KB)
If you post a code snippet, ALWAYS USE CODE TAGS:
How to use code tags: Using code tags properly
You must find a way to get the information you need in order to reason about what the problem is.
What is often happening in these cases is one of the following:
To help gain more insight into your problem, I recommend liberally sprinkling Debug.Log() statements through your code to display information in realtime.
Doing this should help you answer these types of questions:
Knowing this information will help you reason about the behavior you are seeing.
You can also put in Debug.Break() to pause the Editor when certain interesting pieces of code run, and then study the scene
You could also just display various important quantities in UI Text elements to watch them change as you play the game.
If you are running a mobile device you can also view the console output. Google for how on your particular mobile target.
Another useful approach is to temporarily strip out everything besides what is necessary to prove your issue. This can simplify and isolate compounding effects of other items in your scene or prefab.
Here’s an example of putting in a laser-focused Debug.Log() and how that can save you a TON of time wallowing around speculating what might be going wrong: