1
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.
No-Code Workspace — Block Reference
SystemBlock usage recipe
Log (LOG)
Logs messages for monitoring
Documented for app version 1.0.50Updated:
Block Preview
Captured from the in-app Visual Builder block card in the English UI.
English UI
What Does It Do?
Records a message that appears in the control panel while the macro runs. Variables are added with the {{ }} template. The basic tool for debugging and flow monitoring.
When to Use?
1
Use for:
2
Tracking which step the macro is at
3
Checking variable values
4
Finding where a problem is
How to Use?
1
"Add Block" → "Log (LOG)"
2
Type the message; use {{ variable }} for variables, e.g. Counter: {{counter}}
3
The inside of the double braces is a Lua expression: {{ counter * 2 }}
4
You can bind the field to a variable with the lightbulb to log its whole value
Parameters
Message
Text with {{ expression }} template or lightbulb binding
| Parameter | Description |
|---|---|
| Message | Text with {{ expression }} template or lightbulb binding |
Example Usage
1
Scenario: Loop monitoring
2
GROUP (10 times)
3
... operations ...
4
LOG: "Turn {{counter}} / 10 complete"
Combinations / Used With
1
COMBINATIONS:
2
LOG in the TRY_CATCH Catch branch to record errors
3
LOG in COMPARE branches to see which path ran
4
OCR_VALUE + LOG: Verify read values
Tip
Logs messages for monitoring
Warnings / Cautions
1
WARNING:
2
Lua concatenation outside {{ }} ("Counter: " .. counter) is not evaluated; it is logged as text
3
Too many LOGs hurt performance
Step-by-Step Mastery: Basic → Advanced → Pro
The same block at three levels: a quick start, the real options, and professional techniques.
Basic
LOG records a message while the macro runs; the messages appear in the control panel. It is the most basic tool for tracking which step the macro is at, checking variable values, and answering "is my macro running?". It is the backbone of debugging.
Advanced
Type your text in the Message field. You can include a variable value two ways: type {{ variable }} inside the message (e.g. Counter: {{counter}}) or bind the whole field to a variable with the lightbulb. The inside of the double braces is a Lua expression, so {{ counter * 2 }} works too. Lua concatenation written outside the braces ("Counter: " .. counter) is not evaluated; it is printed as plain text. That gives you meaningful trace lines like "Turn {{round}} / 10, state: {{state}}". An empty message logs an empty line. LOG slots in without disrupting the flow, so you can place it before/after any block to see what really happens — especially to learn which branch a COMPARE took or what an OCR_VALUE read.
Pro
LOG is cheap but not free: logging hundreds of lines on every turn of a tight loop (REPEAT/FOR_EACH) hurts performance and panel readability. Use it freely while debugging, but remove unnecessary logs when done or reduce them to key milestones. Always place a LOG in the Catch branch of TRY_CATCH and write the error message ({{error}} or the caught variable) — silent failure is the worst kind of bug. Never log secrets (tokens, personal data); logs can be shared. For structured tracing, pack several fields onto one line ("step=fetch ok={{ok}} n={{count}}") — easier to scan or filter afterward. If you need a summary of operation timings, consider the METRICS block.
Real-World Scenarios — Step-by-Step Recipes
Small, reproducible examples that combine several blocks — build them straight into your own macro.
Track loop progress
- 1GROUP or REPEAT (10 times)
- 2... operations ...
- 3LOG: "Turn {{counter}} / 10 complete"
- 4Watch each turn land in the panel to spot a stall
Make a silent failure visible
- 1HTTP_REQUEST → API call, result: http_result
- 2IF_ELSE → is http_result_code == 200?
- 3If yes: LOG "Request OK, reply: {{http_result}}"
- 4If not: LOG "Request FAILED (code {{http_result_code}}): {{http_result}}"
Which Blocks to Pair With — Pro Combinations
This block is useful on its own — but it shines when paired with the right partners.
+ IF_ELSE
Branches on http_result_code and makes the failure visible with LOG; since the block never throws, this is the only antidote to silent loss.
+ COMPARE
Logs which branch ran so you confirm the comparison produced the result you expected.
+ OCR_VALUE
Surfaces the raw read value so you see what OCR actually produced and catch misreads.
+ SET_VARIABLE
Logs a variable's final value after a calculation or assignment, proving the logic ran correctly.
+ METRICS
Complements LOG lines with a per-operation count and timing summary, so you see which step takes the time.
Common Mistakes and Fixes
Logging on every turn of a tight loop. Hundreds of lines hurt performance and clutter the panel. Fix: log only key milestones, or remove logs once debugging is done.
Logging secrets (tokens, personal data). Logs can be shared and leaked. Fix: never put sensitive values in the message; if needed, show a masked/truncated form.
Leaving the Catch branch empty and not logging the error. The failure vanishes silently and you can't trace it. Fix: put LOG "... {{error}}" in every Catch.
Pro Tips
Pack several fields onto one line ("step=fetch ok={{ok}} n={{count}}"); it's far easier to scan or filter afterward.
Clean up unnecessary logs when debugging is done; in a production macro keep logs few and meaningful so the panel stays readable and performance holds.
To see how long each operation takes, enable METRICS and read its summary; LOG is for momentary tracing.
This Block's Code (Editor View)
LuaThe 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.
System.log("ok")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.
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.
⚙️Command Type
SYSTEM and PANEL_CONTROL first choose a command type; the rest of the fields only make sense in that context.
🧾Argument Semantics
arg1/arg2 or panel fields do not mean the same thing across every command; fill them according to that command.
🧪Dry-Run Thinking
Testing risky system actions with LOG or NOTIFY before going live makes builder flows safer.
🕒Synchronization Waits
Add short waits after app launches, panel state changes, or settings-navigation steps.
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.releaseAfterBounded 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.builderDialogHudTextViewAgentDetectEditorNavigationEditorAdvanced 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_CODEGeneral 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.
MapArrayJSONRegexMetricsLow-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_CODEDebug 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
1
Variables defined with SET_VARIABLE are accessible throughout the macro (global scope). All blocks can read/write the same variable.
2
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.
3
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.
4
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.
5
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
1
Keep scan regions as small as possible — improves speed, reduces false matches.
2
Always add an exit condition when using infinite loops (BREAK, timeout, or conditional exit).
3
Use network operations and error-prone steps inside TRY_CATCH.
4
If you need global error handling, use the Error Handler (ERROR_HANDLER) block as a singleton in the project.
5
Small coordinate offsets (CLICK/SWIPE) improve tap accuracy across different DPI and screen scales.
6
Customize macros with Dialog block — different parameters each run.
7
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_FILE2
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.
3
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.
4
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.