What It Does
click(x, y) performs one focused job in script flow and can be chained cleanly with other API steps. Performs tap action on a target coordinate.
Performs tap action on a target coordinate.
click(x, y) performs one focused job in script flow and can be chained cleanly with other API steps. Performs tap action on a target coordinate.
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.
x, y 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.
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.
click(540, 960)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.
click(540, 960)local stepOk = true
click(540, 960)
if stepOk then
wait(200)
endlocal ok, result = pcall(function()
click(540, 960)
end)
if not ok then
print("API step failed: click(x, y)")
requestStop()
end-- In automation flow, chain actions with short wait() intervals and use requestStop() or controlled retry on failure paths.
local function run_click_step()
click(540, 960)
end
local ok, err = pcall(run_click_step)
if not ok then
toast("Step failed")
print(err)
endlocal target = Point(540, 960)
quickTap(target)
wait(250)
click(540, 960)
wait(250)
print("Automation chain completed")