Property to check if an instance is destroyed or not

[x_o]

As a Roblox developer, it is currently too hard to …
Tell if an arbitrary instance is destroyed or not, simply listening to instance. Destroying is not enough. I do not want to have to cache the destroyed status of an arbitrary amount of objects, that defeats the purpose of destroying them.

If Roblox is able to address this issue, it would improve my development experience because …
it will be easier to migrate to the new destroy replication behavior, and I will not have to rewrite as much legacy code.

Destroy() Can Now Replicate to Clients

Greetings Developers, Coming soon, calls to :Destroy() on the server will replicate to clients. What exactly does this mean? TL;DR: Try changing the ReplicateInstanceDestroySetting under Workspace to Enabled for your experiences and see how they are affected, as we plan to enable it by default in the future. Current Behavior You may have noticed that currently when you call :Destroy() on an Instance, that Instance will be destroyed, meaning that it and all its descendants: Will have their …

[focasds]

I totally want this feature and here is a post that really supports it which I made some time ago:

Upcoming Changes to Destroy()

First of all, I wanted to say that I am happy with this change as I probably had many leaks before this was put in place. Now, I wanted to ask a quick question. Is it so hard for you guys to add a IsDestroyed() function for each instance that returns a boolean value indicating if the Instance has been destroyed or even a property called Destroyed for us to check if the Instance has been destroyed? I am honestly tired of checking if is parented to nil or even if is a descendant of…

[VitalWinter]

I check by indexing the parent.

if part.Parent then --not destroyed

This works in every case I’ve found, except for when objects are intentionally parented to nil (almost never), or not fully initialized yet (damn you player.Character!).

Are there other cases where this property would make sense?

[colbert2677 (Dreamseeker)]

It’s exactly because a nil parent doesn’t imply destruction that it doesn’t “work”. It’s not a safe or accurate strategy of determining when an instance is destroyed especially in complex cases where you have a lot of instance management going on. Developers shouldn’t have to guess or use hacks to differentiate a nil-parented instance from a destroyed one be it for compatibility or a genuine use case that shows up.