Export en US

Export and Translate

Requires 0.2.0 or later. For 0.1.0, use Manual Setup.

1. Export

Select the target game language, then join a world or server where the commands are visible. Run:

/command_translation export

This collects missing entries for visible mod commands. To filter to Create:

/command_translation export create

The filter accepts a namespace or original command root. Chat shows the ZIP path inside the current game directory's resourcepacks folder. The pack is not enabled automatically, and existing files are not overwritten.

2. Translate

Give the ZIP and the prompt below to a translation tool that can work with files. The pack contains:

File	Purpose
en_us.json	English reference
Target locale JSON, such as zh_cn.json	File to translate and replace
translation-manifest.json	Command structure, protected bindings and missing descriptions
pack.mcmeta	Matching game-version metadata; no manual editing needed

Language files are under assets/command_translation/lang/. Vanilla entries and existing target-language translations are not exported again. Existing item and other object names still come from their mods and resource packs.

Translation Prompt

Translate the target language file identified by target_language and target_file in translation-manifest.json. Use en_us.json as the English reference and the command structure as context.
Preserve existing keys, JSON structure, original IDs, placeholders, escapes and formatting markers. Do not translate values whose keys appear in protected_keys: they are bindings.
Aliases (.alias) and namespace display names must contain no whitespace; join multiple words with underscores. Preserve | between alternative aliases. Descriptions should explain the specific purpose concisely, not become input aliases.
Do not invent argument meanings from their names. Keep missing_descriptions pending unless a reliable source is supplied. examples are format examples, not exhaustive choices.
Return only the complete, valid target-language JSON, or a ZIP with only that file replaced. Do not change the English reference, manifest or pack.mcmeta.

To fill pending descriptions, additionally request verification against the mod's official documentation or source code. Add only keys listed in missing_descriptions and provide source links separately. Leave unsupported meanings pending.

3. Use

Put the translated file back at its original path in the ZIP, keeping pack.mcmeta at the ZIP root. Enable the pack in Resource Packs and reload resources. Mod authors can instead merge the translated entries into their own language file; no internal Java API is required.

Exports reflect the current connection and visible commands, not infinite dynamic suggestions or arbitrary player data. Commands with no reported owner use their original root as a separate namespace, listed in command_root_namespaces; the exporter does not guess mod IDs.

The translationExport configuration switch is enabled by default. Detailed tag, component, NBT and binding instructions remain in Manual Setup and the Key Reference.