Contents

Creation tools

Local helpers such as the encoding converter; input is never uploaded or stored

Last updated Nov 1, 2026

Where it lives and what it is for

Creation tools in the sidebar gathers the small helpers used while building and debugging works. The encoding converter is the one available today; more will follow.

The page states its principle at the top: all conversion happens locally, and input is never uploaded or saved. Conversion lives entirely in the interface — closing the page discards it, nothing is logged and no request is made.

Encoding converter

This turns ordinary text into the UTF-8 hexadecimal escapes or Galaxy code the StarCraft editor needs:

  1. Type into Original text, for example a Chinese message.
  2. Switch between the four output formats.
  3. Result updates as you type, is read-only, and can be copied with Copy result; Clear all empties the input.

The four output formats:

FormatShape of the resultWhere it goes
Direct conversionPlain hexadecimal escapesPasted into a string literal
As StringA quoted stringAssigned straight to a string field
As TextA StringToText(...) callInterfaces that expect a text object
TriggerDebugA complete TriggerDebugOutput(...) statementPrinting debug text quickly from a trigger

The escaping details for each format — which characters stay as they are, which are split into surrogate pairs — are in Creation tools · Encoding converter, which gives a byte-by-byte reference.

How it relates to the editor documentation

Creation tools is the local tool page inside the app; the editor documentation covers the whole path from building a work to packaging and distributing it. The two join up: the tools generate code fragments, and the editor documentation shows how to put them into a map and publish it.