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 recipeNewv1.0.51
Repeat previous (REPEAT_PREVIOUS)
Repeats preceding blocks in the same sequence by count or duration
Documented for app version 1.0.51Updated:
Block Preview
Captured from the in-app Visual Builder block card in the English UI.
English UI
What Does It Do?
Place this marker after the blocks to repeat. It reruns them from the start of this section or from after an earlier block in the same sequence; the selected start block is excluded. After the repeats finish, execution continues with the block after the marker. The marker has no child or condition lanes.
When to Use?
1
Use it to repeat actions without moving them into a separate container, or to rerun a selected range within one branch.
How to Use?
1
Add the actions in order.
2
Add Repeat previous after them.
3
Choose the start of this section or after an earlier block.
4
Choose count or duration and set the repeat interval.
5
Count 1 means one additional pass by default. Enable Include the first pass when you want the count to mean the total.
Parameters
Start boundary
Start of this section, or after an earlier sibling in the same sequence. The selected block is excluded. Missing or out-of-scope anchors are rejected; the range is not silently widened.
Count and first pass
The default additional count 1 adds one pass. Additional count 0 is valid. With the first pass included, the count is the total and must be at least 1.
Duration and interval
Duration starts on the first effective marker visit. Duration 0 adds no pass. The interval is waited and the deadline rechecked before another pass; an action already running is not interrupted.
Units and bindings
Display units may be milliseconds or seconds; variables and Random ranges always use milliseconds. Count/duration and interval are captured once on the first effective marker visit of each invocation.
| Parameter | Description |
|---|---|
| Start boundary | Start of this section, or after an earlier sibling in the same sequence. The selected block is excluded. Missing or out-of-scope anchors are rejected; the range is not silently widened. |
| Count and first pass | The default additional count 1 adds one pass. Additional count 0 is valid. With the first pass included, the count is the total and must be at least 1. |
| Duration and interval | Duration starts on the first effective marker visit. Duration 0 adds no pass. The interval is waited and the deadline rechecked before another pass; an action already running is not interrupted. |
| Units and bindings | Display units may be milliseconds or seconds; variables and Random ranges always use milliseconds. Count/duration and interval are captured once on the first effective marker visit of each invocation. |
Example Usage
1
LOG A → LOG B → Repeat previous (defaults) → LOG C produces A B A B C. Selecting after block A instead produces A B B C. A total count of 1 with the first pass included adds no pass.
Combinations / Used With
1
The range can contain actions, conditions and Group Call. Repeat ranges may be nested or disjoint; crossing ranges are rejected. Count, duration and interval fields support variable or Random range bindings.
Tip
Verify the start boundary with small counts and LOG first. Duration mode does not time the initial pass; its budget starts when execution first actually reaches the marker.
Warnings / Cautions
1
The range must be nonempty and cannot jump into another branch or group. Duration is a cooperative limit: the current action completes rather than being interrupted. Even interval 0 yields at least 1 ms before a repeat. Break and Continue still target their actual enclosing loop; this marker does not create a new loop-control scope.
Step-by-Step Mastery: Basic → Advanced → Pro
The same block at three levels: a quick start, the real options, and professional techniques.
Basic
Leave the actions in their normal order and put Repeat previous after them. The default start is the beginning of this section. The default count 1 means one additional pass, so the actions run twice including the initial pass. Execution continues after the marker when it finishes. There is no separate child lane.
Advanced
Selecting an earlier block in the same sequence starts the repeat after that block; the selected block is excluded. Include the first pass changes the count into a total. In duration mode, the budget begins on the first effective marker visit; time spent on the initial pass is excluded. Count/duration and interval bindings are captured once there per invocation. Time variables and Random ranges use milliseconds even when the display uses seconds.
Pro
Ranges may be nested or disjoint, but may not partially cross. The marker cannot jump to a start outside its branch, group or saved group invocation. Restarting an outer range gives its contained repeat range a fresh invocation. Duration is cooperative: the current action completes, and an expired deadline after the interval prevents a new pass. Even interval 0 yields at least 1 ms. Break and Continue target their actual enclosing loop; the marker is not a new loop-control scope.
Real-World Scenarios — Step-by-Step Recipes
Small, reproducible examples that combine several blocks — build them straight into your own macro.
Observe an additional pass with LOGNewv1.0.51
- 1Add LOG A and LOG B.
- 2Add Repeat previous with its defaults after them.
- 3Add LOG C after the marker.
- 4Verify A B A B C.
- 5Enable the first pass and use total 1; verify A B C.
Exclude the selected start blockNewv1.0.51
- 1Arrange LOG A, LOG B, Repeat previous and LOG C.
- 2Choose after block A as the marker start.
- 3Use additional count 1.
- 4Verify A B B C; A must not run a second time.
Which Blocks to Pair With — Pro Combinations
This block is useful on its own — but it shines when paired with the right partners.
+ LOG / Set Variable
Observe the actual pass count and final value; start with small additional counts.
+ Group / Group Call
Rerun a group or group call in the same sequence. A marker outside a group cannot select a block inside it as its start.
+ Conditional branches
Place the marker inside the branch to execute. Keep its start among earlier siblings in that same branch.
Common Mistakes and Fixes
The default count is not a total. Additional count 1 gives two total passes. Enable Include the first pass when you want a total.
A missing start selection does not fall back to the section start. Choose a valid earlier start; do not silently widen the repeated range.
An expired duration does not forcibly stop a scan, wait or custom Lua operation already running. Split long work into smaller actions when shorter response times matter.
Troubleshooting: What the App Says → What to Do
Each row starts with the message the app shows or the block’s output, followed by what to do.
- Start block unavailable
- Choose an eligible earlier block in the same section. At least one block must remain between the selected block and the marker.
- Repeat ranges cross
- Move the starts so the ranges are fully nested or disjoint. Do not target another branch.
Pro Tips
Additional count 0 or duration 0 adds no new pass. A total count including the first pass must be at least 1.
The interval is a wait between repeats; it does not compensate for action execution time. Supply bound time values in milliseconds even with seconds displayed.
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.
do local _repeat_previous_close_guard = function() end end
local _repeat_previous_state = {{}}
::_repeat_previous_start::
System.log("repeat body")
_repeat_previous_state[1].again = false
if not _repeat_previous_state[1].armed then
_repeat_previous_state[1].interval = 0
_repeat_previous_state[1].remaining = (1) - 0
_repeat_previous_state[1].armed = true
end
_repeat_previous_state[1].again = _repeat_previous_state[1].remaining > 0
if _repeat_previous_state[1].again then _repeat_previous_state[1].remaining = _repeat_previous_state[1].remaining - 1 end
if _repeat_previous_state[1].again then
wait(math.max(1, _repeat_previous_state[1].interval))
if _repeat_previous_state[1].again then
goto _repeat_previous_start
end
endNote: 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.
Newv1.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.