[Request] 'Destructor' conditions

[xyzzy]

something that would make handling the destruction of objects a little easier would be a special "destructor" condition (as "Destroyed" or similar under an object's conditions menu)

it would be a triggered event, of course, which is called when an object is destroyed; not just from the Destroy action, but also by anything else that destroys an object, such as "destroy object if too far from frame". i'm not sure if you can even check for when the latter happens and handle objects accordingly, unless you code the whole "far from frame" thing yourself

there might also be an expression along the lines of destructor("Object"), which returns a certain value representing exactly what called the destructor. some ideas i had in mind for this value:

0 - destructor hasn't been called
1 - destructor called by Destroy action
2 - destructor called by "too far from frame"
3 - destructor called due to Next Frame/Restart Frame/Jump To, etc
4, 5, etc - other ones i have missed

[MechatheSlag]

a brilliant idea

[Stephen]

I agree.

stephen1980

[Jaffob]

So do I
For the expression, there should also be a number for "Destroyed by an extension".

[Retriever2]

Agreed, there's numerous ways an object might die and it would be useful for any user-side cleanup.