No-Code Workspace — Block Reference

Data and UtilitiesBlock usage recipe

File Write (FILE_WRITE)

Writes or appends text to a file

Documented for app version 1.0.50Updated: October 2, 2026

What Does It Do?

Writes text into a local file or appends to an existing one. Use it for reports, local logs, exports, and durable intermediate output from builder flows.

Pro note: keep file writes narrow and intentional

FILE_WRITE leaves a persistent trace. Keep the destination path stable, label the content clearly, and support writes with before/after logs for a more professional builder flow.

When to Use?

Useful for:

Writing scan results into a report

Storing error traces for later review

Creating simple text exports such as JSON or CSV-like output

How to Use?

Add FILE_WRITE

Enter the target file path

Prepare the content as fixed text or a {{ variable }} template

Use Append when you want to add to the file instead of replacing it

Parameters

File Path

Local file path to write to

Content

Fixed text, a {{ variable }} template, or a variable bound with the lightbulb

Append

When enabled, appends to the file instead of replacing it

Parameter	Description
File Path	Local file path to write to
Content	Fixed text, a {{ variable }} template, or a variable bound with the lightbulb
Append	When enabled, appends to the file instead of replacing it

Example Usage

Scenario: Accumulate an error log on every failure

Use FILE_WRITE inside ERROR_HANDLER or a FALSE branch

Set Append = true

Write timestamp + error + screen state

Combinations / Used With

COMBINATIONS:

DATE_TIME + FILE_WRITE: timestamped reports

ERROR_HANDLER + FILE_WRITE: local error traces

HTTP_REQUEST + FILE_WRITE: archive API output

Tip

Use append for ongoing logs and overwrite for single-snapshot files.

Warnings / Cautions

WARNING:

Writing to the wrong path can overwrite valuable data

The block never raises an error: a refused write or one over 10 MB only leaves a log entry; verify important files with FILE_READ

Excessive file writes can create unnecessary overhead

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

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

Basic

FILE_WRITE writes the text you prepare into a local file. With Append off it overwrites the file; with Append on it adds to the end of the existing content. It is the most direct block for producing reports, keeping debug logs, or making simple exports. Build the content as fixed text, a {{ variable }} template, or a variable bound with the lightbulb.

Advanced

The path always resolves inside the sandbox, and required parent folders are created automatically on write. Append=true selects append mode (add to the end), while false fully overwrites; that choice is the difference between accumulating a log and keeping a single snapshot. A write that would exceed 10 MB is skipped, and paths with null bytes or invalid characters are rejected. FILE_WRITE never throws: a refused or failed write only leaves a log entry, so read important files back with FILE_READ. Use {{ variable }} in the content; to make the file name dynamic, build the path with SET_VARIABLE (e.g. logs/{{day}}.txt) and bind the path field with the lightbulb.

Pro

Use FILE_WRITE for a durable audit trail: inside ERROR_HANDLER or a FALSE branch, write timestamp + error + screen state with Append=true so you can investigate field issues later. For JSON/CSV-like exports, prepare the content from a JSON.stringify'd variable and write it as a single snapshot (Append=false), then restore it next run with FILE_READ + JSON_PARSE. Frequent writes cost performance; instead of writing every loop iteration, accumulate lines in a variable and write once at the end of the loop. Share the same path with FILE_READ and FILE_DELETE to build a single-source 'state file' pattern.

Real-World Scenarios — Step-by-Step Recipes

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

Accumulate an error log on every failure

1ERROR_HANDLER -> action = CUSTOM, errorVariable = runtimeError
2DATE_TIME -> resultVar = ts
3FILE_WRITE -> path = logs/errors.txt, content = {{ts}} {{runtimeError}}, append = true
4Inform the user with NOTIFY_TOAST

Archive an API result into a local cache snapshot

1HTTP_REQUEST -> resultVar = apiResponse
2FILE_WRITE -> path = cache/report.json, content bound to apiResponse with the lightbulb, append = false
3Read it back next run with FILE_READ + JSON_PARSE

Which Blocks to Pair With — Pro Combinations

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

+ DATE_TIME

Produces timestamped lines or dated file names for meaningful, parseable logs.

+ ERROR_HANDLER

Writes the captured error to a persistent local trace for later field diagnosis.

+ HTTP_REQUEST

Archives the API response to disk so later runs read a local cache instead of the network.

+ FILE_READ

A write/read pair sharing one path is the basis for carrying durable state across runs.

Common Mistakes and Fixes

Forgetting Append and overwriting, wiping the old log. Fix: use Append=true for ongoing logs and Append=false for single-snapshot files.

Writing to the wrong/valuable path and losing data. Fix: use dedicated sandbox paths (logs/..., cache/...) and never share a name with user data.

Writing to the file on every loop iteration. Fix: accumulate lines in a variable and write once with a single FILE_WRITE after the loop.

Pro Tips

Write lines structurally for easy parsing next run: a tab/delimiter format like {{ts}}\t{{event}}\t{{value}} reads cleanly with REGEX_MATCH or STRING_OP split.

Keep the JSON snapshot on one line; compact JSON instead of multi-line pretty-print makes the FILE_READ + JSON_PARSE chain more robust.

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 →

File.writeText("scripts/output.txt", "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 →