If a part is going to be constantly used by the player but isn't always needed, it is better to create and destroy as needed or is it better to parent the part to nil until it is needed? Whichever reduces lag. And this is also being asked for about attachments.
#Best way to prevent lag?
strong goblet
nocturne rivet
you can put the part in replicade storage and clone it to the workspace and delete the clone when not needed
unreal dune
depends what the part is used for, parenting it to nil is just worse than destroy
nocturne rivet
why would you parent it to nil?
unreal dune
idk he said that
errant valve
If a part is going to be constantly used by the player but isn't always needed, ...
You can use the debris functions
errant valve
you can put the part in replicade storage and clone it to the workspace and dele...
and yeah put it into replicated storage
strong goblet
Debris is about to be depreciated iirc :v
earnest spade
and yeah put it into replicated storage
But, why debris ?!
hallow solar
Debris is about to be depreciated iirc :v
no way we are about to be using task.delay for destroying items now 💔
no more easy particle management
gg
earnest spade
no way we are about to be using task.delay for destroying items now 💔
It’s false
It’s just some methods with debris that are deprecated
Which doesn’t include AddItem
strong goblet
depends what the part is used for, parenting it to nil is just worse than destr...
Not trying to bug you days later mb gng but if it's a part that's needed for a core game mechanic, should it be parented to nil when not being used or destroyed when not being used
unreal dune
Not trying to bug you days later mb gng but if it's a part that's needed for a c...
destroyed parents it to nil anyway and does extra things