How To Call It
Events is a global table: call its functions with a dot (Events.<method>(...)), not a colon.
Emits an event with extra values and returns how many listeners ran.
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: eventName. Any further values are passed through unchanged. 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.emit("level_done", { level = 3 })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.emit("level_done", { level = 3 })local stepOk = true
local result = Events.emit("level_done", { level = 3 })
if stepOk then
wait(200)
endlocal ok, err = pcall(function()
local result = Events.emit("level_done", { level = 3 })
end)
if not ok then
print("API step failed: Events.emit: " .. 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_emit_step()
local result = Events.emit("level_done", { level = 3 })
end
local ok, err = pcall(run_emit_step)
if not ok then
toast("Step failed")
print(err)
endlocal result = Events.emit("level_done", { level = 3 })
wait(200)
print("Combined with logging and flow control")