No-Code Workspace — Block Reference

Data and UtilitiesBlock usage recipe

KV Write (KV_SET)

Writes data into local key-value storage

Documented for app version 1.0.50Updated: October 2, 2026

What Does It Do?

Writes small persisted values to local key-value storage. It is the main builder-side persistence block for flags, counters, cached state, and user preferences.

Pro note: treat KV writes as checkpoints

KV_SET does more than save data. It records that a stage completed, a counter moved, or a final decision was made. Name keys around events, not vague generic labels.

When to Use?

Use it to:

Mark that a first-run step has been completed

Update counters

Save the last seen item, ID, or page

Carry new state into future runs

How to Use?

Add KV_SET

Enter the key name to persist

Fill the Value field with fixed text or a {{ variable }} template, or bind it with the lightbulb

Read it later with KV_GET when needed

Parameters

Key

Key name to persist

Value

Fixed text or a {{ variable }} template; it is stored as text, so use tonumber() when reading a number back

Parameter	Description
Key	Key name to persist
Value	Fixed text or a {{ variable }} template; it is stored as text, so use tonumber() when reading a number back

Example Usage

Scenario: Store the last successful order number

Read the order number with OCR_VALUE or TEXT

KV_SET -> key = last_order_id, value = {{orderId}}

Reuse it later with KV_GET

Combinations / Used With

COMBINATIONS:

KV_SET + KV_GET: persistent state management

KV_SET + RANDOM_NUMBER: store counters or seeds

KV_SET + ERROR_HANDLER: keep the last error state

Tip

Use stable key names that will survive future workflow changes. Good key naming reduces maintenance cost.

Warnings / Cautions

WARNING:

Do not persist sensitive data here unnecessarily

Reusing the same key for different data types will make the flow brittle

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

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

Basic

KV_SET writes a small persisted value into local key-value storage. You provide a Key name and a Value; the value can be fixed text or a {{ variable }} template, or you can bind the field to a variable with the lightbulb. You read the same key back later with KV_GET to carry state across runs.

Advanced

It has two fields: Key (the name to persist) and Value (fixed or {{ variable }}-driven content). The generated code calls KV.set("key", "value"); text you type, with or without a template, is stored as text. The Value field supports templates like {{orderId}}, letting you embed other variables so a dynamic value read from OCR/TEXT is persisted in one step. This is the main builder-side persistence block: first-run flags, counters, last-seen item/ID, and a simple cache layer.

Pro

It is the write end of the read-modify-write loop: read state with KV_GET, update it with SET_VARIABLE, write it back with KV_SET. Keep flag lifecycles idempotent — e.g. write has_seen_intro=true once onboarding finishes so it never repeats. Since a value you type is stored as text, be type-aware on read-back (tonumber for numbers, "true"/"false" comparison for flags). Do not keep secrets (tokens, OTPs, passwords) here needlessly; the store persists on the device. Always use one key with one data type; mixing types breaks the flow.

Real-World Scenarios — Step-by-Step Recipes

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

Store the last successful order number

1Read the order number with OCR_VALUE or TEXT → orderId
2KV_SET → key=last_order_id, value={{orderId}}
3Reuse it next session with KV_GET → last_order_id

Set a first-run flag

1KV_GET → key=has_seen_intro, default=false, result=seen
2COMPARE: seen == false → run onboarding
3After onboarding, KV_SET → has_seen_intro = true

Which Blocks to Pair With — Pro Combinations

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

+ KV_GET

The other half of persistent state management; KV_GET reads, KV_SET writes.

+ OCR_VALUE / TEXT

Persists a dynamic on-screen reading straight into storage via a {{ variable }} template.

+ DIALOG

Persists the user's dialog choices so they preload as defaults on the next run.

+ SET_VARIABLE

Updates the value in the read-modify-write loop before KV_SET writes it back.

Common Mistakes and Fixes

Persisting secrets needlessly. Tokens/OTPs/passwords linger on the device. Fix: store sensitive data only when required and for as short a time as possible.

Using the same key with different data types. Writing a number once and a flag another time breaks the read side. Fix: keep each key to a single type and a single meaning.

Forgetting to write the flag. If you read with KV_GET but never KV_SET after the step, the state machine never advances. Fix: always update the flag once the step completes.

Pro Tips

You can combine several variables in the Value template; but composing long text first with SET_VARIABLE and binding the field to that variable with the lightbulb stays cleaner.

Keep flag writes idempotent: run KV_SET only when state actually changes rather than every pass, reducing needless disk writes.

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 →

KV.set("k", "1")

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.

🗃Source and Destination

Use file paths, key names, regex sources, and JSON paths with clear naming discipline.

🧷Default Value

Define default outputs clearly so the builder flow does not collapse when data is missing.

🔄Write Then Read Back

For KV or file writes, verifying the result in the next block is healthier in production-grade flows.

🪶Narrow Output Design

Instead of carrying large raw payloads, extract the value you need and pass it forward via a result variable.

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 →