While do loops Or Runservice loops...?

[XxAkaDuyxX]

What are the differences between a while wait do or a renderstepped, heartbeat, or stepped?

and what should I use these for?

[ElusiveEpix (Epix)]

Task Scheduler

Check out this page, it shows the process a frame takes.

[ElusiveEpix (Epix)]

Also, never use wait() because it is unstable and can cause issues. In almost all cases you can replace it with RunService.Stepped:Wait().

[XxAkaDuyxX]

Why can wait cause issue and become unstable?

[ElusiveEpix (Epix)]

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…

This should give you a pretty good explanation.

[flkfv]

I would use RunService loops if i’m using a wait() because it can be unstable sometimes.

Example of a RunService loop:

RunService.Heartbeat:Connect(function()
-- do stuff
end)

[HugeCoolboy2007 (omega)]

RunService doesn’t create ‘loops.’ The things you listed are events that are fired at certain points during runtime giving the illusion of a loop. Each event fires at specific points:

• Heartbeat fires after Physics are simulated (end of the frame)
• Stepped fires during physics simulation (middle of the frame)
• RenderStepped fires before physics are simulated (start of the frame)

For example, you should use RunService.RenderStepped or RunService:BindToRenderStepped() for a custom camera system because the camera needs to always be rendered first.

---

A while loop is a simple code loop that runs over and over again as long as the condition is true.
So you’d use this in the case of a round system in a game or a countdown.

All in all, you should use the RunService events for interaction with physical objects in the game and use loops for other things. But that’s just how I personally use them.

---

The developer hub has good documentation about these:

Introduction to Scripting

While do loops Or Runservice loops...?

https://developer.roblox.com/en-us/articles/task-scheduler Check out this page, it shows the process a frame takes.

[ItzMeZeus_IGotHacked (notzeussz)]

wait() isn’t that bad impact if you’re doing something small, but it’s an issue when you used it in core game components.

wait(n) doesn’t actually pause the thread for n seconds, it just make it so that it the number is as close as n, also on top of that, it’s literally pausing the entire thread and you’re just waiting until it’s over. I recommend using os.clock() to constrict your own wait().

[Necrozatus]

while loops go in a individual line but RunServices works like while loop except it runs along with other functions at the same time. If you’re going to make a game that runs a lot of loops at the same time then I would recommend you using RunServices.