No-Code Workspace — Block Reference

Data and UtilitiesBlock usage recipe

List (LIST)

Creates a fixed list variable

Documented for app version 1.0.50Updated: October 2, 2026

What Does It Do?

Builds a list from items typed line by line or separated by commas. Numbers stay numbers, true/false stay booleans, others become text. If the field is bound to a list with the lightbulb, its items are copied.

When to Use?

Use it for labels to scan in order, numbers to add up, or known targets to process in one loop.

How to Use?

Enter the list name (default items)

Type the items; quote an item that contains a comma

Type the bare name, without braces, in the FOR_EACH list field

Parameters

List Variable / Items

List name and its items

List variable typeComing soonv1.0.51

Started from a JSON array in the variable editor; indexing starts at 1

Parameter	Description
List Variable / Items	List name and its items
List variable typeComing soonv1.0.51	Started from a JSON array in the variable editor; indexing starts at 1

Example Usage

LIST amounts = 10, 25, 40 → FOR_EACH (list = amounts, item = amount) → SET_VARIABLE total = total + amount → LOG "Total: {{total}}"

Combinations / Used With

COMBINATIONS:

LIST + FOR_EACH: Same steps for each item

LIST + SET_VARIABLE: Accumulate a total in the loop

Tip

Creates a fixed list variable

Warnings / Cautions

WARNING:

The list does not grow on its own at runtime; use a split or matchAll output for dynamic lists

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

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

Basic

LIST defines a static list variable to iterate with FOR_EACH. You enter items line by line or comma-separated, and the block turns them into a table (e.g. items = { "alpha", "beta" }). It is the simplest way to create a ready set of items to loop over.

Advanced

The generated code prepares the list variable as an ordered Lua table — exactly what FOR_EACH iterates with ipairs. You can separate items by newline or comma; numbers become numbers, true/false become booleans and other items become text, so numeric comparisons inside FOR_EACH work as expected. Put an item that contains a comma in quotes ("hello, world"). If you bind the items field to a list variable with the lightbulb, the block copies that list's items. The list is static: it does not grow dynamically at runtime, it returns whatever you wrote at design time. For a dynamic collection, it is better to feed a STRING_OP split or REGEX_MATCH matchAll output into FOR_EACH; LIST is for fixed, known sets.

Pro

Use LIST for known, fixed work sets: menu tabs to scan, group names to run, coordinate labels to tap. Pair it with FOR_EACH and repeat the same block sequence per item; that pattern is far more maintainable than copying ten separate blocks. Keep items meaningful and consistent; inside FOR_EACH you can bind the item variable directly into other blocks (a CLICK target, a GROUP_CALL name, an HTTP path fragment). When you need dynamic data, keep LIST static and produce the real dynamic source (split/matchAll/JSON array) in a separate variable; mixing the two makes the flow fragile.

Real-World Scenarios — Step-by-Step Recipes

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

Scan a fixed tab list in order

1LIST -> items = home, profile, settings
2FOR_EACH -> list = items, item = item
3Inside the loop, bind the TEXT search text to item with the lightbulb
4Tap the match with CLICK

Add up a list of numbers

1LIST -> amounts = 10, 25, 40 (items are stored as numbers)
2SET_VARIABLE -> total = 0
3FOR_EACH -> list = amounts, item = amount
4Inside the loop SET_VARIABLE -> total = total + amount
5LOG "Total: {{total}}"

Which Blocks to Pair With — Pro Combinations

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

+ FOR_EACH

The one natural partner for LIST; it walks the static table with ipairs and runs the same steps per item.

+ SET_VARIABLE

Accumulates a total, a counter or combined text across the loop; numeric items go straight into the math.

+ MAP

Use loop items as keys and accumulate a value per item in a MAP.

+ CLICK / TEXT

If each item is a target label, you bind the item variable into the find-and-tap flow with the lightbulb inside FOR_EACH.

Common Mistakes and Fixes

Expecting LIST to grow dynamically at runtime. Fix: LIST is static; for a dynamic collection feed a STRING_OP split or REGEX_MATCH matchAll output into FOR_EACH.

Defining a LIST but forgetting to iterate it with FOR_EACH. Fix: LIST does nothing on its own; always pair it with a FOR_EACH.

Separating items inconsistently (some newline, some comma, extra spaces). Fix: pick one separator style and keep items clean.

Pro Tips

Compress repeated block sequences with LIST + FOR_EACH; reducing ten copied blocks to one loop dramatically eases maintenance.

Coming soonv1.0.51You can also define a fixed list as a variable instead of a block: in the variable editor pick the List type and enter a JSON array (e.g. ["home", "profile", 3]). The list is a Lua array that starts at 1; FOR_EACH walks it directly and the LIST block can be bound to it with the lightbulb. null is not supported, and it can hold at most 2,048 values and 12 nested levels.

Keep item names directly usable in other blocks (tab label, path fragment) so binding the item variable with the lightbulb works without copying.

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

items = {
 "alpha",
 "beta",
}

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.

🗃Source and Destination

Use file paths, key names, regex sources, and JSON paths with clear naming discipline.

🧷Default Value

Define default outputs clearly so the builder flow does not collapse when data is missing.

🔄Write Then Read Back

For KV or file writes, verifying the result in the next block is healthier in production-grade flows.

🪶Narrow Output Design

Instead of carrying large raw payloads, extract the value you need and pass it forward via a result variable.

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 →