Some part limit deleting parts?

Help and Feedback Scripting Support
#1

(I’m not sure if this is the place to put it, but)

I’m running into an issue where whenever a large cluster of parts are loaded in, new parts cause the oldest one to automatically delete
in other words, whenever a part is added through Instance.new(), the oldest part added through the same method (assuming theres like 1k parts loaded from the method already), is deleted.

I honestly have no idea what’s causing the parts to delete, since the only thing in the code I have that deletes them is debris service, and it usually takes a minute to delete one individual part-

#2

It could be roblox stopping parts from going over a limit to stop the game from crashing.
Other than that I wouldnt know

#3

I looked through the documentation and didn’t find anything about parts automatically deleting themselves, which I find odd.

And even when looking through some of the properties for the data models, like workspace, I couldn’t find anything about auto-deleting parts.

#4

try to disabling streamignenabled in workspace?

#5

I did, the problem still is there-

#6

Yeah its weird this has never been a problem before, do you have any plugins that could possibly be doing this?

#7

Not that I know of.
The only thing that ever deletes the objects is debris service, and that happens usually after 60 seconds.

I increased how many parts spawned per second to about 1.3k, just to test, and the last-inserted part deletes after about a second, so I’m not sure…

#8
#9

OHH that makes sense!

So I can only have 1k items set in debris service?

If that’s the case, what alternative option can I use to schedule an object’s deletion? Should I try inserting a script into each individual part that deletes it after a minute?

#10

In a normal environment, you want to let the parts delete itself to save on resources. With ~a thousand parts, deleting a couple extra wouldn’t really make a difference visually. If this is an issue for you, you’re probably doing something wrong or very inefficiently.

If you insist on doing so:

task.delay(60, part.Destroy, part)
#11

This should fix the issue, thank you!

#12

This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.