No-Code Workspace — Block Reference

Flow ControlBlock usage recipe

Math (MATH_EVAL)

Calculates from OCR, image, color, or text matches

Documented for app version 1.0.50Updated: October 2, 2026

Math (MATH_EVAL) advanced settings panel

What Does It Do?

Feeds a number read from a region, or a match coordinate, into math operations and stores the result in a variable. Input types: OCR text, image match, color match, and text match. Optionally compares the result with a threshold.

When to Use?

Use it to:

Read and calculate amounts, prices or times with OCR

Get match_x/match_y/match_w/match_h from a match

Compare the result with a threshold and branch

How to Use?

Choose INPUT TYPE first: OCR Text, Image Match, Color Match, or Text Match

Pick the scan region and, if needed, the target

OPERATION TYPE: Read Number, Detect Expression, or match_x/y/w/h

Add calculation steps with + (add, multiply, divide, round, etc.)

Enter the result variable and the optional threshold

Parameters

Input Type

OCR text, image, color, or text match

Scan Region / Targets

Constrained area and image, color, or text target

Operation Type

read_number, detect_expression, match_x/y/w/h

Calculations

+, -, x, /, mod, power, sqrt, round, floor, ceil, abs

Result Variable

Variable to store the result

Parameter	Description
Input Type	OCR text, image, color, or text match
Scan Region / Targets	Constrained area and image, color, or text target
Operation Type	read_number, detect_expression, match_x/y/w/h
Calculations	+, -, x, /, mod, power, sqrt, round, floor, ceil, abs
Result Variable	Variable to store the result

Example Usage

Scenario: Read a price and apply a 10% discount

MATH_EVAL → OCR Text, region: price

Read Number, Multiply x 0.9

Result: discountedPrice

Combinations / Used With

COMBINATIONS:

MATH_EVAL + COMPARE: Calculate then compare

IMAGE + MATH_EVAL: Find an image, take its coordinates

MATH_EVAL + TRY_CATCH: Catch divide-by-zero errors

Tip

Calculates from OCR, image, color, or text matches

Warnings / Cautions

WARNING:

Image/color/text modes require a target and a scan region

The OCR region should hold only the number; 5/S and 0/O can be confused

Complex formula layouts, handwriting, or multi-line regions are not supported in OCR expression mode

Division or modulo by zero throws a controlled error

Step-by-Step Mastery: Basic → Advanced → Pro

The same block at three levels: a quick start, the real options, and professional techniques.

Basic

MATH_EVAL reads a value from a screen region and does math on it. At its simplest you pick Input Type "OCR Text", mark the scan region where the number appears, leave Operation Type as "Read Number" (read_number), and store it in a Result Variable (e.g. result). You can then use that number in later blocks.

Advanced

Input Type has four modes: ocr, image, color, text. OCR mode turns the region into a number; image/color/text modes search for a target and you choose Operation Type match_x, match_y, match_w or match_h to read the match's coordinate/size. "Detect Expression" (detect_expression) solves a region that holds only a number or a simple expression (e.g. 12+3). In the Calculations list press + to chain add, subtract, multiply, divide, mod, power, sqrt, round, floor, ceil, abs, min and max. The optional threshold comparison tests the result against a value (>=, >, etc.) and emits a TRUE/FALSE branch.

Pro

To read OCR numbers professionally, shrink the region so it wraps only the digits; background, icons or unit symbols corrupt OCR (5/S, 0/O get confused). If you fill the persistent Cache Key (mathCacheKey) the result is stored on-device, handy for reading the previous run's value next turn to compute a delta/increase. Division and modulo by zero throw a controlled runtime error, so wrap MATH_EVAL in TRY_CATCH when the divisor comes from a variable. In coordinate modes (match_x/y), validating the target first with IMAGE/COLOR and then taking the exact pixel with MATH_EVAL is far more robust than a blind tap.

Real-World Scenarios — Step-by-Step Recipes

Small, reproducible examples that combine several blocks — build them straight into your own macro.

Read a price and apply a 10% discount

1MATH_EVAL → Input Type: OCR Text, scan region: price area
2Operation Type: Read Number (read_number)
3Calculation: Multiply x 0.9
4Result Variable: discountedPrice
5LOG → "Discounted price: {{discountedPrice}}"

Get an image's X coordinate and branch on a threshold

1IMAGE → find the target image
2MATH_EVAL → Input Type: Image Match, Operation Type: match_x, Result Variable: targetX
3MATH_EVAL threshold: targetX >= 540
4TRUE: right half → CLICK
5FALSE: left half → different flow

Which Blocks to Pair With — Pro Combinations

This block is useful on its own — but it shines when paired with the right partners.

+ OCR_VALUE

OCR_VALUE reads the raw number and MATH_EVAL processes it; the OCR_VALUE -> MATH_EVAL -> COMPARE chain is the classic measure-compute-decide flow.

+ IMAGE

Validate the target with IMAGE first, then take its exact pixel with MATH_EVAL match_x/match_y.

+ COMPARE

When the built-in threshold is not enough, feed the MATH_EVAL result into COMPARE for richer conditions.

+ SET_VARIABLE

Transfer the computed result into another variable to accumulate it across a loop.

+ TRY_CATCH

Catches arithmetic errors from divide-by-zero, mod 0, or broken OCR expressions without stopping the macro.

Common Mistakes and Fixes

Letting text, a unit (₺, %) or an icon fall inside the OCR scan region. Fix: shrink the region to wrap only the digits.

Forgetting the target or scan region in image/color/text mode. Fix: these modes require a target, add it first.

Ignoring that a variable divisor can be zero. Fix: wrap MATH_EVAL in TRY_CATCH or check the divisor with COMPARE first.

Using detect_expression on multi-line or complex formula layouts. Fix: expression mode is only for a single-line number/simple expression.

Pro Tips

Instead of re-reading the same number every run, fill the persistent Cache Key; next run you can read the old value and compute the delta/increase.

Rather than fighting OCR, pin the scan region for fixed-position numbers; the smaller and cleaner the region, the more accurate the read.

Use round/floor/ceil in the Calculations chain to coerce the result to the integer type the next block expects; fractional coordinates can miss a tap.

If you open an older MATH_EVAL block without an input type, you see the Lua expression (optional) field and the Compute preview; the expression becomes code only there. New blocks work with an input type and the Calculations list.

This Block's Code (Editor View)

Lua

The 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.

lua

Try in Editor →

local result = nil

Snap.screenRefresh()
local _mm1 = nil
local _mReg1_1 = Region():noScale()
_mm1 = _mReg1_1:find(Asset.text(".*"):mScore(0.8), {ocrScript="auto", engine="balanced_text"})
if _mm1 ~= nil then
 result = Num.parseOcr(_mm1:getText() or "", 0)
 if result >= 0 then
 end
end

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.

Block ↔ Lua Mapping →

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.releaseAfter

Bounded 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.builderDialogHudTextViewAgentDetectEditorNavigationEditor

Advanced 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_CODE

General 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.

MapArrayJSONRegexMetrics

Low-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_CODE

Debug 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 are outside local scope and should not be used.

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 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

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.

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_FILE

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.

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.

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.

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.

Learn more →