No-Code Workspace — Block Reference

Flow ControlBlock usage recipe

Return Value (RETURN)

Exits the current Lua scope with a value

Documented for app version 1.0.50Updated: October 2, 2026

What Does It Do?

The RETURN block exits the current generated Lua scope. Inside a group folder it returns the GROUP_CALL result early; in the main flow it ends the macro. The expression is sanitized as a safe Lua expression and dangerous multi-statement attempts are blocked.

When to Use?

Use when:

Returning a calculated value early from a group folder

Skipping later group steps after a decision point

Returning success or failure state from a shared group

Ending the main macro flow in a controlled way

How to Use?

"Add Block" → "Return Value (RETURN)"

Enter the return expression (for example: result, score + 1, nil)

Inside a Group Folder, choose "Has return value" in the folder settings so Call Group shows its Result Variable field

When RETURN runs, later blocks in the same scope do not run

Parameters

Return Expression

Safe Lua expression to return. Example: result, score + 1, nil

Parameter	Description
Return Expression	Safe Lua expression to return. Example: result, score + 1, nil

Example Usage

Scenario: Return early from a group

Group Folder: "Read Score"

OCR_VALUE → save into "score"

COMPARE: score > 0

TRUE branch: RETURN score

Later group blocks are skipped and GROUP_CALL receives the score

Combinations / Used With

COMBINATIONS:

OCR_VALUE + RETURN: Return a scanned value from a group

COMPARE + RETURN: Exit early based on a condition

TRY_CATCH + RETURN: Return a recovery result

GROUP_CALL + RETURN: Build reusable mini routines

Tip

Exits the current Lua scope with a value

Warnings / Cautions

WARNING:

RETURN in the main flow ends the macro

Outside a group folder it does not produce a GROUP_CALL result

Multiple Lua statements, semicolons, loadstring, require, and control-flow keywords are blocked

Empty expression behaves as nil

Validation warns about blocks left after RETURN in the same scope; they never run

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

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

Basic

RETURN ends the scope it is in with a value. Inside a Group Folder it returns the GROUP_CALL result early; in the main flow it ends the macro in a controlled way. In the Return Expression field you write the value to return (e.g. result, score + 1, nil). When RETURN runs, the later blocks in the same scope no longer run.

Advanced

RETURN’s behavior depends on context: inside a Group Folder it ends that folder early and hands the value back to GROUP_CALL; at the top level of the main flow it ends the macro. To receive the value in a GROUP_CALL variable, the folder needs "Has return value"; only then does the Result Variable field appear. The return expression is checked as a safe Lua expression: multiple statements, semicolons (;), loadstring, require and control-flow keywords are blocked, so you can return only a single expression. An empty expression behaves as nil. Validation warns about blocks left after RETURN in the same scope, because they never run.

Pro

RETURN is the piece that turns groups into real functions: after a decision point, skip the later steps and return a computed result early. Typical pattern: read a value with OCR_VALUE, check it with COMPARE, and on the TRUE branch RETURN the result — later group blocks are skipped and the caller reads it via groupCallResultVar. Return a success/failure state from a central group and branch on the caller side with a single COMPARE. Turn the single-statement limit into an advantage: spread complex logic across the group and return only the result in RETURN. In the main flow use RETURN as a deliberate "early, clean exit"; just be careful not to place it at the top level by accident and end the macro early.

Real-World Scenarios — Step-by-Step Recipes

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

Return early from a group

1Group Folder: "Read Score"
2OCR_VALUE → save into "score"
3COMPARE: score > 0
4On the TRUE branch: RETURN score
5Later group blocks are skipped; GROUP_CALL receives the score

Routine that returns a success/failure state

1Group Folder: "Do Login"
2IMAGE: search for the login-success screen
3On the TRUE branch: RETURN true
4On the FALSE branch (at the end): RETURN false
5On the caller side, evaluate the GROUP_CALL result with COMPARE

Which Blocks to Pair With — Pro Combinations

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

+ GROUP_CALL

Carries the RETURN value into GROUP_CALL's result variable; the group becomes a real function.

+ OCR_VALUE

Return a value read from the screen out of the group to build a computation function.

+ COMPARE

Exit early based on a condition; skip unnecessary steps after a decision point.

+ TRY_CATCH

Return a recovery result (e.g. false) from a single point.

Common Mistakes and Fixes

Writing multiple statements / semicolons / loadstring / require in the return expression; the sanitizer blocks these — return only a single expression.

Expecting a result while RETURN is actually in the main flow, not a Group Folder; in the main flow RETURN ends the macro, it doesn't produce a GROUP_CALL result.

Leaving the Return expression empty but expecting a specific value; an empty expression behaves as nil.

Pro Tips

Design groups like functions: spread the computation across the group and let RETURN return only the result; the caller reads from groupCallResultVar.

Use RETURN on the TRUE branch to skip later steps after a decision point; the flow gets shorter and clearer.

Return a true/false state from a central group; you get clean branching with a single COMPARE on the caller side.

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 →

do return 1 end

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 →