No-Code Workspace — Block Reference

SystemBlock usage recipe

Continue (CONTINUE)

Skips to the next loop pass

Documented for app version 1.0.50Updated: October 2, 2026

What Does It Do?

Skips the rest of the current pass and moves to the next pass of the nearest loop; unlike Break it does not end the loop. In While and Repeat Until the next pass starts with the condition check. Loops are: For Each, While, Repeat Until, a Group or If / Else with its loop on, a looping Group Folder and the main flow’s repeat setting.

When to Use?

Skip empty items in a list

Skip the work on passes where a condition does not hold

How to Use?

Add a condition block inside the loop and put Continue on the branch that should skip

Example Usage

For Each: list rows, item row → Compare row == "" → TRUE branch: Continue

Combinations / Used With

FOR_EACH + COMPARE + CONTINUE: filter items

Tip

Skips to the next loop pass

Warnings / Cautions

A Continue outside any loop is a validation error

In While or Repeat Until, run the step that advances the condition before Continue, or the loop never moves on

Blocks after Continue do not run in that pass

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

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

Basic

CONTINUE skips the REST of the current loop turn and jumps straight to the next turn. Unlike BREAK it does not end the loop, it just short-circuits this turn. It is used to skip the current element's/turn's operations under a condition — e.g. passing over empty elements in a list. Like BREAK it is not standalone; it must sit in a branch of a CONDITION BLOCK so the skip only happens when the condition is met.

Advanced

CONTINUE affects only the NEAREST loop: it skips the rest of the pass and the loop goes on with the next pass; in While and Repeat Until the next pass starts with the condition check. Loops are: For Each, While, Repeat Until, a GROUP or If / Else with its loop on, a looping Group Folder and the main flow’s repeat setting. The block list offers CONTINUE only inside a loop; a CONTINUE outside any loop is a validation error. Its strongest use with FOR_EACH is filtering: check the item with COMPARE and skip unsuitable ones with CONTINUE, so steps like HTTP or CLICK run only for suitable items.

Pro

Use CONTINUE like a guard clause: at the top of the turn weed out invalid/skip-worthy cases with COMPARE + CONTINUE, so the rest of the body works only on clean data and you avoid nested IFs. Caution: inside WHILE/REPEAT_UNTIL, if CONTINUE also skips the SET_VARIABLE that advances the condition, it can cause an infinite loop — increment the counter BEFORE the CONTINUE so your turn counter always advances. In a many-element FOR_EACH, filtering with CONTINUE and then collecting passing elements into a separate result list yields a clean map/filter pattern. Place the pacing WAIT that must run at the very top of the turn, otherwise skipped turns bypass the WAIT and create a busy loop.

Real-World Scenarios — Step-by-Step Recipes

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

Skip empty elements in a list

1FOR_EACH: list=rows, element=row, index=i
2COMPARE: row == ""
3TRUE branch: CONTINUE (skip empty)
4... rest of operations run only for non-empty rows

Skip a turn in WHILE while preserving the counter

1SET_VARIABLE: i = 0
2WHILE: i < 50
3SET_VARIABLE: i = i + 1 (increment BEFORE the CONTINUE)
4WAIT 300ms (pacing at the top of the turn)
5COMPARE: state == "pending" → TRUE: CONTINUE
6... real work only on non-"pending" turns

Which Blocks to Pair With — Pro Combinations

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

+ FOR_EACH

The standard way to filter elements; skips non-qualifying ones and applies expensive operations only to those that pass.

+ COMPARE

Sets the skip condition; it is the inseparable partner since CONTINUE must sit in a condition branch.

+ SET_VARIABLE

By incrementing the counter before CONTINUE in WHILE/REPEAT_UNTIL it guarantees the loop advances even on skipped turns.

+ WAIT

Putting the pacing WAIT at the top of the turn rests the CPU even on skipped turns; otherwise CONTINUE creates a busy loop.

Common Mistakes and Fixes

Putting the counter increment AFTER CONTINUE in WHILE/REPEAT_UNTIL. Fix: do the SET_VARIABLE increment BEFORE CONTINUE, otherwise skipped turns never advance the counter and you get an infinite loop.

Putting the pacing WAIT after CONTINUE. Fix: move WAIT to the top of the turn; otherwise skipped turns run with no delay and create a busy loop.

Using CONTINUE unconditionally. Fix: put CONTINUE on a COMPARE branch; an unconditional CONTINUE pointlessly skips every pass. A CONTINUE outside any loop is rejected by validation.

Pro Tips

Use CONTINUE as a guard clause: weed out invalid cases at the top of the turn, getting a flat, readable body instead of nested IFs.

No block runs in the same turn after CONTINUE; so put steps needed every turn (log/counter) BEFORE the skip check.

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 items = {10, 20}

local _foreach_list_1 = items
if type(_foreach_list_1) ~= "table" then
 if System and System.log then System.log("FOR_EACH skipped: list variable 'items' is not a table") end
 _foreach_list_1 = {}
end
for index, item in ipairs(_foreach_list_1) do
 goto _cont_2
 ::_cont_2::
end
::_break_3::

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 →