Big bug with the destroy block

The second object somehow destroys the original object even though only clones should be destroyed. It may be trying to destroy itself after it had already been destroyed, and destroying the original object in accident. Keeping track of if the object has been destroyed and making sure the second destroy block doesn’t destroy it if it has fixes this.

14 Likes

Ya I’m pretty sure you did.

1 Like

I use Total clones of destroyed object causes womp in this project to womp the project when the original object is destroyed, but this is a different bug.

3 Likes

It’s kinda similar.

1 Like

I don’t see the bug. This pops up before I can see the bug.

3 Likes

That’s caused by the bug. I use another bug to cause that when the original object is destroyed.

3 Likes

I’m pretty sure it’s actually quite different
same block, different glitch

1 Like

I don’t notice what happens.
What was very important is that I keep on getting "Womp"ed.

1 Like

Same with me

2 Likes

Strange bug. I’m not sure why it does this.

1 Like

I’m not sure but I did see a code block that said
When I get a message (clone)
Check if else (self clone index =0)
Create a clone
Else
Destroy

That makes me think that if there are 5 clones running the same code, they will all destroy. Not sure though.