What It Does
notifyPro(title, message) performs one focused job in script flow and can be chained cleanly with other API steps. Shows in-app runtime messages on screen.
Shows in-app runtime messages on screen.
notifyPro(title, message) performs one focused job in script flow and can be chained cleanly with other API steps. Shows in-app runtime messages on screen.
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.
title, message 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.
notifyPro("Status", "Step completed")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.
notifyPro("Status", "Step completed")local stepOk = true
notifyPro("Status", "Step completed")
if stepOk then
wait(200)
endlocal ok, result = pcall(function()
notifyPro("Status", "Step completed")
end)
if not ok then
print("API step failed: notifyPro(title, message)")
requestStop()
end-- Core flow APIs are usually the backbone of larger scenarios; keep them anchored to clear checkpoints and readable variables.
local function run_notifypro_step()
notifyPro("Status", "Step completed")
end
local ok, err = pcall(run_notifypro_step)
if not ok then
toast("Step failed")
print(err)
endnotifyPro("Status", "Step completed")
wait(200)
print("Combined with logging and flow control")