What It Does
System is the main entry point for this object family. Use it to understand the responsibility of the namespace before diving into the methods below it. System provides system/device level helper methods.
System provides system/device level helper methods.
This section explains when to use the API, how to call it, and which structures it works best with in production flow.
System is the main entry point for this object family. Use it to understand the responsibility of the namespace before diving into the methods below it. System provides system/device level helper methods.
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 entry is a namespace or helper object overview; the real flow is built with the methods listed below it.
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:currentTime
local result = System:currentTime("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:currentTime
local result = System:currentTime("value")
-- Use the result in your script flowWraps the base call with minimal flow control.
-- System:currentTime
local result = System:currentTime("value")
-- Use the result in your script flow
-- Continue with one focused method on the object.A practical pattern for real macros with pcall, logging, and guards.
-- System:currentTime
local result = System:currentTime("value")
-- Use the result in your script flow
local note = "System overview loaded"
print(note)This 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_system_step()
-- System:currentTime
local result = System:currentTime("value")
-- Use the result in your script flow
end
local ok, err = pcall(run_system_step)
if not ok then
toast("Step failed")
print(err)
endCombines the API with related structures to form a more realistic workflow.
-- System:currentTime
local result = System:currentTime("value")
-- Use the result in your script flow
wait(200)
print("Combined with logging and flow control")