No-Code Workspace — Block Reference

Flow ControlBlock usage recipeNewv1.0.51

Target Watch (TARGET_WATCH)

Rechecks a target while resuming work at the next action

Documented for app version 1.0.51Updated:

Block Preview

Captured from the in-app Visual Builder block card in the English UI.

English UI
Target Watch (TARGET_WATCH) block card

What Does It Do?

Add one or more blocks, groups or plugins to Target and Work. Target runs first, then after one work action, a chosen batch, or all work actions. Work resumes where it left off; group repeat cursors are not reset.

When to Use?

1

Use it to monitor a critical screen target while running a long or nested workflow.

How to Use?

1

Add Target Watch from Flow.

2

Add a scan and any outcome actions to Target.

3

Add actions or groups to Work.

4

Choose one action, a batch size, or all actions.

5

Set target repeat/time limits and work passes. In Logic, use the Target and Work sockets.

Parameters

Target count/time

1–1,000,000 repetitions or 1–86,400,000 ms. Each check runs the entire Target lane under this limit.

Work batch and passes

Every 1–1,000,000 actions or all actions; 1–1,000,000 work passes. Executed actions inside groups count; their container does not.

Timing and final check

A maximum check interval of 0 disables it; it is sampled at safe boundaries. Target pass spacing is 1–60,000 ms. Final check is on by default.

Example Usage

1

Target: LOG T. Work: LOG A, LOG B, LOG C. Batch 1 with final check: T → A → T → B → T → C → T. A twice-repeated nested group also keeps its own cursor.

Combinations / Used With

1

Use Image, Text or Color in Target; groups, group calls, conditions and plugins in Work. All five numeric settings support variable or Random range bindings.

Tip

Rechecks a target while resuming work at the next action

Warnings / Cautions

1

Checks run only at safe block boundaries. A running wait, scan retry or custom Lua body is not interrupted; a plugin counts as one action. Group duration includes time spent in target checks. An in-flight target pass finishes when its time expires. This is not a background thread.

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

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

Basic

Put the scan to monitor in Target and the actions to perform in Work. By default Target runs first and is rechecked after every work action. Work resumes at the next action.

Advanced

Increase the batch size to check after N executed work actions or choose All actions. Configure target repetition count or milliseconds independently. Work passes repeat the entire Work lane. Nested groups preserve their own counters and durations; their container is not counted as an action.

Pro

Checks occur at block boundaries; a long wait, scan retry or plugin body finishes before a check can intervene. The maximum interval is evaluated at those same boundaries. Group durations include target overhead. Existing monitors are muted while Target runs; a newly nested watch can run independently. Errors and Return unwind monitoring. Target scans restore Work’s pending match, motion and implicit OCR text; use named output variables to share target results. Break and Continue at a lane root affect its own loop; controls inside nested groups keep their scope.

Real-World Scenarios — Step-by-Step Recipes

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

Verify progress with logs
  1. 1Add LOG T to Target.
  2. 2Add LOG A, LOG B and LOG C to Work.
  3. 3Use batch size 1 and enable the final check.
  4. 4Verify T,A,T,B,T,C,T.
Repeat a nested group twice
  1. 1Add a twice-repeated Group to Work.
  2. 2Put LOG A and LOG B in the group.
  3. 3Put LOG T in Target and use batch size 1.
  4. 4Verify T,A,T,B,T,A,T,B,T; each check must not restart at A.

Which Blocks to Pair With — Pro Combinations

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

+ Image / Text / Color

Scan in Target and add outcome actions to its found/not-found branches. Work resumes when the check returns.

+ Group / Group Call

Inner actions are counted individually; call parameters and loop progress remain intact.

+ Plugins

A plugin body is one action. Split long work into separate blocks when more frequent checks are needed.

Common Mistakes and Fixes

The maximum interval is not a hard interruption deadline. A running action must finish before another check starts.

Do not leave Target or Work empty. These are not True/False conditional branches.

Pro Tips

Start with small repeat counts and LOG actions, then add scans on the actual device.

Use the bulb menu to bind limits to a variable or Random range; sampled values must stay within the field bounds.

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.

