No-Code Workspace — Block Reference

Flow ControlBlock usage recipe

For Each (FOR_EACH)

Runs the body once for each item in a list

Documented for app version 1.0.50Updated: October 2, 2026

What Does It Do?

Walks the items of a list variable in order. Each pass writes the item and its position (starting at 1) into the variables you choose for the blocks in the "For Each Item" branch.

When to Use?

Do the same work for every address, text or value in a list

Iterate over lists built with JSON_PARSE, LIST, SET_VARIABLE or a split

How to Use?

Enter the List variable (default items), Item variable (item) and Index variable (index); the list can also be picked with the lightbulb

Add the blocks for each item to the "For Each Item" branch

Parameters

List variable

The list to walk (default items)

Item / Index variable

The item of each pass (item) and its position from 1 (index)

List variable typeComing soonv1.0.51

A variable started from a JSON array with the List type in the variable editor (e.g. ["home", "profile", 3]) is walked directly; indexing starts at 1 and null is not supported

Parameter	Description
List variable	The list to walk (default items)
Item / Index variable	The item of each pass (item) and its position from 1 (index)
List variable typeComing soonv1.0.51	A variable started from a JSON array with the List type in the variable editor (e.g. ["home", "profile", 3]) is walked directly; indexing starts at 1 and null is not supported

Example Usage

SET_VARIABLE: urls = {"https://api.example.com/a", "https://api.example.com/b"}

For Each: list urls, item url, index i

Body: HTTP_GET (URL bound to url with the lightbulb) → LOG "Address {{ i }} processed"

Combinations / Used With

SET_VARIABLE + FOR_EACH: Define a list with blocks, then iterate

FOR_EACH + COMPARE + CONTINUE: skip unwanted items

FOR_EACH + BREAK: leave once the item you need is found

Tip

Runs the body once for each item in a list

Warnings / Cautions

If the list variable is undefined or not a table, the macro does not stop; FOR_EACH skips the body and leaves a log entry

Lua lists start at 1; the loop ends at the first empty (nil) item

If the list must be filled, check it with Assert first

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

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

Basic

FOR_EACH walks a list (a Lua table) one element at a time. Each turn the current element goes into the "item" variable and its position into the "index" variable, both usable in the inner body blocks. Build the list first with SET_VARIABLE, LIST, JSON_PARSE, or STRING_OP split, then iterate it with FOR_EACH. An empty list runs zero times; a non-table value never crashes the macro — the body is skipped and a log line is left.

Advanced

Rename the element and index variables to fit the job (e.g. "url" and "i") so names do not collide in nested loops. Lua lists are 1-based, not 0-based — keep that in mind when doing index arithmetic. FOR_EACH is fail-closed on a non-table value: it emits "FOR_EACH skipped: list variable is not a table", so guard with ASSERT or COMPARE beforehand when the list is mandatory. Feeding a JSON_PARSE array straight into FOR_EACH is the strongest pattern; LOG each element with its index to trace the flow. Mutating the element inside the body does not change the original list; accumulate the result in a separate variable.

Pro

On long lists add a small WAIT inside the body to ease the CPU and the OEM watchdog; this pacing is essential when every turn does IMAGE/OCR_VALUE. Keep the loop body idempotent: processing the same element twice (after a retry) must not produce side effects. Use COMPARE + BREAK for early exit and COMPARE + CONTINUE to skip an element — BREAK/CONTINUE affect only the nearest loop. Instead of grinding a huge list in one FOR_EACH, page it and wrap each page in TRY_CATCH so one bad element does not sink the whole pass. For critical jobs persist the index to KV or a file so you can resume from where you stopped if the process dies.

Real-World Scenarios — Step-by-Step Recipes

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

Process every address in a list

1SET_VARIABLE: urls = {"https://api.example.com/a", "https://api.example.com/b"}
2FOR_EACH: list=urls, item=url, index=i
3Inner: HTTP_GET → bind the URL field to url with its lightbulb
4Inner: WAIT 400 ms
5Inner: LOG "Address {{ i }} processed"

Process an API array

1HTTP_REQUEST → result variable apiResponse
2JSON_PARSE: bind the source to apiResponse, path=items, resultVar=itemList
3FOR_EACH: list=itemList, item=row, index=i (a non-table list skips the body and is logged)
4Inner: COMPARE row.active == true → CONTINUE if not
5Inner: LOG "Processed: {{ row.name }}"

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

The most direct way to define the list to iterate; it prepares the input FOR_EACH consumes.

+ JSON_PARSE

Feeds an array from an API response straight into FOR_EACH; the cleanest pattern for processing network data block by block.

+ COMPARE + CONTINUE

Skips unwanted elements (empty, inactive, non-matching) so only qualifying ones are processed.

+ COMPARE + BREAK

Lets you exit early once the target element is found, without scanning the whole list.

+ TRY_CATCH

Stops a single bad element from sinking the whole pass; wraps the body, catches the error, and moves to the next element.

Common Mistakes and Fixes

Using FOR_EACH before defining the list variable. Fix: build the list with SET_VARIABLE/LIST/JSON_PARSE first; an undefined or non-table value silently skips the body (check the log).

Assuming the index starts at 0. Fix: Lua lists are 1-based; the first element is index=1 in any index arithmetic.

Omitting WAIT inside the body on a long list. Fix: add at least a short WAIT per turn, otherwise CPU/heat climb and OEM process-kill risk rises.

Pro Tips

Give the element and index variables meaningful names ("url", "i"); the defaults "item"/"index" collide in nested FOR_EACH loops.

Add an ASSERT before FOR_EACH when the list is mandatory — since the fail-closed skip is silent, an explicit check is needed to catch missing data early.

Persist progress by writing the index to KV/a file; if the process dies you can resume from the element you stopped at.

Coming soonv1.0.51Instead of building a fixed list with a block, pick the List type in the variable editor and enter a JSON array (e.g. ["home", "profile", 3]); type that variable’s name in FOR_EACH’s List variable field. The list is a Lua array that starts at 1; it can hold at most 2,048 values and 12 nested levels, and null is not supported.

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 items = {10, 20}

local _foreach_list_1 = items
if type(_foreach_list_1) ~= "table" then
 if System and System.log then System.log("FOR_EACH skipped: list variable 'items' is not a table") end
 _foreach_list_1 = {}
end
for index, item in ipairs(_foreach_list_1) do
 wait(1)
 ::_cont_2::
end
::_break_3::

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 →