|
| 27 Apr 2013 10:23 AM |
Why would you use either of these, I never understood the differrences really.
:Remove() :Destroy() .Parent = nil |
|
|
| Report Abuse |
|
|
|
| 27 Apr 2013 10:31 AM |
Remove sets the object's parent to nil Destroy set's the object's parent to nil and the locks the parent
|
|
|
| Report Abuse |
|
|
|
| 27 Apr 2013 10:31 AM |
.Parent = nil
I'm taking a guess that this puts it into some kind of folder where it could be used again in other instances? |
|
|
| Report Abuse |
|
|
|
| 27 Apr 2013 10:34 AM |
Using the Remove method and just setting the Parent to nil do almost the exact same thing...
Remove ->Sets parent to nil .Parent = nil ->Sets parent to nil Destroy ->Sets parent to nil and locks it.
if you use Remove or just set the parent to nil the object can be re-parented and used again. With destroy you can not do this because it locks the parent. |
|
|
| Report Abuse |
|
|
|
| 27 Apr 2013 10:37 AM |
:Remove() no longer works.... It's replaced by .Parent=nil Also, if you use Destroy, you can't call back whatever you used it on. I personally recommend using :Destroy() on clones only. |
|
|
| Report Abuse |
|
|
|
| 27 Apr 2013 10:41 AM |
| Remove works fine...It is just deprecated |
|
|
| Report Abuse |
|
|