What It Does
System:noti performs one focused job in script flow and can be chained cleanly with other API steps. System:noti - Macro Handler scripting API method.
System:noti - Macro Handler scripting API method.
This section explains when to use the API, how to call it, and which structures it works best with in production flow.
System:noti performs one focused job in script flow and can be chained cleanly with other API steps. System:noti - Macro Handler scripting API method.
In system flow, design steps as observe first and act second when the API can affect device state. This API becomes most valuable in multi-step chained scenarios.
value 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.
-- System:noti
local result = System:noti("value")
-- Use the result in your script flowFrom 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.
-- System:noti
local result = System:noti("value")
-- Use the result in your script flowWraps the base call with minimal flow control.
local stepOk = true
-- System:noti
local result = System:noti("value")
-- Use the result in your script flow
if stepOk then
wait(200)
endA practical pattern for real macros with pcall, logging, and guards.
local ok, result = pcall(function()
-- System:noti
local result = System:noti("value")
-- Use the result in your script flow
end)
if not ok then
print("API step failed: System:noti")
requestStop()
endThis level packages the API into a reusable helper with error reporting.
-- In system flow, design steps as observe first and act second when the API can affect device state.
local function run_noti_step()
-- System:noti
local result = System:noti("value")
-- Use the result in your script flow
end
local ok, err = pcall(run_noti_step)
if not ok then
toast("Step failed")
print(err)
endCombines the API with related structures to form a more realistic workflow.
-- System:noti
local result = System:noti("value")
-- Use the result in your script flow
wait(200)
print("Combined with logging and flow control")