No-Code Workspace — Block Reference

Flow ControlBlock usage recipe

Event State (EVENT_STATE)

Switches groups and selected blocks on or off at runtime

Documented for app version 1.0.50Updated: October 2, 2026

What Does It Do?

Controls whether Group Folders and individual blocks you pick may run while the macro runs. Every group has an event key (the group name when empty). Later GROUP_CALL gates skip a disabled folder, and a disabled target block is skipped when the flow reaches it.

When to Use?

Keep a group off until a slow screen is ready

Turn on a recovery group on an error or disconnect screen

Keep only one phase’s group enabled at a time

How to Use?

In the Event State section of the Group Folder settings set the event key and "Enabled / Disabled when macro starts"

Add Event State; action: Enable, Disable, Toggle, Reset or Enable only

With Selected groups as target mode, pick from Target groups and Target blocks; add optional custom target keys

Optionally choose a Fail-safe recovery group: it runs when every known folder is disabled

Parameters

Event State action

Enable, Disable, Toggle, Reset, Enable only (enable / disable / toggle / reset / enable_only)

Targets

Selected groups (Target groups, Target blocks, custom keys) or All groups

Fail-safe recovery group

The group that runs when every known Group Folder is disabled

Event key and start state

Set on the Group Folder: the Group Event key (empty = group name) and Enabled on start

TimingComing soonv1.0.51

Override dialog selection, Apply after (ms) and Restore previous state after (ms; 0 = no expiry); times 0–604,800,000 ms (7 days)

Parameter	Description
Event State action	Enable, Disable, Toggle, Reset, Enable only (enable / disable / toggle / reset / enable_only)
Targets	Selected groups (Target groups, Target blocks, custom keys) or All groups
Fail-safe recovery group	The group that runs when every known Group Folder is disabled
Event key and start state	Set on the Group Folder: the Group Event key (empty = group name) and Enabled on start
TimingComing soonv1.0.51	Override dialog selection, Apply after (ms) and Restore previous state after (ms; 0 = no expiry); times 0–604,800,000 ms (7 days)

Release Notes

Coming soonv1.0.51
Three new fields: Override dialog selection (an enabled target may run even when its start-dialog condition is not met; the saved choice is unchanged), Apply after (ms) and Restore previous state after (ms; 0 = no expiry).
Coming soonv1.0.51
Times are capped at 7 days. A new command for the same target cancels its earlier timing, and Reset also clears the dialog override; the timers belong to the macro and reset when it ends.
Coming soonv1.0.51
Example: to run a block that is unchecked in the start dialog for 5 seconds, use Enable, Target blocks: that block, Override dialog selection on, Apply after 0, Restore previous state after 5000. The saved choice is unchanged; after 5 seconds the block returns to its normal condition.

Example Usage

Set the "Reconnect" Group Folder to Disabled when macro starts; the Call Group in the main flow skips it while it is off

If IMAGE finds the "Connection lost" screen, its TRUE branch runs Event State: Enable, Target groups: Reconnect

The next Call Group runs the folder; an Event State: Reset at the end of the folder returns it to its disabled start state

Combinations / Used With

IMAGE + EVENT_STATE + GROUP_CALL: enable and run a group when a screen event appears

EVENT_STATE (Enable only): only the current phase’s group stays enabled

TRY_CATCH + EVENT_STATE: on a caught error, disable the main group and enable recovery

Tip

Switches groups and selected blocks on or off at runtime

Warnings / Cautions

Reset returns a group to its start state; it does not always enable it

Enable only and All groups cover Group Folders only, not individual blocks

Event State only affects later runs of a target; it does not cut off a group that is already running

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

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

Basic

Event State (EVENT_STATE) is a switchboard that controls whether Group Folders and individual blocks you pick may run while the macro runs. Each folder’s settings have an event key (the group name when empty) and an "Enabled / Disabled when macro starts" choice. The block changes these keys with Enable, Disable, Toggle, Reset and Enable only. A later GROUP_CALL skips a disabled folder, and a disabled block chosen under Target blocks is skipped when the flow reaches it.

Advanced

Target mode is Selected groups or All groups; All groups covers Group Folders only. With selected groups you pick from the Target groups and Target blocks lists and can add comma-separated custom target keys. A GROUP block can be a target block too; its start state is chosen in its own settings. Reset returns a target to its start state rather than always enabling it. Enable only disables every known folder and enables only the selected ones; it does not disable other individual blocks. If you choose a Fail-safe recovery group, it runs when every known folder ends up disabled, once for the same all-off state. Event State only affects later runs of a target: it does not cut off a group that is already running, and a disabled folder is skipped at the next GROUP_CALL.

