When would I have to use spawn()?

[xDeltaXen]

Hello, I know what spawn does I am pretty sure it delays the function inside of it I just do not know when I would need to do something like that.

[EmbatTheHybrid (Embat)]

spawn isn’t recommended to use as it has a wait() before it runs the given function and depending on conditions could take longer than 1/30th of a second before running your function. Use coroutines as they’re practically the same except coroutines do not have that wait()

If you want more info as to why spawn is bad, Spawn is evil by evaera and this entire thread should be good enough

Coroutines V.S. Spawn()... Which one should I use?

The title says it all… Basically I want to know in what scenarios I should use: spawn(function() -- Script end) And what scenarios I should use: local thing = coroutine.create(function() -- Script end) coroutine.resume(thing) So… When is it best to use spawn(function() and when it is best to use coroutines?

[NGC4637 (NoMore_Sugarcoating)]

i agree with the person above

instead of

spawn(function()
    --code
end)

use

coroutine.wrap(function()
    --code
end)()

or

coroutine.resume(coroutine.create(function()
    --code
end))

if you want it to behave like an improved spawn, do this:

coroutine.wrap(function()
    game:GetService("RunService").Heartbeat:Wait()
    --code
end)()

yes, game:GetService("RunService").Heartbeat:Wait() is a better alternative to wait()

to answer your question, spawn like coroutine.wrap, creates a “seperate thread”, which can be helpful in situation such as these:

while true do
    -- code to loop forever
end

spawn(function()
    --code
end) -- if this function was not spawned or wrapped as a coroutine, this will never run