I have Always Asked that Question What is the difference between Remove and Destroy, Does Remove Actually Delete an Object from the Game, Or Destroy?
✓ ANSWER ACCEPTED
What is the Difference between "remove" and "destroy" ?
3 answers
✓ Accepted answer
EDIT: After reading the Wiki, I can now give you a better answer.
Remove() is deprecated in favor of destroy(). So if you're making new scripts, don't use remove(), it only exists for compatibility (so it doesn't wreck everyone's scripts). Remove sets the object and all of its descendants to nil.
Destroy() completely, well, destroys the object and all of its descendants. According to the wiki, destroy() "sets the Parent property to nil, locks the Parent property, disconnects all connections and calls Destroy() on all children."
So who's the winner here?
Destroy() is better. The only reason it's better is because remove() is deprecated and doesn't really remove objects.
The :Destroy() Method completely destroys the object by making it nil and locking it. :remove() just sets the object to nil. While it can still be set back. This is what I heard. Not sure if it's correct.
I'm pretty sure remove is just deprecated
This discussion is preserved as it was. New answers, comments, and votes are closed.
9 comments
But Why would ROBLOX Create 'Destroy" and 'Remove" if they have the same Purpose?
I don't know. Ask ROBLOX.
xD
Lol I found the answer. Remove() is deprecated.
The Remove method was created prior to the creation of Destroy. The Remove method did not actually delete items correctly and caused the need for a new and more efficient method that was known as Destroy.
Thanks Again! +1 Point and accepted Answer!
TheContinentofEurope & yumtaste, there is a cool thing: https://scriptinghelpers.org/questions/15544/why-doesnt-the-destroy-method-truly-destroy-an-instance.
I saw that, too. I think I put an answer there XD
You can recover a destroyed object by Cloning it and setting its parent.