#benefits of Debris:AddItem?
1 messages · Page 1 of 1 (latest)
debris:additem is handled by roblox in the c backend
it's more optimized
and added to an internal queue
cleaner code
another thing to note
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)
just use task.delay debris is deprecated
if i remember task.delay is more than 10x faster than debris
debris is not deprecated and again, it's directly talking with the engine
false, task.delay spawns a luau virtual thread, whereas debris:additem relies on roblox engine level systems
idk where you heard that it was deprecated 💔💔
debris starts removing items before their destruction delay is up
if you overload it
also its more like hundreds
nope
not a thousand
nope
it's hardcoded 1000
please refer to the documentation
if you're going to debate this
and debri is just cooler
Idk someone said that on devforum 2 yrs ago lol
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
Again, it is not faster, and there is an incredibly noticeable difference in performance between debris and task, since virtual threads are extremely expensive.
This is the last time I’m commenting on this mindless debate
How are vts "extremely expensive" ? They're not ??
** You are now Level 1! **