What happens to non-parented instances, and is there a way to use them efficiently?

[i_darkest (darkest)]

Topic

What happens to created objects that are created with Instance.new() or :Clone(), but are never parented using the .Parent argument?

Questions & Theories

I’m interested to know what happens if for example, I clone a Part, and set its .Position and .Size, but never actually Parent the part.

Can I still cast rays from the .Position of the Part, even though its .Parent isn’t ever being set to anything, and not have to worry about using :Destroy() to later remove the Part in order to stop a memory leak from the buildup of parts?

Could this even slightly boost performance, and is it better than simply setting a Part’s .Transparency to 1 in order to never render it, and then using :Destroy() on it?

According to Roblox, setting a Part’s .Parent to nil causes it to be “temporarily removed”, what does that mean?

[Jackscarlett]

@i_darkest

What happens to created objects that are created with Instance.new() or :Clone() , but are never parented using the .Parent argument?

I do believe this is the same when you use Instance.new() as well, and you can manage change its properties but I don’t believe you can actually use it with other scripts (Unless if you call WaitForChild())

@i_darkest

setting a Part’s .Parent to nil causes it to be “temporarily removed” , what does that mean?

I believe it’s just a placeholder for it, not sure though

[0Luke_Skywalker0 (Luke)]

@i_darkest

According to Roblox, setting a Part’s .Parent to nil causes it to be “temporarily removed” , what does that mean?

You can later reparent it somewhere(eg workspace) as long as you have the variable that references the part. It will not be completely removed by gc

[i_darkest (darkest)]

What if I don’t want to reparent the Part anywhere, as this makes me have to call :Destroy() (this uses up more memory).

Would there be a performance boost if I just never Parented the Part, but still cast rays from it?

[0Luke_Skywalker0 (Luke)]

@i_darkest

but still cast rays from it?

wdym by that? You don’t need a part for raycasting

[i_darkest (darkest)]

Let’s say I want to grab the Part’s .Position for the [origin] argument that’s needed for raycasting. Would it boost performance if I never set the .Parent, but just used the Part to grab the .Position?

[0Luke_Skywalker0 (Luke)]

I am not sure if that will even work or not, it might. But why can’t you just have a vector3 value if you only wanted the position? Instancing a part is pretty expensive

[i_darkest (darkest)]

@0Luke_Skywalker0

I am not sure if that will even work or not, it might.

That’s why I’m asking this in the first place.

@0Luke_Skywalker0

But why can’t you just have a vector3 value if you only wanted the position? Instancing a part is pretty expensive

This would be the best way to do it, but I’m just giving a scenario.

[0Luke_Skywalker0 (Luke)]

tested in a baseplate, it works

[i_darkest (darkest)]

Thank you for testing it. I will mark you as the solution.