No-Code Workspace — Block Reference

SystemBlock usage recipe

Metrics (METRICS)

Measures and summarizes operation timings

Documented for app version 1.0.50Updated: October 2, 2026

What Does It Do?

Enable starts measuring (off by default): for each tracked operation it collects the count and the average, minimum, maximum and total time (ms). Read Summary writes this table as text into a variable.

When to Use?

Use it to find which step spends the time, or to compare timings before and after a change.

How to Use?

Add METRICS → Enable at the start of the flow

Run the blocks to measure

METRICS → Read Summary (default variable runtime_metrics)

Print it with LOG "{{runtime_metrics}}"; Reset or Disable when done

Parameters

Action

Read Summary, Enable, Disable, Reset

Result Variable

Summary table (default runtime_metrics)

Parameter	Description
Action	Read Summary, Enable, Disable, Reset
Result Variable	Summary table (default runtime_metrics)

Example Usage

Enable → GROUP (IMAGE + CLICK, 20 times) → Read Summary → LOG → Reset

Combinations / Used With

COMBINATIONS:

METRICS + LOG: Show the summary in the panel

METRICS + FILE_WRITE: Save the summary to a file

Tip

Measures and summarizes operation timings

Warnings / Cautions

WARNING:

Until Enable has run, the summary only reports that no metrics were collected

Measurements live in memory; use FILE_WRITE to keep them

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

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

Basic

METRICS manages the performance metrics the macro gathers while it runs. The most common action is summary: it writes the current metric snapshot into a result variable so you can display it with LOG. With no action chosen, the default behavior is to produce a summary. Measuring is off by default; until enable runs, the summary only reports that no metrics were collected.

Advanced

METRICS supports four actions: summary (read the current metric snapshot), enable (turn collection on), disable (turn collection off) and reset (zero the counters). The summary action needs a result variable (default runtime_metrics); the generated code calls Metrics.summary() and assigns it to that variable. The summary is a text table, sorted by total time, that shows the count and the average, minimum, maximum and total time (ms) for each operation the app tracks. The enable/disable/reset actions are side-effects and return no value; reset clears what was collected and restarts the session clock.

Pro

Long-run monitoring pattern: METRICS reset at the start of a loop, then METRICS summary → LOG after the critical section, giving you a clean performance window per iteration. To measure an expensive stage (say a heavy OCR or image-search section) while suppressing noise elsewhere, disable outside it and enable inside it. Bind the summary to a HUD_OVERLAY text field with the lightbulb to show a performance panel on screen without pausing the macro. Taking a summary inside TRY_CATCH and logging it in the catch branch is a tidy way to capture state at the moment of failure.

Real-World Scenarios — Step-by-Step Recipes

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

Per-iteration performance window

1GROUP (infinite loop)
2METRICS → action=reset
3... heavy work (IMAGE, OCR_VALUE) ...
4METRICS → action=summary, result=stats
5LOG: "Iteration stats: {{stats}}"
6WAIT 1000ms

Measure only the critical section

1METRICS → action=disable
2... irrelevant setup ...
3METRICS → action=enable
4... the section you want to measure ...
5METRICS → action=summary, result=stats
6LOG {{stats}}

Which Blocks to Pair With — Pro Combinations

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

+ LOG

Surfaces the summary output in the control panel, the most direct way to read metrics.

+ HUD_OVERLAY

Displays the summary on screen as a live performance panel, no need to pause the macro.

+ TRY_CATCH

Lets you capture and log the metric state at the moment of failure in the catch branch.

+ GROUP

reset at the loop start + summary at the end gives an isolated measurement window per iteration.

Common Mistakes and Fixes

Not giving summary a result variable. Without it you cannot use the value you read. Fix: fill the result variable and consume it with LOG/COMPARE.

Placing reset in the wrong spot. Resetting AFTER the summary wipes that iteration's data before you read it. Fix: put reset at the START of the window and summary at the END.

Forgetting enable after a disable. If collection stays off, the next summary only reports that no metrics were collected, or shows old values. Fix: call enable before the section you want to measure.

Pro Tips

Since the summary is a value, wrapping it in tostring() to build one readable LOG line is handy.

Once performance hunting is done, remove the METRICS blocks or leave them disabled; needless measurement is itself a small cost.

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

runtime_metrics = Metrics.summary()

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.

⚙️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.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 →