How intensive is tick()?

[RuizuKun_Dev (Kitsune)]

You should not use spawn, delay and sometimes wait.

Using tick shouldn’t be intensive at all it just returns a float and with modern day machinery it’s more than enough to process what you are attempting.

—

@Eqicness

Using a tick Debounce is arguable more accurate and better practice in certain cases which you do not want to have unnecessary yielding and create absurd amounts of new threads.

(It’s also less punishable when mistakes are made)

---

Avoiding wait() and why

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…

Don’t use spawn / delay

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

EDIT (2020-08-12): This post gets a lot of attention. If you want to learn more, you can read this brief article. Please do not use spawn. It’s a hold-over from Roblox’s 30hz pipeline and has no guarantees about when (or if) it will begin executing the new thread. spawn is especially evil because it seems innocent at first, but once you have a lot of code that all uses spawn, you can see significant delays in execution upwards of several seconds in a resource-intensive game. Roblox throttles e…