How To Call It
Events is a global table: call its functions with a dot (Events.<method>(...)), not a colon.
Removes a listener by id, or every listener of an event by name.
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.
Required: listenerIdOrEventName. Returns a boolean (true or false).
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 ok = Events.off("level_done")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 ok = Events.off("level_done")local stepOk = true
local ok = Events.off("level_done")
if stepOk then
wait(200)
endlocal ok, err = pcall(function()
local ok = Events.off("level_done")
end)
if not ok then
print("API step failed: Events.off: " .. 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_off_step()
local ok = Events.off("level_done")
end
local ok, err = pcall(run_off_step)
if not ok then
toast("Step failed")
print(err)
endlocal ok = Events.off("level_done")
wait(200)
print("Combined with logging and flow control")