No-Code Workspace — Block Reference

Flow ControlBlock usage recipeComing soonv1.0.51

Time/Repeat gate (PHASE_GATE)

Chooses the True or False path by visit count or elapsed time

Documented for app version 1.0.51 (not on Google Play yet)Updated: October 2, 2026

Time/Repeat gate (PHASE_GATE) block card

What Does It Do?

Runs its internal actions for a visit count or time period. In the True phase, the internal actions run once, followed by the True branch. In the False phase, only the False branch runs. The block does not create an inner loop; the surrounding flow supplies later visits.

When to Use?

Use it to run a scan on 3 visits and a different action on 1 visit, or alternate two phases by time.

How to Use?

Add Time/Repeat gate from the Flow category.

For each phase, choose Visits, Milliseconds or Seconds as the unit and enter the limit.

Put the work in Internal actions (True phase) and the follow-up actions on the True and False branches.

Set Start with the True phase and Repeat after the False phase.

Use an outer loop for later visits.

Parameters

True/False unit and limit

Visits, Milliseconds or Seconds for each phase; the defaults are 3 visits True and 1 visit False. Limits are 1–1,000,000,000 visits, 1–604,800,000 ms or 1–604,800 seconds (7 days); supports variable and Random bindings.

Repeat and starting phase

Repeat after the False phase returns from False to True; Start with the True phase chooses the first phase. Both are on by default.

Internal actions and branches

Internal actions (True phase) run once, only in the True phase and before its True branch.

Parameter	Description
True/False unit and limit	Visits, Milliseconds or Seconds for each phase; the defaults are 3 visits True and 1 visit False. Limits are 1–1,000,000,000 visits, 1–604,800,000 ms or 1–604,800 seconds (7 days); supports variable and Random bindings.
Repeat and starting phase	Repeat after the False phase returns from False to True; Start with the True phase chooses the first phase. Both are on by default.
Internal actions and branches	Internal actions (True phase) run once, only in the True phase and before its True branch.

Example Usage

True: 3 visits. False: 1 visit. Repeat enabled, start with True. An Image block inside runs on visits 1, 2, and 3. Visit 4 runs only the False branch; visit 5 starts a new True phase.

Combinations / Used With

Use Image or Color inside. Bind limits to a variable or Random range through the lightbulb menu. The code editor provides PhaseGate.create, next, status, and reset.

Tip

Chooses the True or False path by visit count or elapsed time

Warnings / Cautions

Time is checked only on the next visit; an expired phase does not interrupt a running child action. The active limit is fixed at phase entry. With repeat disabled, the block stays in False. A new macro run resets its state. Limits must be positive integers.

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

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

Basic

Time/Repeat selects the True or False phase on each visit; it does not create a loop. The visual defaults select True for 3 visits, False for 1 visit, then repeat. In the True phase, Internal actions complete once before the True branch. The False phase runs only the False branch. An outer macro loop or existing flow supplies the next visit.

Advanced

Choose visit count, milliseconds, or seconds separately for each phase. Limits must be at least 1; the bulb menu supports a variable or a two-endpoint Random range. Timing starts on the first actual visit and is evaluated only when revisited; expiry does not interrupt an inner action already running. Each visit makes at most one phase transition. Configure Repeat after False and Start with True separately.

Pro

The active phase keeps the unit and limit captured on entry; a changed binding applies on the next phase entry. Restarting the macro resets run counters. In Lua, call PhaseGate.create once and retain the handle between visits; PhaseGate.next evaluates one visit. PhaseGate.status only reads without advancing the phase; PhaseGate.reset returns to the state before the first visit. Options passed to next or reset are a complete configuration, not a partial patch. API defaults are 1 True / 1 False; the visual block explicitly sends its 3 / 1 defaults.

Real-World Scenarios — Step-by-Step Recipes

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

Run 3 times and skip once

1Place Time/Repeat inside a bounded outer repetition.
2Set both units to visit count, with limits 3 and 1; enable repeating and starting with True.
3Add LOG to Internal actions and distinct LOG messages to the True and False branches.
4Across 8 visits, verify that the first 3 run Internal actions and True, the fourth runs only False, and the pattern repeats.

Evaluate a timed phase on revisit

1Set the True phase to seconds with a limit of 2 and the False phase to visit count with a limit of 1.
2Enable repeating and revisit the block through a controlled outer flow with a short Wait.
3After 2 seconds from the first visit, verify that the next visit selects False.
4If an inner action lasts longer than 2 seconds, do not expect it to be interrupted; the phase is evaluated on the next visit.

Which Blocks to Pair With — Pro Combinations

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

+ GROUP / outer loop

Revisits the phase gate; the gate itself does not create a repetition loop.

+ IMAGE / TEXT / COLOR

A scan inside Internal actions runs only during True. Treat scan success and phase selection as separate decisions.

+ LOG / variable / Random

Use LOG to check phase order; bound limits apply on the next phase entry without restarting the active phase.

Common Mistakes and Fixes

Do not enter 0 as a phase limit: the minimum is 1. Wait before/after are separate millisecond fields where 0 is valid.

Calling PhaseGate.create on every iteration restarts the counter. Retain the same handle between visits.

With repeating disabled, the gate stays in False; starting with False never advances to True. Enable repeating and check the outer flow when alternation is needed.

Pro Tips

Visit limits are 1–1,000,000,000; time limits are 1–604,800,000 ms or 1–604,800 seconds. Correct fractional, negative, unknown, or excessive values before running.

Logic uses the same phase editor: Internal actions live inside the node, while True/False paths use canvas connections. Verify with LOG that connections do not call an action twice.

PhaseGate.status returns these fields without advancing the phase: phase (nil before the first visit), visits (in the active phase), total (all visits), cycles (returns from False to True), mode, limit and elapsedMs; a timed limit is reported in milliseconds. Use it to log progress.

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 __mh_phase_gate_api = {create = PhaseGate.create, next = PhaseGate.next}
local __mh_phase_gate_state = {}

do
 local _mh_phase_config_1 = {trueMode="count", trueLimit=3, falseMode="count", falseLimit=1, repeatCycle=true, startWithTrue=true}
 __mh_phase_gate_state["00000000-0000-4000-8000-000000000001"] = __mh_phase_gate_state["00000000-0000-4000-8000-000000000001"] or __mh_phase_gate_api.create(_mh_phase_config_1)
 if __mh_phase_gate_api.next(__mh_phase_gate_state["00000000-0000-4000-8000-000000000001"], _mh_phase_config_1) then
  System.log("phase body")
  System.log("true phase")
 else
  System.log("false phase")
 end
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 →