local __mh_target_watch_clock = Stopwatch(); __mh_target_watch_clock:start()
local __mh_target_watch_api = (function()
 local stack, mutedThrough = {}, 0
 local function now() return __mh_target_watch_clock:elapsedMs() end
 local function check(frame)
  local match, motion, ocr = _lastMatch, _lastMovingColorMotion, _lastOcrText
  local previous = mutedThrough
  mutedThrough = #stack
  local ok, signal, value = pcall(frame.target)
  mutedThrough = previous
  _lastMatch, _lastMovingColorMotion, _lastOcrText = match, motion, ocr
  if not ok then error(signal, 0) end
  frame.steps, frame.checked = 0, now()
  return signal, value
 end
 return {
  check = check, now = now,
  push = function(frame) stack[#stack + 1] = frame end,
  pop = function(frame) assert(stack[#stack] == frame); stack[#stack] = nil end,
  before = function(counted)
   for index = mutedThrough + 1, #stack do
    local frame = stack[index]
    if (frame.batch > 0 and frame.steps >= frame.batch) or
       (frame.interval > 0 and now() - frame.checked >= frame.interval) then
     local signal, value = check(frame)
     if signal ~= nil then return signal, value end
    end
    if counted then frame.steps = frame.steps + 1 end
   end
  end,
 }
end)()

do
 local _mh_watch_signal_1, _mh_watch_value_2 = __mh_target_watch_api.before(false)
 if _mh_watch_signal_1 == "__VB_RETURN__" then
  do return _mh_watch_value_2 end
 end
end
do
 local _mh_watch_frame_3 = {steps = 0, checked = 0, batch = 1, interval = 0}
 _mh_watch_frame_3.target = function()
  local _mh_watch_quota_6 = 1
  for _mh_watch_target_pass_8 = 1, _mh_watch_quota_6 do
   do
   do
    local _mh_watch_signal_9, _mh_watch_value_10 = __mh_target_watch_api.before(true)
    if _mh_watch_signal_9 == "__VB_RETURN__" then
     do return "__VB_RETURN__", _mh_watch_value_10 end
    end
   end
   System.log("target")
   ::_watch_cont_4::
   end
   if _mh_watch_target_pass_8 < _mh_watch_quota_6 then wait(8) end
  end
  ::_watch_exit_5::
 end
 __mh_target_watch_api.push(_mh_watch_frame_3)
 local _mh_watch_ok_11, _mh_watch_result_12, _mh_watch_return_13 = pcall(function()
  do
   local _mh_watch_signal_17, _mh_watch_value_18 = __mh_target_watch_api.check(_mh_watch_frame_3)
   if _mh_watch_signal_17 == "__VB_RETURN__" then
    do return "__VB_RETURN__", _mh_watch_value_18 end
   end
  end
  for _mh_watch_pass_14 = 1, 1 do
   local _mh_watch_work_signal_15, _mh_watch_work_value_16 = (function()
    do
     local _mh_watch_signal_19, _mh_watch_value_20 = __mh_target_watch_api.before(true)
     if _mh_watch_signal_19 == "__VB_RETURN__" then
      do return "__VB_RETURN__", _mh_watch_value_20 end
     end
    end
    System.log("work")
   end)()
   if _mh_watch_work_signal_15 == "__VB_RETURN__" then return _mh_watch_work_signal_15, _mh_watch_work_value_16 end
   if _mh_watch_work_signal_15 == "__VB_BREAK__" then break end
   if _mh_watch_frame_3.steps > 0 then
    do
     local _mh_watch_signal_21, _mh_watch_value_22 = __mh_target_watch_api.check(_mh_watch_frame_3)
     if _mh_watch_signal_21 == "__VB_RETURN__" then
      do return "__VB_RETURN__", _mh_watch_value_22 end
     end
    end
   end
   if _mh_watch_pass_14 < 1 then wait(8) end
  end
 end)
 __mh_target_watch_api.pop(_mh_watch_frame_3)
 if not _mh_watch_ok_11 then error(_mh_watch_result_12, 0) end
 do
  local _mh_watch_signal_23, _mh_watch_value_24 = _mh_watch_result_12, _mh_watch_return_13
  if _mh_watch_signal_23 == "__VB_RETURN__" then
   do return _mh_watch_value_24 end
  end
 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.

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.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

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_FILE
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.

2

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.

Learn more →