1
Send to the shared area
When one item or a multi-selection is active, the shared-area button can copy the selected part from the workspace, group, true/false action branch, dialog, and variables surfaces into the device-local library.
No-Code Workspace — Block Reference
Flow ControlBlock usage recipe
Compare (COMPARE)
Compares two values or screen regions and branches
Documented for app version 1.0.50Updated:
Block Preview
Captured from the in-app Visual Builder block card in the English UI.
English UI
What Does It Do?
The comparison type picks one of two modes. Compare values tests a left and a right operand with an operator. Compare screen regions captures the first region as a reference and searches the target regions for a similar image. The TRUE or FALSE branch runs from the result.
When to Use?
1
Has a counter reached its target (counter >= 10)
2
Does a value equal the expected one, does a text contain a word
3
Does the image in one region also appear in another
How to Use?
1
Choose the comparison type
2
Compare values: Left Operand, Operator and Right Operand; operands can be a variable name, a literal or {{ expression }}, or a lightbulb variable
3
Compare screen regions: Reference region and target regions (2–8 in total), Reference capture and Target region logic (Any / All)
4
Fill the TRUE and FALSE branches; in region mode the match gives tap, swipe and touch blocks on the TRUE branch a live target
Parameters
Comparison type
Compare values or Compare screen regions
Left Operand / Operator / Right Operand
==, !=, >, <, >=, <=, Contains, Does Not Contain
Reference capture
Once per macro run, On every block execution or Every N executions; the reference stays in memory only
Region scan
Match Confidence, Scale, scan engine, Search Duration, Scan Rate, Maximum scan attempts (1–20), Retry Interval
Result outputs
Status variable (matched / not_found / invalid_config) and the matched target region’s 1-based index
| Parameter | Description |
|---|---|
| Comparison type | Compare values or Compare screen regions |
| Left Operand / Operator / Right Operand | ==, !=, >, <, >=, <=, Contains, Does Not Contain |
| Reference capture | Once per macro run, On every block execution or Every N executions; the reference stays in memory only |
| Region scan | Match Confidence, Scale, scan engine, Search Duration, Scan Rate, Maximum scan attempts (1–20), Retry Interval |
| Result outputs | Status variable (matched / not_found / invalid_config) and the matched target region’s 1-based index |
Example Usage
1
Inside a GROUP with Infinite Loop, SET_VARIABLE counter = counter + 1
2
COMPARE: counter >= 10 → BREAK on the TRUE branch
Combinations / Used With
1
OCR_VALUE + COMPARE: compare a value you read with a threshold
2
COMPARE (regions) + CLICK: tap the matched target region
3
BOOLEAN_GROUP: combine several value comparisons
Tip
Compares two values or screen regions and branches
Warnings / Cautions
1
An empty Left or Right Operand is a validation error; the macro does not start
2
>, <, >= and <= convert both sides to numbers (unconvertible values become 0); == and != compare as-is: "10" stored as text does not equal the number 10
3
Contains and Does Not Contain are case-sensitive
4
Compare screen regions does not run in a Boolean Group or If / Else condition list; add it as a standalone block
Step-by-Step Mastery: Basic → Advanced → Pro
The same block at three levels: a quick start, the real options, and professional techniques.
Basic
COMPARE compares two values and routes to the TRUE (onTrue) or FALSE (onFalse) branch based on the result. The left value (compareLeft) and right value (compareRight) can be constants or variables; the operator between them (compareOperator) defines the comparison. It is the core block for everyday decisions like counter checks, equality checks, and threshold checks.
Advanced
There are two comparison types. Compare values: == and != compare the values as they are; >, <, >= and <= convert both sides to numbers (unconvertible values become 0); Contains and Does Not Contain search inside text case-sensitively. Operands can be a variable name, a literal or {{ expression }}, and a variable can be bound with the lightbulb. Compare screen regions: the first region is the reference, captured on every block execution, once per macro run or every N executions; 1–7 target regions are searched for a similar image, with Target region logic Any or All. A match gives tap, swipe and touch blocks on the TRUE branch a live target, and Result outputs write the status (matched / not_found / invalid_config) and the matched target region’s index. The reference image lives only in runtime memory.
Pro
Watch type consistency: == and != compare without conversion, so "10" stored as text does not equal the number 10. For numeric thresholds use operators such as > or >=; both sides are converted to numbers. An empty Left or Right Operand is a validation error and the macro does not start. In text equality, leading/trailing spaces and letter case change the result; normalize with STRING_OP first if needed. Compare screen regions cannot be used in a Boolean Group or If / Else condition list; add it to the flow as a standalone Compare.
Real-World Scenarios — Step-by-Step Recipes
Small, reproducible examples that combine several blocks — build them straight into your own macro.
Exit the loop when the counter hits the threshold
- 1SET_VARIABLE: counter = 0 (before the loop)
- 2Inside GROUP (infinite loop) do the work
- 3SET_VARIABLE: counter = counter + 1
- 4COMPARE: counter >= 10
- 5TRUE: BREAK (exit after 10 passes)
Compare screen regions and tap the match
- 1Reference region: the selected icon; target regions: two rows of the list
- 2Reference capture: On every block execution, Target region logic: Any
- 3Add CLICK on the TRUE branch; the match gives it a live target
- 4Watch the status variable with LOG (matched / not_found)
Which Blocks to Pair With — Pro Combinations
This block is useful on its own — but it shines when paired with the right partners.
+ SET_VARIABLE
Defines the variable to compare first; it is the prerequisite for counter and state checks.
+ OCR_VALUE
Writes a number read from the screen into a variable; COMPARE then performs the threshold check.
+ BREAK
On the COMPARE TRUE branch, BREAK gives you a conditional exit from the loop.
+ BOOLEAN_GROUP
When a single COMPARE is not enough, it combines several COMPAREs into one decision with AND/OR logic.
Common Mistakes and Fixes
Comparing an undefined variable: if it does not exist the result is unexpected or errors. Define it first with SET_VARIABLE/OCR_VALUE/DIALOG.
Using contains for number comparison: contains searches text. For numeric thresholds/equality use operators like ==, >, <, >=.
Leaving the left or right value empty: validation reports it as an error and the macro does not start. Fill both sides or bind a variable with the lightbulb.
Forgetting whitespace/case differences when comparing text with ==: " Yes" is not equal to "yes". Normalize first if needed.
Pro Tips
For a numeric threshold pick a numeric operator; tonumber kicks in automatically and the text "50" behaves like 50.
For flexible text matching consider contains/not_contains instead of ==; the decision survives even if the UI text changes slightly.
Log the comparison result with LOG; during debugging you instantly see which branch was taken and why.
This Block's Code (Editor View)
LuaThe Lua below is what the Code Editor generates for this block with sample settings. Adding cases, branches, actions or loops, or changing settings, extends the generated code accordingly. Study it to see what the block does under the hood, to learn Lua, or to copy and adapt it. Use the Copy button (top-right) to paste it into the Code Editor, or “Try in Editor →” to run it in the live editor.
local _cmp_result1 = (1 == 1)Note: generated code can evolve across versions; helper names (e.g. _reg1, m1) and internal optimizations may change. The logic and the called APIs reflect the block’s behavior.
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.
🔀Branch and Exit Rules
Define TRUE/FALSE, try/catch, and loop exit behavior before chaining more blocks.
📦Results and Scope
Keep it explicit where group, dialog, and loop variables are created and where they are consumed.
🛑Safety Bounds
Long flows become brittle quickly without timeouts, ASSERT blocks, BREAK logic, or explicit guards.
🧩Modularity
Moving repeated steps into GROUP and GROUP_CALL improves readability in larger projects.
Builder vs Lua Boundary
Raw touch pointer lifecycle stays code-first
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.releaseAfterBounded dialog design is builder-backed; freer composition stays code-first
The DIALOG block and dialog designer cover a bounded field set in the builder: Info Text, Text Input, Checkbox, Description, Radio Group, Dropdown, Multi Select, Tab Group, Date Time, Number Range, Slider, Image Picker, Color Picker, File Picker, Recorder Picker, Tag, Signature, and Spacer. The buttons are designed too: the Positive button and Negative button tabs set each button’s text, background, and border color, corner radius, and minimum height next to a preview. Freer Setting.builder composition, multi-step wizard flows, and mixed HUD/dialog choreography still do not map 1:1 into the builder.
Coming soonv1.0.51Two more fields: Agent Detect references (agent_detect_editor) lets the user pick a saved reference set or add and edit references, and Save confirms the selection; Navigation setup editor (navigation_editor) edits a saved map, marker and route from the Dialog and returns the setup and route selection without moving the character.
Setting.builderDialogHudTextViewAgentDetectEditorNavigationEditorAdvanced HTTP request chaining stays code-first
HTTP_GET, HTTP_POST, and HTTP_PUT cover common fixed-method flows; HTTP_REQUEST covers one bounded request with method, header lines, body, content type, query parameters (GET and DELETE), timeout, and a bounded retry. These blocks never throw; they write the status code (-1 on a network failure). Cookie handling, chained request objects, and lower-level client flows still need the code editor.
Request()Request.setCookieRequest.getCookiesCUSTOM_CODEGeneral programming surfaces stay code-first
The MAP, LIST, JSON_PARSE, REGEX_MATCH, and METRICS blocks cover the everyday cases: map actions, a static list, reading a value from a JSON path, regex match, find, replace, and split, and metrics actions. The rest of the Map, Array, JSON, Regex, and Metrics APIs (for example Array sort, filter, and map) is broader than the builder recipe model and stays on the CUSTOM_CODE and code editor side.
MapArrayJSONRegexMetricsLow-level runtime and Lua composition stays code-first
Runtime helpers, raw Request objects, Lua built-ins such as print/pcall/xpcall, and free-form object chaining patterns are represented through CUSTOM_CODE or the code editor.
RuntimeRequestprintpcallxpcallCUSTOM_CODEDebug 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
1
Variables defined with SET_VARIABLE are accessible throughout the macro (global scope). All blocks can read/write the same variable.
2
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.
3
FOR_EACH loop variables (item and index) only carry valid values inside the loop body. Outside the loop they are outside local scope and should not be used.
4
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.
5
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 has not 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.
Syntax
{{ expression }}Examples
Skor: {{ score + 1 }} → "Skor: " .. tostring(score + 1){{ name }} kazandı! → tostring(name) .. " kazandı!"X:{{ x }} Y:{{ y }} → "X:" .. tostring(x) .. " Y:" .. tostring(y)Supported Blocks
SET_VARIABLELOGCOMPARECLIPBOARD_WRITENOTIFY_TOASTKV_SET
Security Note
Expressions are checked by the sandbox policy. Security-sensitive calls like loadstring, require, debug are automatically blocked.
General Tips
1
Keep scan regions as small as possible — improves speed, reduces false matches.
2
Always add an exit condition when using infinite loops (BREAK, timeout, or conditional exit).
3
Use network operations and error-prone steps inside TRY_CATCH.
4
If you need global error handling, use the Error Handler (ERROR_HANDLER) block as a singleton in the project.
5
Small coordinate offsets (CLICK/SWIPE) improve tap accuracy across different DPI and screen scales.
6
Customize macros with Dialog block — different parameters each run.
7
Define repeating steps once with GROUP_CALL, call from many places.
Cross-macro local library
Local Shared Macro Area
The Local Shared Macro Area moves blocks, variables, dialog fields, gallery assets, and imported media dependencies between macros on the same device. It is device-local, not cloud sync, not Firebase sharing, and not a replacement for public macro sharing.
Professional usage model: put a reusable login flow, common scan region, shared dialog form, variable group, template image, color profile, replay recording, or imported PLAY_SOUND media file into the shared area from one macro, then import it from the relevant + menu in another macro.
VISUAL_BLOCKSVARIABLESDIALOG_FIELDSTEMPLATE_IMAGECOLOR_SWATCHREPLAY_RECORDMEDIA_FILE2
Import into another macro
The shared-area entry under the + menu imports the selected item into the surface that opened it. Main workspace, group, action branch, dialog, and variables each receive the compatible item type.
3
Share gallery assets
Gallery items include template images, color swatches, replay records, and imported audio/media files. They can move between macros on the same device so repeated templates, colors, recordings, and PLAY_SOUND media assets do not need to be captured again.
4
Keep it clean
The shared area is not a permanent dumping ground. Delete stale shared items from the shared-library panel; imports create a copy in the target macro and do not rewrite the source macro flow.
Checkpoint: after importing, review block names, linked template/image/color/record/media assets, and variable names in the target macro. The shared area creates a copy; delete stale shared items from the shared-library panel to keep the library clean.
AI assistant
Build a block chain with MH AI in natural language
Tell MH AI what you want in plain language; it proposes the right block sequence and lands it in the workspace after you approve. In the current release it works with cloud providers such as Gemini, Claude, and OpenAI; on-device local models are on the roadmap.