You should use the new methods. Here’s a quick cheat-sheet:
| Before | Now | Now (Alt.) |
|---|---|---|
wait() |
task.wait() |
|
wait(n) |
task.wait(n) |
|
spawn(f) |
task.defer(f) |
task.delay(0, f) |
delay(n, f) |
task.delay(n, f) |
|
spawn(function () f(uv1, ...) end) |
task.defer(f, uv1, ...) |
task.delay(0, f, uv1, ...) |
delay(n, function () f(uv1, ...) end) |
task.delay(n, f, uv1, ...) |
I forgot, does this do any performance increase with delay and spawn when switiching to task.delay/task.defer?
Of course.
The new task library uses an improved polling system.
I had a question.
Is wait() really deprecated?
Since then, I’ll change all my waits’ now. Else I’ll replace them later with task.wait
It’s not deprecated yet so that people have some time to naturally migrate off of it before being annoyed by warnings in the script editor, but it will be at some point.
Well it does make sense, since wait is the only function that is used the most, so I guess it’s good to give developers some time. Thanks for the reply!
I think there’s a small bug with the autocomplete, as the script editor says task.wait() returns void (nil)
The DevHub says it returns a number:
Is that intentional?
So does this mean that my analogy is correct? When .defer was released I went by saying “It basically schedules threads to be resumed once there’s no other threads running anymore.” Would that mean that this analogy isn’t actually that wrong?
Almost, but not quite. A deferred thread is resumed when all threads that were scheduled or running when it was deferred have yielded or terminated.
I’ve heard before that Debris uses the older ‘deprecated’ wait/delay, anything I ask forward is dependant if that’s the case, if that’s the case, any plan to switch Debris to use task.wait/delay instead? Is that something that you guys think could break some code? If so, would Debris get possibly deprecated in the near future?
you can do this if you want:
local function Debris(waitTime, Instance)
task.delay(waitTime, function()
Instance:Destroy()
end)
end
I know I can, that’s why I would expect Debris to be deprecated since it just does that anyway.
I always thought Debris was weird.
Also, even better version of this:
You could add some asserting into this, but this works just fine.
local function DestroyInstanceIn(waitTime, instance)
assert(
typeof(waitTime) == 'number',
"WaitTime must be a number!"
)
assert(
typeof(instance) == 'Instance',
"Must be an instance"
)
task.delay(waitTime, instance.Destroy, instance)
end
I didnt do that because it might error like it does if you try this on remote events/functions
task.spawn(RemoteEvent.Fire, Params)
Yeah, because you’re supposed to pass the RemoteEvent object as the 2nd argument before Params:
task.spawn(RemoteEvent.Fire, RemoteEvent, Params)
Has anyone been having trouble using task.spawn in real servers? I don’t mean testing in studio, I mean in real games. I tried switching to using task.spawn not too long after the task library became available and it had what felt like a 40% chance of just not working in a real game in server scripts.
I’d like to know if these issues have been ironed out since this update was last pushed.
Is this library still in an early release stage?
If not, it’d be awesome to get it on the wiki with a better explanation of the more in-depth diagrams that we saw in the beta post. I couldn’t seem to find it via the search function on the site.
Edit: Forgot to mention how much I’m loving using this task library. Finger-saver, no more RunService.Heartbeat:Wait(), improved functionality (and efficiency), and a removal of unnecessary RunService GetService variables (for the sake of continuity).
does this help out?
Yes! Thank you very much. I think the page could still use the explanation from the diagrams when the task library was in its beta stage.
I guess it’s not a page that’s easily indexed. 
had to go on google to find it, came up as the second result
I wonder when it will become searchable
Previously, I think it actually did work even after script deletion, but someone filed it under engine bugs somewhere, so it was fixed.
Edit: found it (I think) Task.wait() does not respect script.Disabled and always resumes - #6 by ZeezyRed
