Chunk Item Operation

In chunk modules, the chunk name is case sensitive. This means that MYCHUNK is not equivalent to mychunk or MyChunk.

In chunk modules, the item names are case sensitive. This means that item1 is not equivalent to Item1 or ITEM1.
To avoid mismatch between names and RegEx ^, ., $, *, +, ?, (, ), [, ], {, }, \, | are not allowed in the names.

can be a RegEx (Regular Expression)
see regular expression.

• ^a.* match any string starting by "a"
• (?i)^a match any string starting by "a" or "A" (case insensitive)
• .*a$ match any string ending by "a"
• .*\d$ match any string ending by a number "1","2","3", etc.
• .at matches any three-character string ending with "at", including "hat", "cat", "bat", "4at", "#at" and " at" (starting with a space).
• [hc]at matches "hat" and "cat".
• [^b]at matches all strings matched by .at except "bat".
• [^hc]at matches all strings matched by .at other than "hat" and "cat".
• ^[hc]at matches "hat" and "cat", but only at the beginning of the string or line.
• [hc]at$ matches "hat" and "cat", but only at the end of the string or line.
• \[.\] matches any single character surrounded by "[" and "]" since the brackets are escaped, for example: "[a]", "[b]", "[7]", "[@]", "[]]", and "[ ]" (bracket space bracket).
• s.* matches s followed by zero or more characters, for example: "s", "saw", "seed", "s3w96.7", and "s6#h%(>>>m n mQ".
• [hc]?at matches "at", "hat", and "cat".
• [hc]*at matches "at", "hat", "cat", "hhat", "chat", "hcat", "cchchat", and so on.
• [hc]+at matches "hat", "cat", "hhat", "chat", "hcat", "cchchat", and so on, but not "at".
• cat|dog matches "cat" or "dog".
• \\ to search the \ char (backslash)

In chunk modules, the item names are case sensitive. This means that item1 is not equivalent to Item1 or ITEM1.
To avoid mismatch between names and RegEx ^, ., $, *, +, ?, (, ), [, ], {, }, \, | are not allowed in the names.

Type mismatch between payload and stored item If an item already exists as a float and you overwrite it with a different type (e.g., string), the item's type changes silently. Any other module reading that item with the original type assumption will get unexpected values. Keep the type consistent across all modules that read and write the same item.

"Auto add or modify" triggers on every payload change In auto add or modify item mode, the chunk is written every time the payload input changes — including during patch initialization or preset loading. This can cause unintended writes. Use add or modify item with an explicit perform trigger if you need precise control over when writes happen.

"Clear chunk" and "destroy chunk" are global operations Clear chunk deletes all items but the chunk still exists. Destroy chunk removes the chunk entirely. Both operations affect every module in Usine that references this chunk. Use with caution in complex setups.

"Delete item" vs "clear item" Clear item resets the item's content (array size to 0 or string to NULL) but the item still exists in the chunk. Delete item removes the item entirely — any chunk-item-get reading it will report it as invalid. Choose based on whether you want to preserve the item's existence or remove it.