No-Code Workspace — Block Reference

Flow ControlBlock usage recipe

Assert (ASSERT)

Stops execution with an error when a condition fails

Documented for app version 1.0.50Updated: October 2, 2026

What Does It Do?

Checks a Compare-style condition but does not branch. If it holds the flow continues; if not, an error with the Error Message is raised. Inside Try/Catch it goes to Catch; otherwise the macro stops at this step.

When to Use?

Stop at once when the expected screen state is missing

Do not continue when a critical variable is empty or wrong

Inside Try/Catch, turn a condition that raises no error by itself (such as an HTTP status code) into one

How to Use?

Enter the condition with Left Operand, Operator and Right Operand (the Compare operators)

Type the failure text in Error Message; {{ expression }} works, and an empty message becomes "Assertion failed: <block name>"

Parameters

Left Operand / Operator / Right Operand

==, !=, >, <, >=, <=, Contains, Does Not Contain

Error Message

Text of the error raised on failure; supports {{ expression }} and a lightbulb variable

Parameter	Description
Left Operand / Operator / Right Operand	==, !=, >, <, >=, <=, Contains, Does Not Contain
Error Message	Text of the error raised on failure; supports {{ expression }} and a lightbulb variable

Example Usage

Read orderId with OCR_VALUE

Assert: orderId != "", Error Message: "Order id could not be read"

Later HTTP or CLICK steps run only if the check passes

Combinations / Used With

OCR_VALUE + ASSERT: stop when the value read is empty

ASSERT + TRY_CATCH: raise an error but recover in a controlled way

HTTP_REQUEST + ASSERT: check the status code so Try/Catch can retry

Tip

Stops execution with an error when a condition fails

Warnings / Cautions

There is no FALSE branch; use Compare or If / Else for two paths

Outside Try/Catch a failed assert stops the macro (or reaches the Error Handler if there is one)

An empty Left or Right Operand is a validation error

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

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

Basic

ASSERT checks a Compare-style condition but raises an error instead of branching: if the condition is TRUE the flow continues; if FALSE an error with the Error Message is raised. Inside Try/Catch the error goes to Catch; otherwise the macro stops (or reaches the project Error Handler if there is one). An empty Error Message becomes "Assertion failed: <block name>".

Advanced

You build the condition like COMPARE with a left value / operator (==, !=, >, <, >=, <=, contains, not_contains) / right value, and you also enter an error message. The key difference from COMPARE: ASSERT has no FALSE branch; on failure it cuts the flow with an error() call. That is why pairing ASSERT with TRY_CATCH is powerful: outside TRY_CATCH, ASSERT stops the macro; inside it, the failure falls into the catch branch and you recover in a controlled way. Write a meaningful error message; you will see this text in logs and immediately know which precondition dropped.

Pro

ASSERT is the no-code counterpart of the guard-clause pattern: before a risky step (REPLAY, CLICK, HTTP) you check every required precondition and stop at once if one fails, so a harmful action in the wrong state never runs. For several preconditions, place ASSERTs one after another; the first that fails stops with its own message. Because the Error Message supports {{ expression }}, you can print the current value in it. In critical macros wrap ASSERTs in TRY_CATCH and compensate in Catch, turning a hard stop into a controlled recovery. ASSERT also turns conditions that raise no error by themselves (such as an HTTP status code) into an error that triggers TRY_CATCH’s retry.

Real-World Scenarios — Step-by-Step Recipes

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

Validate a critical variable, stop if missing

1Get order_id with OCR_VALUE or SET_VARIABLE
2ASSERT: order_id != ""
3Error message: "Order id could not be read"
4Later HTTP/CLICK steps only run if validation passes

Validate a screen precondition, recover with TRY_CATCH

1Add a TRY_CATCH block
2Inside try, IMAGE: search the target button, write match_x
3ASSERT: match_x > 0, message: "Target button missing, replay aborted"
4If ASSERT passes, run REPLAY
5In the catch branch: return to the screen and retry

Which Blocks to Pair With — Pro Combinations

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

+ TRY_CATCH

ASSERT throws an error; TRY_CATCH catches it so you recover in a controlled way instead of hard-stopping.

+ OCR_VALUE

If the value read from the screen is empty/0, ASSERT hard-stops to prevent proceeding with bad data.

+ IMAGE

Validates that a match really exists (match_x > 0), setting up a safety check before a risky step.

+ HTTP_REQUEST + TRY_CATCH

HTTP raises no error on a network failure; asserting the status code right after the request inside Try triggers the retry.

Common Mistakes and Fixes

Expecting a FALSE branch from ASSERT: there is none. If the condition fails the flow is cut. If you need two paths, use IF_ELSE/COMPARE.

Using ASSERT outside TRY_CATCH and being surprised it stops: a bare ASSERT halts the macro. Wrap it in TRY_CATCH if you want to recover.

Writing an empty or vague error message: text like "error" reduces debug quality. Write a clear message saying which precondition dropped and why.

Not defining the variable in the condition beforehand: with an undefined variable ASSERT behaves unexpectedly. Define it first with SET_VARIABLE/OCR_VALUE.

Pro Tips

Put a guard ASSERT before every risky step; a damaging action in the wrong state never starts, and the macro stays predictable.

Check several preconditions with separate ASSERTs in a row; each one says which condition failed with its own message.

Put context in the error message (variable name + expected value); in logs you find the root cause of a failure within seconds.

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 →

if not (1 == 1) then
 error("assert failed")
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 →