How To Call It
Events is a global table: call its functions with a dot (Events.<method>(...)), not a colon.
Clears the listeners of one event, or of every event when no name is given.
Documented for app version 1.0.51Updated:
Events is a global table: call its functions with a dot (Events.<method>(...)), not a colon.
Core flow APIs are usually the backbone of larger scenarios; keep them anchored to clear checkpoints and readable variables.
Optional: eventName (omit to pass nil and use the runtime default). Returns a number.
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.
local result = Events.clear()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.
local result = Events.clear()local stepOk = true
local result = Events.clear()
if stepOk then
wait(200)
endlocal ok, err = pcall(function()
local result = Events.clear()
end)
if not ok then
print("API step failed: Events.clear: " .. tostring(err))
requestStop()
end-- Core flow APIs are usually the backbone of larger scenarios; keep them anchored to clear checkpoints and readable variables.
local function run_clear_step()
local result = Events.clear()
end
local ok, err = pcall(run_clear_step)
if not ok then
toast("Step failed")
print(err)
endlocal result = Events.clear()
wait(200)
print("Combined with logging and flow control")