What is the difference between m:Destroy() and m:Remove()?
Should I use one over the other depending on the situation or does it not matter? Thanks.
2
0
4 answers
This is a common question many users have when scripting.
Remove is deprecated [meaning it's highly discouraged from use], while Destroy is the better method to use to get rid of an object.
Remove
Let's look at two scripts:
1 | s = Instance.new("Part",workspace) |
2 | s.Parent = nil |
and
1 | s = Instance.new("Part",workspace) |
2 | s:Remove() |
What you just saw above does the EXACT same thing. Remove merely sets the parent of the object to nil.
To prove this, we can do this:
1 | s = Instance.new("Part",workspace) |
2 | s:Remove() |
3 | s.Parent = workspace |
In the code example above, the part, although removed, is able to make its way to Workspace since all we did was just re-declare the parent and it came back.
Destroy
Destroy is different in a way:
1 | s = Instance.new("Part",workspace) |
2 | s:Destroy() |
Sets the Parent property to nil, locks the Parent property, disconnects all connections and calls Destroy() on all children, thus why Roblox suggests we use Destroy over Remove
Let's prove this:
1 | s = Instance.new("Part",workspace) |
2 | s:Destroy() |
3 | s.Parent = workspace |
With the following code above, the part will never return.
Links
Destroy: http://wiki.roblox.com/index.php?title=API:Class/Instance/Destroy Remove: http://wiki.roblox.com/index.php?title=API:Class/Instance/Remove
0
0
0
0
0
1
0
Remove is deprecated the other one isn't.
Remove only changes the parent to nil. So remove doesn't actually remove the object. So you can do this.
1 | local part = workspace.Part |
2 |
3 | part:remove() |
4 | wait(3) |
5 | part.Parent = workspace --The part will disappear for 3 seconds then come back. |
This is the same as doing this
1 | local part = workspace.Part |
2 |
3 | part.Parent = nil --Parent is nil, remove changes the parent of an object to nil |
4 | wait(3) |
5 | part.Parent = workspace --The part will disappear for 3 seconds then come back. |
Destroy actually destroys the object. If it's destroyed, it's done. You cannot bring it back.
1 | local part = workspace.Part |
2 |
3 | part:Destroy() |
4 | wait(3) |
5 | part.Parent = workspace --The part will disappear forever! and the script will also error since part does not exist anymore. |
Hope this helps!
The different between Destroy and Remove is that;
Destroy: Destroy removes the Child/Target, then will lock the Child and it's Descendants, preventing it from being used again.
Remove: Remove only reverts the Child's Parent property to nil, without locking it or it's Descendants, allowing the user to use the Model/Child again, however, due to you being able to set a Child's Parent manually without remove [Is what I'm guessing],
Removehas become Deprecated.
Hope this helped!
All I know is that, both works the same.
1