Why is Wait So Bad?

[RamonPIayz (ramon)]

Hello all! I was wondering why so many devs advise against using “wait()”. I don’t see a problem, so could someone please explain it to me? Thank you so much!

[wf_sh (wait)]

[nicemike40]

Most of the points in this post are still accurate:

Avoiding wait() and why

This is an adaptation of a Twitter thread I made a while ago. This is simply a better formatted and more fleshed out version. Let’s talk about wait(). Not wait(n) (although if you are using small n values to where it’d be barely distinguishable from wait(), you’re probably going to hit the same issues mentioned in this thread). We probably learned about wait() at first as the solution to “why are my infinite loops crashing me?”. It’s a super easy solution and it works! This starts a bad habit…

That post leaves out talking about task.wait, which solves some of the issues with wait. The points about event-based design are still good. More about task.wait:

Task Library - Now Available!

Hey developers, We have just enabled a brand new library that you can use in your projects. The task library allows you to talk directly with our engine’s task scheduler to manage and schedule code. It features a number of new methods as well as some improvements to existing methods. Details task.spawn Takes a thread or function and resumes it immediately through the engine’s scheduler. Additional arguments are passed to the thread or function being resumed. void task.spawn(function | thread,…