Solved - Challenge Destroying an Object

I'm working on a tower defense game and it has an object "Bullet" that is fired from a turret object "Tower".

I want to destroy the Bullet if it collides with another Tower (instead of the enemy).

So, I wrote this:

Bullet On Collision with Tower -> Bullet Destroy

But, since the Bullet is being created on top of a Tower, it is destroying the Bullet before it can even move away from the tower that created it.

Is there a simple way to prevent this from happening?

Thanks in advance,

Chris

p.s. In my game, these bullets bounce, so it's possible the bullet would hit the original tower and that should destroy it as well (just not as soon as it appears).

There are different approaches. You could add an instance variable on the bullet to track where its spawned from so in your spawn bullet event directly under the spawn action you can set the bullet.var to tower.UID (the tower picked will be the one that is spawning the bullet)

Now that the bullet has the UID of the spawning tower attached, on the collision with tower event you can add another condition bullet.var does not equal tower.UID, meaning the bullet will not be destroyed by the tower spawning it.

As for being destroyed by the spawning tower later there are couple of ways. I used bouncing bullets in my game and I used another variable that tracks the number of bounces, so again on that same collision with tower event, with an action you can add 1 to this new numBounces var. Then you could add an event like if bounce > 0 set bullet.var (the UID check) to 9999 means it will now be destroyed when colliding with the spawning tower.

There may be a simple way to do this with parent/child hierarchy but I've not used that functionality.

That's not bad either! You just need to remove the Else and bring the second event out of a sub event on its own. With the two separate events I think you should see it working.

That's not bad either! You just need to remove the Else and bring the second event out of a sub event on its own. With the two separate events I think you should see it working.

Thanks for that suggestion, it tightened the code and works perfectly.