Command video guide
SmartTap
SmartTap recognizes image states and decides whether to tap when the same command is revisited. This Overview explains every control without Test or Play. The Asset Creation tab reuses the shared cropping guide.
A working command needs a search Area and at least two enabled positive assets, with up to ten rows. This tour inspects one sample row rather than saving a runnable setup. Choose distinct states, preserve their intended order, and keep only useful, stable pixels. SmartTap accepts the first approved match in saved enabled-row order; it does not choose the globally highest score.
Each row has Enabled, Label and optional Confidence. Global Confidence is a whole percentage from 1 to 100, default 90. Higher values are stricter. A positive row value overrides global confidence; blank or zero uses global confidence. Do not enter a fraction or percent sign. Avoid semi-transparent edge pixels that change with the background.
Center taps the matched image center. Set Coordinates taps a fixed X/Y location, entered literally or supplied by earlier Integer variables. The coordinate outputs still describe the matched image, not that fixed tap location.
All four triggers accept the first approved match of a run. Switch Only and Every Change tap again when the approved asset changes; seeing the same approved asset repeatedly does not retrigger them. First Seen taps only for the first approved match. Every Match taps for every approved match, including repeated recognition of the same asset. State belongs to that SmartTap command and resets for a new run; use a Loop when repeated checks are needed. A failed search does not invent a matched state.
Set Variables offers optional destinations in This Script Only or Script Thread scope. Boolean b1 is True only when that execution successfully dispatches a tap, otherwise False. Integer x1/y1 store the approved matched center, even when trigger policy suppresses the tap; without an approved match those coordinates remain unchanged.
Negative Assets can reject positive candidates when an unwanted image matches nearby; up to ten can be selected. They are mentioned here without a negative-asset demonstration. Complete the active fields before using header Test or saving OK. This tour closes its unsaved draft.
Watch the walkthrough
Step-by-step guide
Step 01 SmartTap recognizes images and decides whether to tap based on the last approved match. It is useful when a script revisits the same visual controls and should react to a new state instead of tapping blindly. This Overview explains the options without Test or Play.
Step 02 Create a blank script for this tour. We will inspect one SmartTap draft, then discard its settings. This keeps the option tour separate from a runnable demonstration.
Step 03 Give the new script a clear name and open its editor. Existing scripts stay unchanged.
Step 04 Open Advanced and drag SmartTap into the live script. Then open the placed command. Always drag a new command from the palette; opening its saved row is a separate action.
Step 05 Use In chooses where the optional output variables will be saved. This Script Only keeps them local. Use Script Thread when other scripts in the same thread need those results, and keep later readers in that same scope.
Step 06 Area limits where SmartTap looks for its images. The text opens numeric coordinates; the icon opens a visual selector. Drag the corners around the relevant part of the screen, then accept. A smaller useful area can reduce matching work.
Step 07 Asset selections are the visual states SmartTap can recognize. A working command needs at least two enabled assets, with up to ten rows. We will inspect one sample row here. The shared Asset Creation tab explains how to prepare and crop reusable images.
Step 08 Each row shows its asset name, an Enabled switch, a Label and an optional Confidence. Enabled decides whether that row participates. The label makes a recognized state easier to identify. We will call this sample Icon.
Step 09 Global Confidence is a whole percentage from one to one hundred. Higher values are stricter; lower values allow more color variation. Ninety is the default. This is image similarity, not a probability that the script is correct.
Step 10 A positive row Confidence overrides the global value. One hundred requests an exact match. Blank or zero uses the global setting instead. These controls take whole percentages, without a percent sign. We will show one hundred, then return this row to zero.
Step 11 Asset order matters. SmartTap checks enabled rows in their saved order and accepts the first approved match. Distinct, tightly cropped states make that choice easier to predict. Avoid unstable, semi-transparent edge pixels, and use only the pixels needed for reliable recognition.
Step 12 Tap Target Center taps the center of the matched image. Set Coordinates taps a fixed location instead. The target icon lets us choose a safe empty spot; its X and Y fields can also use earlier Integer variables.
Step 13 Trigger chooses when a recognized image should cause a tap. These choices matter when the same SmartTap command is visited again, such as inside a Loop. Its remembered state belongs to that command and resets for a new run.
Step 14 Switch Only accepts the first approved match. On later visits, it taps again only when a different approved asset is recognized. Seeing the same asset repeatedly does not cause repeated taps.
Step 15 First Seen taps for the first approved match in that run, then suppresses further taps from this command. Choose it when a repeated check should act only once.
Step 16 Every Change also accepts the first approved match and responds when the approved asset changes. Repeating the same matched asset does not trigger another tap. An unsuccessful image search does not invent a new matched state.
Step 17 Every Match taps on every visit that finds an approved image, even when it is the same asset as before. Use this when each successful check should act again.
Step 18 Set Variables exposes optional result destinations. Boolean b1 is True only when this execution successfully sends a tap; otherwise it is False. This is a tap result, not just an image-found flag. The full variable name includes its number.
Step 19 The X and Y outputs store the matched image center. We use Integer variables x1 and y1. These coordinates describe the match even when Set Coordinates sends the tap somewhere else. Without an approved match, the coordinate destinations remain unchanged.
Step 20 Negative Assets can reject an otherwise matching candidate when an unwanted image is found near it. Up to ten can be selected. We leave this option off here; the shared Asset Creation video covers preparing image assets.
Step 21 The header Test checks the current draft, so use it deliberately after the active settings are complete. This option tour does not run Test or Play. One inspected row is not a runnable configuration: a real SmartTap command still needs at least two enabled assets.
Step 22 Close the modal to discard this tour draft. For a real script, finish the assets, area and active target, then save with OK. Test with your own images, and check the tap results during normal script playback.
Create the image asset once, then select it in this command. This is the same shared video used by the other image-matching guides.
Asset Creation
Every Match taps on every approved match, including repeated matches of the same image.
The new guide script has supporting String, Loop, Standard PromptMe and End Loop commands prepared. String variable s1 holds Next check; PromptMe uses s1 as its header, with a Continue button writing Boolean b1. SmartTap is manually dragged from the palette and moved before PromptMe inside the three-repeat Loop.
The controlled example shows image A, image A again, then image B. The actual tap-counter sequence is 1, 2, 3. Only a real tap on the dark target increments it. PromptMe waits below the image so the target remains visible. Press Continue after the third check for natural completion.
The assets are genuine portions of the ScriptTap icon. Use the shared Asset Creation tab for preparing images, and Overview for asset ordering, confidence, output variables, fixed targets and negative assets. If Android asks, allow screen capture.
Every Match
Step-by-step guide
Step 01 Every Match makes SmartTap tap on every approved image match, even when the same image stays on screen. A visible counter will show each real tap in this three-check example.
Step 02 This new guide script has a short supporting sequence prepared. A String stores Next check in s1. Loop repeats three times, with no delay or concurrent play. Standard Prompt Me uses s1 for its header and a Continue button with Boolean output b1. The prompt pauses after each check, and is positioned below the image.
Step 03 Drag SmartTap from the Advanced palette into the script. Move its row inside Loop, before Prompt Me, then open the placed command. Only SmartTap will perform image matching; the other commands make its result easy to inspect.
Step 04 Use Area to select a small region around the target image. Keep the page controls and counter outside the region, then accept the selection. If Android asks, allow screen capture.
Step 05 Choose ScriptTap Outline and ScriptTap Branch, two saved portions of the ScriptTap icon. For preparing your own images, refer to the shared Asset Creation video. We can reuse these assets instead of creating them again.
Step 06 Keep both assets enabled and the global confidence at ninety percent. A blank or zero row confidence uses the global value. SmartTap checks enabled rows in their saved order and uses the first approved match.
Step 07 Scroll to the tap and trigger controls. Keep Tap Target at Center and choose Every Match. Each execution of this command can tap another approved match, whether the selected image changed or not.
Step 08 Save with OK. Optional output variables and Negative Assets stay off here; the Overview explains their purpose.
Step 09 The complete sequence is String, Loop, SmartTap, Prompt Me, and End Loop. SmartTap runs once in each repetition. Prompt Me then waits for Continue before the loop can make its next check.
Step 10 Close the editor and reset the example page to image A and zero taps. Only a real tap on the dark target changes the counter. The separate control changes the displayed image.
Step 11 When the script is complete, simply use the Play button in the main overlay.
Step 12 SmartTap finds image A and taps its center. The counter becomes one. Prompt Me pauses below the target so the image and counter remain unobstructed.
Step 13 Press Continue without changing image A. Every Match approves the same asset again and the counter becomes two. This mode does not require a visual change.
Step 14 While Prompt Me waits, switch the page to image B. The counter stays at two because changing this control is not a tap on the target.
Step 15 Continue. The third check finds the second asset, and the counter becomes three. Both the unchanged image and a different approved image have produced another tap.
Step 16 Continue once more to leave the final pause. The three checks are complete and the script stops automatically. Use the other trigger guides when repeated matches should not always cause another tap.
First Seen taps only the first approved match for this command in each run, not the first match of every different asset.
Reuse the five-command example from Every Match. Change only the Trigger mode; the two assets, small search area, ninety-percent confidence and Center target remain unchanged.
The controlled example shows image A, image A again, then image B. The actual tap-counter sequence is 1, 1, 1. Only a real tap on the dark target increments it. PromptMe waits below the image so the target remains visible. Press Continue after the third check for natural completion.
The assets are genuine portions of the ScriptTap icon. Use the shared Asset Creation tab for preparing images, and Overview for asset ordering, confidence, output variables, fixed targets and negative assets. If Android asks, allow screen capture.
First Seen
Step-by-step guide
Step 01 First Seen makes SmartTap tap only on the first approved match for this command in a script run. Later matches do not produce another tap, even when a different selected asset appears. This guide reuses the five-command example prepared in Every Match.
Step 02 Open the placed SmartTap command and scroll to Trigger. The two assets, search area, confidence, and centered tap target stay unchanged.
Step 03 Choose First Seen and save with OK. This changes when an approved match may produce a tap; it does not change the images being searched.
Step 04 Close the editor and reset the example page to image A and zero taps. Loop repeats the same SmartTap command three times, with Prompt Me pausing below the target between checks.
Step 05 When the script is complete, simply use the Play button in the main overlay.
Step 06 The first check finds image A, and the counter becomes one. Prompt Me holds the script after that check so the outcome remains visible.
Step 07 Continue with image A unchanged. The counter remains one: First Seen has already used this command’s first approved match.
Step 08 While Prompt Me waits, switch the page to image B. Changing this separate control does not itself add a target tap.
Step 09 Continue with image B. The counter still remains one. First Seen means the first approved match for this command in the run, not the first sighting of every different asset.
Step 10 Continue to finish the final pause. The finite loop ends and the script stops automatically. A new run starts with fresh SmartTap memory.
Switch Only taps on the first approved match, then again only when the approved asset changes.
Reuse the five-command example from Every Match. Change only the Trigger mode; the two assets, small search area, ninety-percent confidence and Center target remain unchanged.
The controlled example shows image A, image A again, then image B. The actual tap-counter sequence is 1, 1, 2. Only a real tap on the dark target increments it. PromptMe waits below the image so the target remains visible. Press Continue after the third check for natural completion.
Switch Only and Every Change produce the same result in this A/A/B example. Every trigger accepts its first approved match; no invented fallback image or tap is used.
The assets are genuine portions of the ScriptTap icon. Use the shared Asset Creation tab for preparing images, and Overview for asset ordering, confidence, output variables, fixed targets and negative assets. If Android asks, allow screen capture.
Switch Only
Step-by-step guide
Step 01 Switch Only makes SmartTap tap on the first approved match, then again only when the approved asset changes. It avoids repeatedly tapping an unchanged image. This guide reuses the five-command example prepared in Every Match.
Step 02 Open the placed SmartTap command and scroll to Trigger. The two assets, search area, confidence, and centered tap target stay unchanged.
Step 03 Choose Switch Only and save with OK. This changes when an approved match may produce a tap; it does not change the images being searched.
Step 04 Close the editor and reset the example page to image A and zero taps. Loop repeats the same SmartTap command three times, with Prompt Me pausing below the target between checks.
Step 05 When the script is complete, simply use the Play button in the main overlay.
Step 06 The first check finds image A, and the counter becomes one. Prompt Me holds the script after that check so the outcome remains visible.
Step 07 Continue with image A unchanged. The counter remains one. Switch Only remembers the approved asset and does not tap it again merely because the command repeats.
Step 08 While Prompt Me waits, switch the page to image B. Changing this separate control does not itself add a target tap.
Step 09 Continue with image B. The approved asset has changed, so Switch Only taps again and the counter becomes two. In this A, A, B example, Every Change produces the same result.
Step 10 Continue to finish the final pause. The finite loop ends and the script stops automatically. A new run starts with fresh SmartTap memory.
Every Change taps on the first approved match, then again only when the approved asset changes.
Reuse the five-command example from Every Match. Change only the Trigger mode; the two assets, small search area, ninety-percent confidence and Center target remain unchanged.
The controlled example shows image A, image A again, then image B. The actual tap-counter sequence is 1, 1, 2. Only a real tap on the dark target increments it. PromptMe waits below the image so the target remains visible. Press Continue after the third check for natural completion.
Switch Only and Every Change produce the same result in this A/A/B example. Every trigger accepts its first approved match; no invented fallback image or tap is used.
The assets are genuine portions of the ScriptTap icon. Use the shared Asset Creation tab for preparing images, and Overview for asset ordering, confidence, output variables, fixed targets and negative assets. If Android asks, allow screen capture.
Every Change
Step-by-step guide
Step 01 Every Change makes SmartTap tap on the first approved match, then again when the approved asset changes. Repeating the same approved asset does not cause another tap. This guide reuses the five-command example prepared in Every Match.
Step 02 Open the placed SmartTap command and scroll to Trigger. The two assets, search area, confidence, and centered tap target stay unchanged.
Step 03 Choose Every Change and save with OK. This changes when an approved match may produce a tap; it does not change the images being searched.
Step 04 Close the editor and reset the example page to image A and zero taps. Loop repeats the same SmartTap command three times, with Prompt Me pausing below the target between checks.
Step 05 When the script is complete, simply use the Play button in the main overlay.
Step 06 The first check finds image A, and the counter becomes one. Prompt Me holds the script after that check so the outcome remains visible.
Step 07 Continue with image A unchanged. The counter remains one because the approved asset has not changed.
Step 08 While Prompt Me waits, switch the page to image B. Changing this separate control does not itself add a target tap.
Step 09 Continue with image B. This different approved asset produces another tap and the counter becomes two. For this A, A, B example, Every Change and Switch Only behave the same.
Step 10 Continue to finish the final pause. The finite loop ends and the script stops automatically. A new run starts with fresh SmartTap memory.