Localization

Included Languages

Each player sees the game in their own client locale; the server never reads or stores a per-player language preference. The matching .lang file is resolved client-side, with English as the per-key fallback.

Native Language Files (.lang)

The nine built-in languages ship as native Hytale .lang translation files bundled in the mod jar, and new languages are added the same way - as a small asset pack dropped into your mods directory. This is the recommended way to add or share a language: it is discovered automatically at server start, needs no admin commands, and survives mod updates.

• The full authoring guide (the mmoskilltree.lang filename rule, the fallback chain, and the zip gotcha) is on the Translation Packs page.

Quest and achievement notice wording (progress ticks, completion jingles, parked notices, the achievement unlock toast and its server banner, claim chimes, the server-first note) is not a .lang file at all - it is authored per moment under Server/ZiggfreedCommon/FeedbackMoments/, and reworded, recoloured, or silenced by dropping a same-named file in a content pack. See Feedback Moments.

Prefer to tweak a handful of strings without shipping a pack? Use the optional per-server JSON admin override below; it layers on top of the native files and always wins.

The Filename Is the Key Prefix

In practice that means a key goes in the file named for whoever owns it. Most MMO Skill Tree keys go in mmoskilltree.lang, but the jar ships five more, each holding one slice of the mod's own vocabulary:

A net-new file for this mod follows the same convention: name it mmoskilltree.<domain>.lang, and every key inside it drops the segment the filename already carries (invisible to call sites, since the engine prefixes every key with the file's basename).

The required ZiggfreedCommon jar ships files of its own, in all 9 languages, and you override one of its words by writing into a file with that same name:

Keys You Can Answer Yourself

Some names are looked up by convention, so simply authoring the key is enough to give something a proper, translated name. These work from a content pack or from your own language pack:

For a shelf or a band the ladder is: what the content itself authors, then your own key, then the shared library's neutral default, then the raw name shown as-is.

Admin Override: Custom Translations

Use this override to tweak a handful of server-resolved strings (in the server's default language) without shipping a full language pack. These overrides live on your server and always win over pack and built-in translations for that language:

1. Set the server's default language if it isn't already what you want to edit: /mmoconfig language <code> (e.g. /mmoconfig language ja)
2. Create mods/mmoskilltree/localization/messages-<code>.json (e.g. messages-ja.json) - there is no file to copy, the mod never writes a reference file to disk; start from an empty object
3. Add only the specific keys you want to override, as a flat key-value map; English key names and values for reference live in the bundled en-US/mmoskilltree.lang file
4. Run /mmoconfig reloadlang
5. The overridden strings apply immediately, but only to the server-resolved sinks listed above, for the server's configured default language

Message Structure

Language files use a flat key-value structure with placeholder support:

{
  "language.name": "English",
  "ui.button.close": "CLOSE",
  "ui.button.back": "< BACK",
  "ui.viewxp.title": "Skill Overview",
  "ui.viewxp.level_prefix": "Lv. {0}",
  "notify.xp_gain": "+{0} {1} XP",
  "notify.level_up": "LEVEL UP! {0} is now Level {1}!",
  "skill.mining": "Mining",
  "reward.stat_health": "Max Health",
  "reward.format.percent": "+{0}%",
  "reward.format.flat": "+{0}"
}

Message Categories

Placeholders

Use {0}, {1}, etc. for dynamic values:

• "notify.xp_gain": "+{0} {1} XP" → "+50 Mining XP"
• "ui.viewxp.level_prefix": "Lv. {0}" → "Lv. 42"

Hot Reload

/mmoconfig reloadlang

Reload all language files without server restart. New translations take effect immediately.

Server Default Language

/mmoconfig language <code>

Sets the server's single default language, stored in mods/mmoskilltree/skill-config.json (default en). This does not change what any individual player sees - per-player locale is resolved entirely client-side and the server never reads or stores it. This command only controls which language the admin-override JSON files above and the residual server-resolved sinks (combat text, tooltips, console output) target.

Fallback Behavior

• Resolution order: admin override, then native language file, then English default
• Missing keys fall back to English, per-key
• A conversation line with no translation behind it renders as its raw key instead, so it can be spotted and fixed rather than dropping the player from their session

Sharing Translations

Override files are portable; share your messages-XX.json with other servers. To publish a full language for everyone, package it as a native language asset pack.

What's Localized

• All UI text (pages, buttons, labels)
• XP and level-up notifications
• Skill names
• Reward type names and descriptions
• Command responses and error messages
• Settings labels