Stop A Thread When A Part Is Deleted

[PersonifiedPizza]

Join the club

Instance.Destroyed Event

The Instance.Destroyed event would fire once after all other events have disconnected, then it will disconnect itself. It would fire when the Instance can no longer be parented to or interact with the game world. It would allow for ‘extensions’ of existing Instances without messy or inefficient cleanup code. It is very common that I have an ‘extended’ instance that needs to terminate some running code when the actual instance it uses in the hierarchy is deleted. Currently there is no signal for…

---

On a more serious note, using Instance.AncestoryChanged and then checking if the new parent is nil works pretty well. It’s different than the object actually being “destroyed” but it’s usually about the same thing.

Are you using coroutines or roblox events/connections? If you’re using connections, just store them in a table then loop though that table disconnecting them when the parent changes to nil.

Let me know if you’ve got any questions/or if this doesn’t work for you because Roblox still hasn’t added a Destroyed event like Unity

---

@DataSigh

Parent the connection to the part and when the part gets destroyed the connection dies too

Using events of the Part also works. Note this might not be possible in all cases though, like when you need RunService events.