Pro

With Event State you switch branches at runtime without rewriting the flow, so a linear macro follows what is on screen. Recovery pattern: on a disconnect or error screen disable the main group, enable the recovery group, and flip back once it is fixed; a Fail-safe recovery group does this by itself when everything is switched off. Enable only builds a phase machine: in each phase only that phase’s group stays enabled. For stability use a fixed event key, not the name.

Real-World Scenarios — Step-by-Step Recipes

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

Keep the validation group disabled until its screen appears

1Group Folder "Validation": event key validation_phase, Disabled when macro starts
2IMAGE: search for the icon on the validation screen
3On TRUE: Event State → Enable, target: Validation
4GROUP_CALL: Validation (now runs)
5If an error screen appears: Event State → Disable, target: Validation

Phase machine with enable_only

1Three folders: main_phase, validation_phase, idle_phase (event keys set)
2When the validation screen appears: Event State → Enable only, target: validation_phase (the other folders switch off)
3When validation ends: Enable only, target: main_phase
4In each phase only the matching GROUP_CALL runs; the others are skipped and logged

Run a block that is unchecked in the start dialog for 5 secondsComing soonv1.0.51

1Add Event State → action: Enable, Target blocks: that block
2Override dialog selection: on
3Apply after (ms): 0
4Restore previous state after (ms; 0 = no expiry): 5000
5The saved dialog choice is unchanged; after 5 seconds the block returns to its previous state

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

Group targets take effect at the next GROUP_CALL: a disabled folder is not called.

+ IMAGE / TEXT

When a screen event (button/text) appears you enable the matching group and bring it online.

+ TRY_CATCH

On a caught error, disable the main group and enable the recovery group; you build automatic recovery.

+ GROUP (Group Event key)

The event key and start state in the folder settings decide what the Event State block switches.

+ LOG

Log which state change happened and follow the flow with Execution Trace.

Common Mistakes and Fixes

Confusing group targets with block targets: a group target affects calls to the folder through GROUP_CALL; to switch off a single block, pick it in the Target blocks list.

Calling a folder that is disabled when the macro starts without running Enable first; the call is skipped and only written to the log.

Assuming Reset always switches the group on; it returns it to its start state. Use Enable to be sure it is on.

Mistyping a custom target key; validation warns and the expected group is not enabled. Pick targets from the lists whenever you can.

Coming soonv1.0.51Sending a second Event State command to the same target shortly after the first: the new command cancels the older timer, so the first command’s restore time never applies.

Pro Tips

Recovery pattern: on an error or ad screen Disable the main group, Enable the recovery group, and flip back once it is fixed.

Build a phase machine with Enable only; in each phase keep only that phase’s folder enabled.

Give the folder a fixed event key; your Event State logic survives a folder rename.

Coming soonv1.0.51Apply after and the restore time range from 0 to 604,800,000 ms (7 days); the restore time counts from when the change is applied, and the change is checked when the target is reached. Reset restores the normal dialog rules; saved selections are not changed.

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_event_state = {}
local __mh_event_recovery_running = false
local __mh_event_default_state = {
}
local __mh_event_known_keys = {
}
local function __mh_event_key(raw)
 local key = tostring(raw or "")
 if key == "" then return nil end
 return key
end
local function __mh_event_is_enabled(raw)
 local key = __mh_event_key(raw)
 if key == nil then return true end
 if __mh_event_state[key] ~= nil then return __mh_event_state[key] ~= false end
 return __mh_event_default_state[key] ~= false
end
local __mh_event_recovery_fired = false
local function __mh_event_set(raw, enabled)
 local key = __mh_event_key(raw)
 if key ~= nil then __mh_event_state[key] = enabled and true or false end
 if enabled then __mh_event_recovery_fired = false end
end
local function __mh_event_toggle(raw)
 local key = __mh_event_key(raw)
 if key ~= nil then __mh_event_state[key] = not __mh_event_is_enabled(key) end
 if key ~= nil and __mh_event_state[key] then __mh_event_recovery_fired = false end
end
local function __mh_event_reset(raw)
 local key = __mh_event_key(raw)
 if key ~= nil then __mh_event_state[key] = nil end
 if key ~= nil and __mh_event_is_enabled(key) then __mh_event_recovery_fired = false end
end
local function __mh_event_all_disabled()
 local has_known = false
 for key, _ in pairs(__mh_event_known_keys) do
  has_known = true
  if __mh_event_is_enabled(key) then return false end
 end
 return has_known
end

__mh_event_set("Utility", false)

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 →