Continue script even when it's ancestor is destroyed?

[coo1ifyy]

I made a system where if the thing that is being throwed will dissappear after a few seconds and it will be destroyed, however I don’t want the script that is inside of the thing that is being throwed to end because it waits 4 seconds until it makes the player they hit get back up and everytime the script is still destroyed it would stop waiting and the ragdoll still stays.

Any ideas?

[JarodOfOrbiter]

The proper way to do it would be to put the script somewhere else. That would also give you the benefit of more reliable control over what happens with the thrown object in case something goes wrong.

[coo1ifyy]

Sorry for the bump, but is there another way I don’t want to move the script, cause I already made the script based on it’s original parent

[JarodOfOrbiter]

Not in a way that would be future-proof. You might be able to find some hacky glitch or something that will work, but you won’t have any guarantee that Roblox won’t break that functionality later. It’s worth it to redo it.

[coo1ifyy]

does having a module script handle the work do the job?

[mapleflavouredk9]

Would

Ancestor.Destroying:Connect(function()
    Ancestor.Path.To.Script.Parent = SafePlace
end)

work? It’d probably disrupt the current thread of the script but it’d continue running

Sorry I didn’t read the thread fully. You can do something like this:

Ancestor.Destroying:Connect(function()
    Ancestor.Path.To.Script.Parent = SafePlace
    
    -- make it a variable so its easily changeable, and set it to the new parent
   dependentObjectVariable = dependentObjectVariable.Parent
end)

This would keep everything relative to your new parent, omitting the need for a solution other than moving the parent