No-Code Workspace — Block Reference

Data and UtilitiesBlock usage recipe

KV Read (KV_GET)

Reads a value from local key-value storage

Documented for app version 1.0.50Updated: October 2, 2026

What Does It Do?

Reads small persisted values from local key-value storage. Use it for state such as last page, counters, flags, user preferences, or values carried over from a previous run.

Pro note: always define a default

KV_GET reads shared state. If the key has not been written yet, a clearly defined default value keeps the rest of the builder flow from collapsing into undefined behavior.

When to Use?

Ideal for:

Restoring a flag from a previous run

Distinguishing first run vs repeat run

Reading last seen item, counters, or persisted preferences

How to Use?

Add KV_GET

Enter the storage key you want to read

Set a Default Value to be used when the key does not exist

Expose it through Result Variable for later blocks

Parameters

Key

Unique name of the stored value to read

Default Value

Fallback value when the key is missing

Result Variable

Variable that will receive the loaded value

Parameter	Description
Key	Unique name of the stored value to read
Default Value	Fallback value when the key is missing
Result Variable	Variable that will receive the loaded value

Example Usage

Scenario: Show onboarding on first run, skip later

KV_GET -> key = has_seen_intro, default = false

COMPARE -> if false, call the onboarding group

After onboarding, KV_SET -> has_seen_intro = true

Combinations / Used With

COMBINATIONS:

KV_GET + COMPARE: state-based branching

KV_GET + GROUP_CALL: onboarding or recovery flows

KV_GET + LOG: inspect persisted state

Tip

Keep storage keys stable and purposeful. Do not reuse the same key for unrelated meanings.

Warnings / Cautions

WARNING:

If default value is left empty, downstream logic may behave like the value is blank or nil

This block is for small state values, not large structured payloads

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

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

Basic

KV_GET reads a small persisted value from local key-value storage into a result variable. You give a key name, set a Default Value for when the key is missing, and expose the loaded value to later blocks. It is the simplest way to carry state across runs.

Advanced

It has three fields: Key (the unique name of the stored value), Default Value (the fallback returned when the key is missing) and Result Variable (where the value lands). The generated code calls KV.get("key", default). This store is for small state values: flags, counters, last-seen item, user preferences, or state carried over from a previous run. If the default is left empty, downstream blocks must treat a missing key as nil/blank, so supplying a meaningful default (false, 0, "") hardens the flow.

Pro

Persistent state-machine pattern: read a flag at macro start with KV_GET (e.g. has_seen_intro, default=false), branch with COMPARE, and update the flag with KV_SET once the relevant step finishes. That distinguishes first run from repeat run and powers onboarding/recovery flows. Keep key names stable and purposeful; reusing one key for unrelated meanings causes silent bugs later. KV_GET shows no UI, so for unattended macros it is far lighter than a DIALOG for reading state.

Real-World Scenarios — Step-by-Step Recipes

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

Onboarding on first run, skip after

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

Resume a counter from the previous run

1KV_GET → key=run_count, default=0, result=count
2SET_VARIABLE: count = tonumber(count) + 1
3... macro work ...
4KV_SET → key=run_count, value={{count}}

Which Blocks to Pair With — Pro Combinations

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

+ COMPARE

Branches on the loaded state (first run? flag set?) and steers the flow.

+ KV_SET

Completes the read-modify-write loop: start with KV_GET, persist the new state with KV_SET.

+ GROUP_CALL

Calls an onboarding or recovery sub-flow depending on the loaded state.

+ SET_VARIABLE

Converts a counter read as a string into a number with tonumber() for arithmetic.

Common Mistakes and Fixes

Leaving the Default Value empty. When the key is missing, downstream blocks behave unexpectedly under nil/blank logic. Fix: supply a meaningful default (false, 0, "").

Assuming the KV value is a number. The KV store is text-based; using a read counter directly with + can error. Fix: convert with tonumber().

Reusing the same key for different meanings. Using one key as a counter here and a flag there makes the flow brittle. Fix: give each purpose its own stable key name.

Pro Tips

Keep key names snake_case and module-independent (like last_order_id); good naming lowers long-term maintenance cost.

KV is for small state; store large JSON/lists in a file flow instead and keep only a key/pointer in KV.

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 kvVal = nil

kvVal = KV.get("k", 0)

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 →