What It Does
System:stop performs one focused job in script flow and can be chained cleanly with other API steps. Starts or stops a System process.
Starts or stops a System process.
System:stop performs one focused job in script flow and can be chained cleanly with other API steps. Starts or stops a System process.
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.
This entry does not require mandatory parameters. This API is primarily side-effect driven; the important result is the device state change rather than the raw return value.
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:stop
local result = System:stop()
-- 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.
-- System:stop
local result = System:stop()
-- Use the result in your script flowlocal stepOk = true
-- System:stop
local result = System:stop()
-- Use the result in your script flow
if stepOk then
wait(200)
endlocal ok, result = pcall(function()
-- System:stop
local result = System:stop()
-- Use the result in your script flow
end)
if not ok then
print("API step failed: System:stop")
requestStop()
end-- In system flow, design steps as observe first and act second when the API can affect device state.
local function run_stop_step()
-- System:stop
local result = System:stop()
-- Use the result in your script flow
end
local ok, err = pcall(run_stop_step)
if not ok then
toast("Step failed")
print(err)
end-- System:stop
local result = System:stop()
-- Use the result in your script flow
wait(200)
print("Combined with logging and flow control")