How long does wait() wait for?

[Ozmius (Ozzy)]

How long does wait() wait for?

[AskForHeaven (Heaven)]

A horrendously inconsistent amount of time.

If you want to check the average wait time in your game accounting for the lowest lag possible, use print(wait()) in the command bar.

[prepsure (paige)]

it’s supposed to be 1/30 of a second, but can be a bit longer depending on certain conditions

[Cerulean7]

IIRC it’s a minumum of 0.02999, but as @Imp_erator said, it’s not always exactly that amount of time. You can verify that number in studio settings.

[AskForHeaven (Heaven)]

0 is actually the technical minimum, you can adjust the default wait time through the Lua settings in studio.

[Cerulean7]

I know, I meant that 0.0299 was the default number in the settings and that was the shortest number it could wait (you cant do wait(0.000001))

[TypicallyShadow (Shad)]

You should look at the post below for more information to make your wait() more accurate.

How to have a more accurate wait in a loop

EDIT: replace wait() with task.wait(). Also, raw RenderStepped faces the same issue. It’s just a matter of drift. If you have ever used wait() in a loop such as the one below: for i = 1, 240 do wait(1) end you may be surprised to learn that your wait() isn’t as trusty or accurate as you may have thought. Infact, if you attach some code to print out the time that the function took based on tick()… local startTime = tick() for i = 1, 240 do wait(1) end print(tick - startTime) Running code …

[un1ND3X (ice)]

It yields for how many seconds you tell it to wait for - the extra delay is for it to wait for an empty slot and resume the Lua thread through the queued resume task.