No-Code Workspace — Block Reference
Choose a block from the selector below or, on desktop, from the left rail. Every block includes purpose, parameters, common scenarios, cautions, and an in-app screenshot.
Image (IMAGE)
SearchBlock Preview
Captured from the in-app Visual Builder block card using the screenshot locale matched to the selected website language.
What Does It Do?
Searches for a specific template inside the selected scan region. Goes to TRUE if a match is found, FALSE otherwise. Scanning runs with a single selected engine; there is no automatic full-screen fallback.
Pro note: region strategy matters
IMAGE is not only about choosing one template. In the builder, multiple regions and per-region excludes are a core part of making the flow stable.
Shared Mechanics for Search Blocks
IMAGE, TEXT, COLOR, and OCR-related blocks can define multiple search regions. Each region can also carry its own exclude region to remove noisy areas and reduce false matches.
You can now assign a sticky anchor to each search region. This brings Region.sticky into the no-code surface so the region can stay aligned to anchors such as top_left, bottom_right, or center when screen geometry changes.
Search timeout defines one search window. Retry on true, retry on false, and waitUntilFound turn a block into a one-shot check or controlled polling step. scanRateHz controls attempts per second.
mScore, scale, and scan engine choices matter across themes, display sizes, and rendering differences. Smaller regions plus the right engine dramatically improve builder stability.
When to Use?
Use when you want to check if any screen element is visible:
- Checking if a button appeared
- Detecting if a notification or alert opened
- Waiting for a loading screen to finish
- Verifying navigation to a specific page
- Checking if any icon or visual element exists
How to Use?
1. Add "Image (IMAGE)" block
2. Capture the template with "Select Template"
3. SCAN REGION: Always constrain the search area (smaller = faster)
4. SCAN ENGINE: quick_image / balanced_image / precision_image / color_aware_image / small_object_image
5. MATCH RATIO (mScore): lower = flexible, higher = stricter
6. SCALE: adjust for device differences
7. SEARCH TIMEOUT: 0 = single attempt
8. If retry is needed, set SCAN RATE (Hz): attempts per second
9. Configure TRUE/FALSE branches
Parameters
Image to search for. Capture from screen or select from gallery
Screen area to search [x, y, width, height]. Smaller = faster
0.10-0.99 range. 0.80 default. Low = flexible, high = exact. Slider + manual + variable supported
1.0 = original. For different screen resolutions. Slider + manual + variable supported
quick_image / balanced_image / precision_image / color_aware_image / small_object_image
0 = single try, 5000 = try for 5sec. Slider 0-30000ms + variable supported
Attempts per second in retry mode. 1-30 Hz
Wait before searching. Slider 0-5000ms + variable supported
Wait after searching. Slider 0-5000ms + variable supported
Retry on true / Retry on false / Infinite / Wait until found
| Parameter | Description |
|---|---|
| Template | Image to search for. Capture from screen or select from gallery |
| Scan Region | Screen area to search [x, y, width, height]. Smaller = faster |
| Match Ratio (mScore) | 0.10-0.99 range. 0.80 default. Low = flexible, high = exact. Slider + manual + variable supported |
| Scale | 1.0 = original. For different screen resolutions. Slider + manual + variable supported |
| Scan Engine | quick_image / balanced_image / precision_image / color_aware_image / small_object_image |
| Search Timeout | 0 = single try, 5000 = try for 5sec. Slider 0-30000ms + variable supported |
| Scan Rate (Hz) | Attempts per second in retry mode. 1-30 Hz |
| Wait Before (ms) | Wait before searching. Slider 0-5000ms + variable supported |
| Wait After (ms) | Wait after searching. Slider 0-5000ms + variable supported |
| Retry Modes | Retry on true / Retry on false / Infinite / Wait until found |
Example Usage
Scenario 1: Auto-click "OK" button when it appears
1. Add IMAGE → save "OK" button as template
2. Scan region: Area where button can appear
3. Add CLICK to TRUE → enable "Click on match"
4. Retry: "Retry on false" (waits until button appears)
Scenario 2: Wait for loading screen to finish
1. IMAGE → save loading icon as template
2. Retry: "Retry on true" (waits until icon disappears)
3. In FALSE: Loading done, proceed to next step
Combinations / Used With
MOST COMMON COMBINATIONS:
- IMAGE + CLICK: Find something and click it
- IMAGE + WAIT: Wait for something to appear/disappear
- IMAGE + SWIPE: Swipe when something is found
- IMAGE + IMAGE: Multiple visual checks in sequence
- IMAGE + COMPARE: Make decisions based on found position
- IMAGE + LOG: Log search results (for debugging)
Tip
Searches for a template image on screen
Warnings / Cautions
WARNING:
- Starting macro without selecting template means block always goes to FALSE
- Do not leave scan region as full screen — slow and may cause false matches
- Do not capture templates from areas with changing backgrounds
- Do not lower match ratio below 0.50
- Adjust Scale when using on devices with different resolution
Shared Controls for This Block Family
The guidance below is not identical for every block. It summarizes the professional controls that most often repeat in the selected block family.
Keep the search close to the target. Smaller regions are faster and more stable.
Exclude static noise, badges, animations, or reflective areas to reduce false matches.
Timeout and scan rate define whether the block acts as a single check or controlled polling step.
mScore, scale, and engine choice must be tuned together for theme, resolution, and rendering differences.
Passing _lastMatch, _lastOcrText, and related result values into later blocks keeps the flow readable.
Builder vs Lua Boundary
TOUCH and TOUCH_BREAK cover recipe-style touch flows. Raw pointer choreography such as Touch.down, Touch.move, Touch.up, Touch.dispatch, Touch.reset, Touch.breakAll, and Touch.releaseAfter is not exposed as a first-class builder block.
Touch.downTouch.moveTouch.upTouch.dispatchTouch.resetTouch.breakAllTouch.releaseAfterThe DIALOG block and dialog designer cover a bounded, supportable field set in the builder: info text, text input, checkbox, radio group, dropdown, image picker, tab group, and recorder picker. Freer Setting.builder composition, multi-step wizard flows, and mixed HUD/dialog choreography still do not map 1:1 into the builder.
Setting.builderDialogHudTextViewThe HTTP_REQUEST block already covers one bounded request with method, header lines, body, content type, and timeout. Freer query composition with Request.setParameter, Request.setHeader, Request.setBody, Request.setContentType, chaining multiple request objects, and lower-level client flows still do not map 1:1 into the builder.
Request.setParameterRequest.setHeaderRequest.setBodyRequest.setContentTypeRequest()TRY_CATCHCUSTOM_CODEGeneral-purpose helpers such as Map, Array, JSON, Regex, and Metrics are broader than the builder recipe model. These surfaces remain on the coded runtime side instead of becoming first-class builder blocks.
MapArrayJSONRegexMetricsDebug Mode and Breakpoints
Each block card now exposes an independent breakpoint toggle. When enabled, the breakpoint preference is stored with the block.
Breakpoints are only emitted into runtime code when Debug Mode is enabled from Visual Builder settings. When Debug Mode is off, breakpoints stay saved but do not pause execution.
Use ASSERT for fail-fast validation, and use breakpoints for step-by-step tracing and controlled pauses in the same flow.
Variable Scope
Variables defined with SET_VARIABLE are accessible throughout the macro (global scope). All blocks can read/write the same variable.
However, a variable defined inside a GROUP will be 'nil' (undefined) until the GROUP executes. Blocks outside the GROUP using this variable may produce unexpected results.
FOR_EACH loop variables (item and index) only carry valid values inside the loop body. Outside the loop they retain the last iteration's value, but this should not be relied upon.
TRY_CATCH error variable is only valid within the catch block. If the try block succeeds, the catch branch is not entered and the error variable remains undefined.
TIP: Before using a variable inside a GROUP, assign a default value with SET_VARIABLE outside the GROUP. This way the variable won't be nil even if the GROUP hasn't run.
Inline Expressions
You can embed variable values and calculations into text fields using {{ expression }} syntax. Expressions inside double curly braces are evaluated as Lua code and the result is inserted into the text.
{{ expression }}Skor: {{ score + 1 }} → "Skor: " .. tostring(score + 1){{ name }} kazandi! → tostring(name) .. " kazandi!"X:{{ x }} Y:{{ y }} → "X:" .. tostring(x) .. " Y:" .. tostring(y)Expressions are checked by the sandbox policy. Security-sensitive calls like loadstring, require, debug are automatically blocked.
General Tips
Keep scan regions as small as possible — improves speed, reduces false matches.
Always add an exit condition when using infinite loops (BREAK, timeout, or conditional exit).
Use network operations and error-prone steps inside TRY_CATCH.
If you need global error handling, use the Error Handler (ERROR_HANDLER) block as a singleton in the project.
Small coordinate offsets (CLICK/SWIPE) improve tap accuracy across different DPI and screen scales.
Customize macros with Dialog block — different parameters each run.
Define repeating steps once with GROUP_CALL, call from many places.