No-Code Workspace — Block Reference

Flow ControlBlock usage recipe

Comment (COMMENT)

Adds a note to the flow; does not affect execution

Documented for app version 1.0.50Updated: October 2, 2026

What Does It Do?

Use it to explain the project, add a section header or note a to-do. The Comment Type is Note, Section, TODO or Warning, and the card shows that type as its name. It reaches the Lua only as comment lines (-- NOTE:, -- TODO:, -- WARNING: or a section header).

Pro note: comments create structure

The note, section, todo, and warning comment kinds are not just notes in large projects. They provide structure, navigation, and team-readable intent.

When to Use?

Note the purpose of a complex group

Split the flow with section headers

Mark unfinished work as TODO and a fragile step as Warning

How to Use?

Choose the Comment Type: Note, Section, TODO or Warning

Write the text; for Section the first line becomes the header

Parameters

Comment Type

Note, Section, TODO or Warning

Parameter	Description
Comment Type	Note, Section, TODO or Warning

Example Usage

Comment (Section): "Login" → login blocks → Comment (TODO): "Add recovery for the error screen"

Combinations / Used With

COMMENT + GROUP: explain the group’s purpose

COMMENT + CUSTOM_CODE: describe in plain words what the code does

Tip

Adds a note to the flow; does not affect execution

Warnings / Cautions

A comment produces no executable code and does not change the flow

An empty comment is not added to the Lua

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

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

Basic

COMMENT is an explanatory note that does NOT affect macro execution at all. It generates no code and changes no runtime behavior — it exists only to document the project, explain a group's purpose, or leave context for a future maintainer (or future you). You write the explanation text and place it next to critical blocks.

Advanced

The COMMENT block’s Comment Type is Note, Section, TODO or Warning, and the card shows that type as its name. In the generated Lua it becomes comment lines only: -- NOTE: for Note, -- TODO: for TODO, -- WARNING: for Warning, and a section divider that uses the first line as the header for Section. It runs no action; writing critical logic in a comment does not do the work, the real blocks are still required. An empty comment is not added to the Lua at all, so it has no performance cost.

Pro

In professional macros COMMENT is a documentation discipline: put a "what this section does / why it exists" note at the top of every large group, a WARNING next to every dangerous/fragile block, and a TODO where work is unfinished. Explaining why a complex branch (TRUE/FALSE) exists saves whoever returns months later from re-deriving the macro. Leave temporary debug notes with COMMENT too, but review them before shipping — stale notes can mislead. Never bury logic in a comment alone: COMMENT provides context, it does no work.

Real-World Scenarios — Step-by-Step Recipes

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

Document the purpose of a long loop

1COMMENT: "This group retries until the page finishes loading."
2GROUP (infinite) + IMAGE + BREAK on the TRUE branch
3The note makes future maintenance far easier

Section headers and to-dos

1Comment (Section): "Login"
2Login blocks...
3Comment (TODO): "Add recovery for the error screen"
4Comment (Section): "Collect Reward"

Which Blocks to Pair With — Pro Combinations

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

+ GROUP

Put a purpose note at the head of complex groups to make the flow self-documenting.

+ TRY_CATCH

Explains why the error-recovery logic is needed; eases future maintenance.

+ SET_VARIABLE

Note what a variable is for and its unit (e.g. duration in ms).

+ CUSTOM_CODE

Explains in plain language what the inline Lua does; gives context to a non-coder user.

Common Mistakes and Fixes

Thinking COMMENT is a functional block; it generates no code and doesn't change execution flow.

"Hiding" critical logic only in a comment; without the real blocks the macro won't do that work.

Leaving stale/temporary debug notes in the shipped macro; outdated comments mislead later maintenance.

Pro Tips

Put a "what it does / why it exists" note at the top of every large group so the macro explains itself even months later.

Classify notes with the Comment Type (Note, Section, TODO, Warning); scanning the flow gets faster.

Explain why a complex branch exists; future-you or someone else won't have to re-derive the macro.

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 →

-- NOTE: Test comment

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 →