No-Code Workspace — Block Reference

Data and UtilitiesBlock usage recipe

String Operation (STRING_OP)

Transforms text: trim, split, replace, upper/lower

Documented for app version 1.0.50Updated: October 2, 2026

What Does It Do?

Offers 15 text operations: substring, replace, concat, trim, split, join, length, upper, lower, contains, startsWith, endsWith, indexOf, pad and repeat.

When to Use?

Use it to clean OCR or clipboard text, do light parsing, or normalize text before branching.

How to Use?

Type the source text or bind the field to a variable with the lightbulb

Pick the operation and fill its parameters

Store the result in the result variable

Parameters

Source

Text to transform or a lightbulb-bound variable

Operation

One of the 15 operations

Parameters

Extra fields required by the operation

Parameter	Description
Source	Text to transform or a lightbulb-bound variable
Operation	One of the 15 operations
Parameters	Extra fields required by the operation

Example Usage

OCR_VALUE → priceText → STRING_OP replace (source bound to priceText, TL → empty) → trim → COMPARE

Combinations / Used With

COMBINATIONS:

STRING_OP + REGEX_MATCH: Clean first, then extract

STRING_OP + COMPARE: Branch on normalized text

Tip

Transforms text: trim, split, replace, upper/lower

Warnings / Cautions

WARNING:

Source and parameter fields do not resolve {{ }} templates; use the lightbulb for variables

length and indexOf return numbers, contains/startsWith/endsWith return true/false

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

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

Basic

STRING_OP shapes text inside the builder in one block: it gathers operations like cut, replace, split, trim, upper/lower, and length. You enter the source text or bind a variable, choose the operation, and store the result in the Result Variable. It is the practical way to quickly clean OCR, clipboard, or API text.

Advanced

The operation choices, by their real names: substring (start, end), replace (old, new), concat (append), trim, split (separator), join (combine with separator), length, upper, lower, contains, startsWith, endsWith, indexOf, pad (target length + pad char), and repeat (count). Each operation uses as many parameters as it needs: replace takes two (param1=old, param2=new), substring takes two positions, contains/indexOf take a single search fragment. length and indexOf return a number, while contains/startsWith/endsWith return a boolean (true/false). The source and parameter fields take what you type as plain text; to use a variable's value, bind the field to that variable with the lightbulb (these fields do not resolve {{ }} templates).

Pro

Make STRING_OP your first line of OCR normalization: clean currency markers, spaces, line breaks, and thousands separators from the OCR_VALUE/TEXT result with replace + trim, and only then feed MATH_EVAL or COMPARE (a number-expecting block can't read the text '1,234 TL' correctly). Instead of one complex regex, several small STRING_OP steps are usually more readable and debuggable. Use contains/startsWith to check presence and feed IF_ELSE; use split to fragment and produce list-shaped data for FOR_EACH. Watch the types: length returns a number, contains returns a boolean — route those results to the right block type. To hand the user clean output, finish with CLIPBOARD_WRITE.

Real-World Scenarios — Step-by-Step Recipes

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

Clean a number out of an OCR price

1OCR_VALUE -> resultVar = priceText
2STRING_OP -> source bound to priceText with the lightbulb, op = replace, param1 = TL, param2 = (empty), resultVar = noUnit
3STRING_OP -> source bound to noUnit, op = trim, resultVar = cleanPrice
4Use cleanPrice in COMPARE

Branch on whether a label is present

1TEXT or CLIPBOARD_READ -> resultVar = body
2STRING_OP -> source bound to body with the lightbulb, op = contains, param1 = SUCCESS, resultVar = hasSuccess
3IF_ELSE -> if hasSuccess is true continue, else ERROR_HANDLER

Which Blocks to Pair With — Pro Combinations

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

+ REGEX_MATCH

Light cleanup with STRING_OP first, then precise extraction with REGEX_MATCH, is the most robust text pipeline.

+ JSON_PARSE

Normalizes raw API text before parsing, reducing invalid-JSON failures.

+ MATH_EVAL

Once the text is cleaned and number-ready, the arithmetic runs reliably.

+ CLIPBOARD_WRITE

Hands the user the shaped final text as clean output.

Common Mistakes and Fixes

Using a text result ("10") where a number (10) is expected. Fix: COMPARE/MATH_EVAL expect numbers; clean the STRING_OP output first and make sure it's a real number.

Confusing the returned type (contains is boolean, length is a number). Fix: route contains/startsWith to IF_ELSE and length to COMPARE.

Trying to do everything in one giant operation. Fix: chain a few small, named STRING_OP steps; the flow becomes more readable.

Pro Tips

Keep a fixed order for OCR normalization: replace first (noise), then trim (edge whitespace), and lower last (for comparison). A consistent order eases debugging.

Use split to fragment text and feed it straight into LIST/FOR_EACH; operations that return a table are ideal sources for looping flows.

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

str_val = Str.length("hello")

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 →