What It Does
wait(ms) performs one focused job in script flow and can be chained cleanly with other API steps. Creates a millisecond delay in script execution flow.
Creates a millisecond delay in script execution flow.
This section explains when to use the API, how to call it, and which structures it works best with in production flow.
wait(ms) performs one focused job in script flow and can be chained cleanly with other API steps. Creates a millisecond delay in script execution flow.
Core flow APIs are usually the backbone of larger scenarios; keep them anchored to clear checkpoints and readable variables. This API becomes most valuable in multi-step chained scenarios.
ms define the purpose of the call; preparing them in clearly named variables before execution makes production debugging easier. The safest usage pattern is to store the call result in a variable, wrap it with pcall, and pass it into later steps in a controlled way.
Using this API with logging, error handling, and next-step control produces much more professional results than calling it in isolation.
The snippet below is a starter pattern that can be applied directly in runtime flow.
wait(500)
wait(1000)From foundation to combined usage, each level is provided as a separate code block so you can copy the level you need and adapt it directly.
Shows the shortest direct way to call the API.
wait(500)
wait(1000)Wraps the base call with minimal flow control.
local stepOk = true
wait(500)
wait(1000)
if stepOk then
wait(200)
endA practical pattern for real macros with pcall, logging, and guards.
local ok, result = pcall(function()
wait(500)
wait(1000)
end)
if not ok then
print("API step failed: wait(ms)")
requestStop()
endThis level packages the API into a reusable helper with error reporting.
-- Core flow APIs are usually the backbone of larger scenarios; keep them anchored to clear checkpoints and readable variables.
local function run_wait_step()
wait(500)
wait(1000)
end
local ok, err = pcall(run_wait_step)
if not ok then
toast("Step failed")
print(err)
endCombines the API with related structures to form a more realistic workflow.
wait(500)
wait(1000)
wait(200)
print("Combined with logging and flow control")