HexParse

HexParse mod

Provides a pair of patterns and a set of commands to convert custom code into (pattern or literal) list iota; requires player to have a focus item in hand.

(Old KubeJS version HERE)

| Example Code | Example Iota | Example Iota (Colorful Nested) | |---------------------------------------------------------------------------------|---------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------| | | | |

_The highlight VSCode extension is available on the Marketplace (source code)._

<!-- TOC -->

• HexParse mod
• Supported IO Item Types
• Commands Added
• Reading & Writing
• Configs
• Misc. & Helpers
• OP-Only Commands
• Patterns Added
• Misc. Features
• New Iota: CommentIota
• HexParseAPI
• External Documents
• Supported Expressions
• Available Configs

<!-- TOC -->

Supported IO Item Types

• Focuses
• Spell Books
• (1.20) Thought Knots
• recognized by item classes, able to add more via HexParseAPI or IOMethod

Commands Added

Reading & Writing

• /hexParse <code string> [rename]: parse input code into supported held item; optional rename argument to rename the item.
• /hexParse read: read handheld item's iota, parse into code and show in chat window; the result will be copied

when clicked.

• /hexParse read_signatures: same as read, but ignores all known pattern IDs and outputs all as angle signatures.
• /hexParse clipboard [rename]: read client clipboard text and parse into supported held item; optional rename argument to rename

the item.

• /hexParse clipboard_angles [rename]: same as clipboard, but only accept patterns input with raw angle string like

"wedsaq".

• /hexParse clipboard_hexpattern [rename]: (experimental) same as clipboard, but accepts .hexpattern format; _warning: only partial features supported_.
• /hexParse share: (experimental) same as read but broadcasts iota's raw content and click-copy-able parsed code to

every player in the server.

• /hexParse read_hexbug: same as read but translates the result to the format used by discord HexBug's /patterns hex command. _note:

non-pattern constants and some old registry names still need to be handled manually_

• /hexParse mind_stack ...: read/write iota from player's mind (staff casting VM)
• ... peek: read the last iota inside mind stack; gets null if stack is empty
• ... push <code>: parse code and push into mind stack
• ... push_clipboard: same as above, but code comes from clipboard
• /hexParse property ...: (Hexcellular interop) get/set data for PropertyIota; used property names all force-added leading _ for security reason
• ... read <propName>: read and parse from certain property
• ... write <propName> <code>: write code into certain property
• ... clipboard <propName>: same as above, but code comes from clipboard

Configs

• /hexParse (macro/dialect) ...: edit client-saved code dialects (1-on-1 mapping, not starting with #) and macros (

mapped to code segments, starting with #)

• ... list: list all saved macros/dialects; there exist several predefined macros from ~~the nature~~
• ... define <key> <value>: define a macro/dialect mapping; could be fresh-new or overriding existed one.
• macro define_clipboard <key>: same as above, but only for macros, and reads player's clipboard
• ... remove <key>: remove mapping entry with given key (if exists)
• /hexParse conflict: conflict resolver for multiple patterns with same short name (ID path)
• _only enables in physical client (singleplayer, local multiplayer) or with OP permission_
• ... or ... list: list all short names pointed by multiple long IDs
• ... list <short_name>: list all conflicting IDs under certain short name
• ... set <short_name> <long_ID>: redirect certain short name to input pattern ID

Misc. & Helpers