What It Does
Point 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. Point handles tap, swipe, and action execution flow.
Point handles tap, swipe, and action execution flow.
This section explains when to use the API, how to call it, and which structures it works best with in production flow.
Point 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. Point handles tap, swipe, and action execution flow.
In automation flow, chain actions with short wait() intervals and use requestStop() or controlled retry on failure paths. This API becomes most valuable in touch and control-panel centric 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.
It works best together with wait(), Point, SwipeParam, ClickParam, and sometimes a Region result.
The snippet below is a starter pattern that can be applied directly in runtime flow.
-- Point:x
local result = Point:x("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.
-- Point:x
local result = Point:x("value")
-- Use the result in your script flowWraps the base call with minimal flow control.
-- Point:x
local result = Point:x("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.
-- Point:x
local result = Point:x("value")
-- Use the result in your script flow
local note = "Point overview loaded"
print(note)This level packages the API into a reusable helper with error reporting.
-- In automation flow, chain actions with short wait() intervals and use requestStop() or controlled retry on failure paths.
local function run_point_step()
-- Point:x
local result = Point:x("value")
-- Use the result in your script flow
end
local ok, err = pcall(run_point_step)
if not ok then
toast("Step failed")
print(err)
endCombines the API with related structures to form a more realistic workflow.
local target = Point(540, 960)
quickTap(target)
wait(250)
-- Point:x
local result = Point:x("value")
-- Use the result in your script flow
wait(250)
print("Automation chain completed")