No-Code Workspace — Block Reference

Flow ControlBlock usage recipe

Run Macro (RUN_MACRO)

Runs another saved macro

Documented for app version 1.0.50Updated: October 2, 2026

What Does It Do?

RUN_MACRO picks another saved macro from the target picker and runs it. There are two wait modes: "Start and continue" queues the target macro and the current flow continues immediately (Macro.run); "Wait for completion" runs the target inside the caller's session, waits with a timeout, and writes the outcome into an optional variable (Macro.runWait). One key=value parameter can be passed per line; the target macro reads them with Macro.params(). Self-calls and circular chains are bounded by the runtime call-chain guard (max depth 3, cycle detection).

When to Use?

Use when:

Keeping a shared flow (login, daily reward collection) in its own macro and calling it from many macros

Triggering sub-task macros in order from one orchestrator macro

Waiting for a preparation macro to finish and branching on its outcome

Firing an independent helper macro in the background while continuing your own flow

How to Use?

"Add Block" → "Run Macro (RUN_MACRO)"

TARGET MACRO: tap "Select a macro…" and pick the target from the list

WAIT MODE:

"Start and continue": the target is queued and the flow continues immediately

"Wait for completion": enter a timeout (ms); 0 = runtime default (there is no unlimited wait)

In wait mode, enter a RESULT VARIABLE name (optional)

PARAMETERS: one key=value per line (e.g., mode=fast); values support {{ expression }}

Parameters

Target macro

Saved macro to run; picked from the list

Wait mode

Start and continue (Macro.run) or Wait for completion (Macro.runWait)

Timeout (ms)

Maximum wait in wait mode; 0 = runtime default

Result Variable

Variable that receives the Macro.runWait outcome in wait mode (optional)

Parameters

One key=value per line; the target macro reads them with Macro.params()

Parameter	Description
Target macro	Saved macro to run; picked from the list
Wait mode	Start and continue (Macro.run) or Wait for completion (Macro.runWait)
Timeout (ms)	Maximum wait in wait mode; 0 = runtime default
Result Variable	Variable that receives the Macro.runWait outcome in wait mode (optional)
Parameters	One key=value per line; the target macro reads them with Macro.params()

Release Notes

Coming soonv1.0.51
While this macro holds background-swipe fingers, the started macro’s TOUCH blocks are refused and its own background gestures cannot start; release the fingers with Touch Break (TOUCH_BREAK) before starting the target.

Example Usage

Scenario: Wait for the daily-reward macro and branch on the outcome

RUN_MACRO → target: "Daily Reward"

Wait mode: Wait for completion, timeout 60000 ms

Result variable: reward_result

Parameter: mode=fast

COMPARE: check reward_result → continue the main flow on the TRUE branch

On the FALSE branch, warn with LOG + NOTIFY

Combinations / Used With

COMBINATIONS:

RUN_MACRO (wait) + COMPARE: Branch on the sub-macro outcome

IMAGE + RUN_MACRO: Trigger the matching macro when a screen appears

RUN_MACRO (start and continue) + your own flow: Keep going while the helper macro runs

TRY_CATCH + RUN_MACRO: Catch a target-macro error and run a recovery flow

SET_VARIABLE + RUN_MACRO parameters: Pass dynamic values to the target

Tip

Runs another saved macro

Warnings / Cautions

WARNING:

If the target macro is deleted, saving warns and runtime raises an error

Targeting the macro itself creates a self-call chain; it can keep restarting until the runtime depth limit (3) kicks in

In wait mode a 0 timeout is NOT unlimited; the runtime applies its safe default

Parameter lines that do not match "key=value" are ignored with a warning

JSON-flow targets are not supported in wait mode

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

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

Basic

RUN_MACRO runs ANOTHER macro saved on the device. You add the block and pick the target from the list via "Select a macro…". There are two wait modes: "Start and continue" queues the target and your flow continues immediately; "Wait for completion" runs the target and waits for it to finish. It is the clean way to keep a shared flow in its own macro and call it from many macros.

Advanced

Wait mode takes two values: fire_and_forget (Start and continue — Macro.run, the target is queued) and wait (Wait for completion — Macro.runWait, runs inside the caller's session). In "Wait for completion" mode you enter a timeout (ms); 0 = runtime default, meaning there is NO unlimited wait. If you also give a Result Variable name in that mode, the Macro.runWait outcome is written there. Parameters are passed one key=value per line (e.g. mode=fast) and the target macro reads them with Macro.params(); values support {{ expression }}. Parameter lines that don't match the format are ignored with a warning. JSON-flow targets are not supported in wait mode.

Pro

RUN_MACRO is the foundation of multi-macro orchestration: one orchestrator macro triggers sub-task macros in order by waiting and branches on each outcome. Collect shared login/daily-reward flows into a single macro and, instead of fire_and_forget, actually evaluate the result with wait + Result Variable + COMPARE. Use fire_and_forget for background helpers — e.g. fire a monitoring/notification macro and keep going with your own flow. Targeting the macro itself creates a self-call chain that risks restarting until the runtime depth limit (3) kicks in, so avoid it unless intentional. If the target macro is deleted, saving warns and runtime errors — wrap critical chains in TRY_CATCH.

Real-World Scenarios — Step-by-Step Recipes

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

Wait for the daily-reward sub-macro and branch on outcome

1RUN_MACRO → target: "Daily Reward"
2Wait mode: Wait for completion, timeout 60000 ms
3Result variable: reward_result
4Parameter line: mode=fast
5COMPARE: check reward_result → on TRUE continue the main flow, on FALSE LOG + NOTIFY

Fire a background monitor macro

1RUN_MACRO → target: "Connection Monitor"
2Wait mode: Start and continue (fire_and_forget)
3No result variable needed; your flow continues immediately
4While the main macro keeps working, the monitor runs its own loop in the background

Which Blocks to Pair With — Pro Combinations

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

+ COMPARE

In wait mode you evaluate the sub-macro's result variable and branch the flow.

+ SET_VARIABLE

Pass dynamic values into parameter lines (with {{ expression }}) to carry context to the target macro.

+ TRY_CATCH

If the target errors (deleted/failed), catch it and run a recovery flow.

+ IMAGE

Trigger the matching sub-macro when a specific screen appears; screen-aware orchestration.

+ GROUP_CALL

GROUP_CALL for reuse inside one macro, RUN_MACRO to chain separate macros — two layers of modularity.

Common Mistakes and Fixes

Thinking a 0 timeout in "Wait for completion" mode means unlimited; 0 = the runtime's safe default, not infinite.

Writing a parameter that doesn't match "key=value"; invalid lines are ignored with a warning and never reach the target.

Targeting the macro itself; it risks restarting until the runtime depth limit (3) kicks in.

Deleting the target macro but leaving the reference; you get a save warning and a runtime error. Wrap critical chains in TRY_CATCH.

Pro Tips

Build a multi-macro architecture: an orchestrator macro waits on sub-tasks in order with wait + Result Variable and branches on their outcomes.

Keep the shared flow (login, reward) in one macro; maintenance happens in one place and all callers update automatically.

Use fire_and_forget when you don't truly need to wait — background helpers shouldn't block the main flow.

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 _mrunParams1 = {}
_mrunParams1["mode"] = "fast"
Macro.run("macro_target_1", _mrunParams1)

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 →