#benefits of Debris:AddItem?

1 messages · Page 1 of 1 (latest)

hardy fjord
#

are there any benefits of using Debris:AddItem(delay, instance) over doing something like

task.spawn(delay, function(): ()
    instance:Destroy()
end)
#

it seems very very pointless

tropic junco
#

slow

#

dont use it

oblique kestrel
#

it's more optimized

#

and added to an internal queue

oblique kestrel
#

it doesn't spawn any new threads

#

it uses timestamps within the queue and periodically checks the queue for expired objects

#

so it doesn't take as many resources as a thread would (i.e. task.spawn, task.delay)

wanton oak
#

just use task.delay debris is deprecated

tropic junco
#

if i remember task.delay is more than 10x faster than debris

oblique kestrel
oblique kestrel
oblique kestrel
native osprey
#

if you overload it

oblique kestrel
#

1000 items

#

max

#

do you know how hard it is to reach that limit

native osprey
#

wym

#

its so easy

oblique kestrel
#

then you're doing something wrong

#

😔

native osprey
oblique kestrel
#

nope

native osprey
#

not a thousand

oblique kestrel
#

nope

#

it's hardcoded 1000

#

please refer to the documentation

#

if you're going to debate this

native osprey
#

b

#

well its still slop 🤑

urban gyro
#

and debri is just cooler

wanton oak
#

but i don't need a service to just delay the instance delete

#

task.delay is faster to use and there will be no noticable difference with debris

oblique kestrel
#

This is the last time I’m commenting on this mindless debate

wanton oak
grizzled onyxBOT
#

studio** You are now Level 1! **studio