No-Code Workspace — Block Reference

Flow ControlBlock usage recipe

Wait (WAIT)

Waits for a set duration

Documented for app version 1.0.50Updated: October 2, 2026

What Does It Do?

Pauses the macro for the duration you enter, in milliseconds: 1000 ms = 1 second. Use it between steps to let an animation finish, a page load or a server respond.

When to Use?

Let a page load or an animation finish after a tap

Allow for a server’s response time

How to Use?

Enter the time in Wait Duration (ms) (1000 = 1 second)

To take the duration from a variable, tap the field’s lightbulb and pick the variable

Parameters

Wait Duration (ms)

1000 = 1 second. Can be bound to a variable with the lightbulb

Parameter	Description
Wait Duration (ms)	1000 = 1 second. Can be bound to a variable with the lightbulb

Release Notes

Coming soonv1.0.51
The Wait Duration lightbulb menu adds a Random option: enter two bounds (for example 1000 – 3000) and the block picks a new duration from that range every time it runs.
Coming soonv1.0.51
Newly added tap, swipe, search, system and loop blocks start with Wait After = 50 ms; saved blocks keep their values. That field is separate from the WAIT block.

Example Usage

CLICK → WAIT 2000 ms → confirm the expected screen with IMAGE

From a variable: ask for the duration with DIALOG (key delay) and bind Wait Duration to delay with the lightbulb

Combinations / Used With

CLICK + WAIT: tap, then let the interface respond

SYSTEM + WAIT: open an app and let it load

Tip

Waits for a set duration

Warnings / Cautions

When you wait for something to appear, the IMAGE or TEXT retry mode that waits until it is found is usually more reliable than a fixed wait

A duration of 0 does not wait

This block is separate from the Wait Before / Wait After fields on tap, swipe, search and loop blocks

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

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

Basic

WAIT pauses the macro for the duration you enter. The value is in milliseconds (ms): 1000 = 1 second, 5000 = 5 seconds. The most common use is to let a page or animation settle after a CLICK.

Advanced

Wait Duration (ms) is the only field; instead of a fixed number you can bind a variable with the field’s lightbulb. That lets you feed a bounded test delay produced by RANDOM_NUMBER (delayMs) straight into WAIT. A duration of 0 does not wait. WAIT is deliberately a fixed delay: when you need to wait for something to appear, use the IMAGE/TEXT retry mode that waits until it is found, because it adapts to load times that vary from device to device.

Pro

In professional flows keep fixed WAITs to a minimum: every fixed wait is either too short and hurts stability, or too long and slows the macro. To calibrate, ask for the duration once with DIALOG, keep it in a variable and bind your wait fields to it with the lightbulb; you tune the whole rhythm from one place. When you need a real clock gate (waiting until a specific time), SLEEP_UNTIL is the right tool, not WAIT; WAIT is for relative, short pauses.

Real-World Scenarios — Step-by-Step Recipes

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

Click, settle, verify

1CLICK the button
2WAIT 2000ms for the page to load
3Verify the expected screen with IMAGE

Test load delays with a variable

1RANDOM_NUMBER -> min=1500, max=3500, resultVar=delayMs
2WAIT -> bind the Wait Duration field to delayMs with the lightbulb
3The next CLICK runs with slightly different timing each round

Random wait in one blockComing soonv1.0.51

1Add WAIT → tap the Wait Duration field’s lightbulb → Random
2Enter Minimum: 1500 and Maximum: 3500
3The block picks a new duration from that range every time it runs; no separate RANDOM_NUMBER block is needed

Which Blocks to Pair With — Pro Combinations

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

+ CLICK

The most common pair: click, then give the UI a short breath to respond.

+ SWIPE

After a swipe it waits out the transition animation, preventing a tap at the wrong position.

+ RANDOM_NUMBER

Binding the duration to a random variable tests the UI across a controlled delay range; keep the minimum and maximum bounded.

+ IMAGE (waitUntilFound)

In most cases it replaces WAIT: instead of a fixed delay it waits intelligently until the target appears.

Common Mistakes and Fixes

Using a fixed WAIT for every delay. Fix: when waiting for something on screen, prefer the IMAGE/TEXT 'wait until found' mode; keep WAIT only for genuinely fixed delays.

Giving the WAIT block a very short duration so the following check fails. Fix: measure on the target device and leave a reasonable margin. This duration is separate from the Wait After field on tap, swipe and search blocks.

Leaving the duration at 0 and wondering why it does not wait. Fix: 0 means do nothing; enter a positive ms value.

Pro Tips

Bind your wait durations to a single variable (read it from a persistent key with KV_GET if you like); when the device changes you recalibrate the whole macro by tuning one value.

Replace long fixed waits (e.g., over 30s) with a loop plus an IMAGE check; you exit faster and catch stalls earlier.

Coming soonv1.0.51The lightbulb’s Random option picks its own value for each WAIT. When several blocks must share the same random duration, generate it once with RANDOM_NUMBER into a variable and bind the wait fields to that variable.

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 →

wait(200)

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 →