Most Efficient Way to Instance

[VegetationBush (FartedWayTooHard)]

So, I’ve recently read this mind-boggling piece of a thread:

PSA: Don't use Instance.new() with parent argument

I’ve discovered a pretty bad performance issue in one of top games that has to do with Instance.new and wanted to write about this, since this is not obvious unless you know the system inside out. Tthere are several ways to create a ROBLOX object in Lua: local obj = Instance.new(‘type’); fill obj fields local obj = Instance.new(‘type’, parent); fill obj fields local obj = util.Create(‘type’, { field1 = value1, … }) If you care at all about performance, please only use the first option - I wi…

And my mind was already blank before I read the comments.

I understand what the comment section was saying, how instancing in different orders can either increase the amount of time or decrease it.

My question is that in what order is the best way to instance? The thread is kind of hard to comprehend, even though I am very experienced with Instances

[ankurbohra]

@zeuxcg

the optimal sequence is:

A. Instance.new
B. Assign properties
C. Assign Parent
D. Connect signals

Explanation

@zeuxcg

Once an object is attached to game , a lot of internal ROBLOX systems start listening to property changes on the object and updating various internal data structures for the change to take effect. These updates can involve queueing changes for replication, updating physics contact state, queueing rendering state changes etc.

It’s thus important that when you create the object, the initial object field assignment is correctly classified as “initial setup” as opposed to “changing state of the existing object” - and the differentiator for this is .Parent, or rather the object being a descendant of game .__ For this reason, .Parent assignment should go after all property assignments during the object creation.__

[Lightlimn]

Basically, set the parent of an instance AFTER changing the properties. That’s the most important thing to take away from that thread.

[ankurbohra]

Applying this to a case where I want to make a noncollidable part with a Touched connection:

local part = Instance.new("Part")
part.CanCollide = false
part.Anchored = true
part.Parent = workspace
part.Touched:Connect(touched)

[VegetationBush (FartedWayTooHard)]

thank you @ankurbohra04 @Lightlimn , I guess I was shocked by the sheer amount of things I had to change and didn’t see that(Im gonna cry)