Localization - Exit-9B/CustomSkills GitHub Wiki

Adding localization support for skill names and descriptions works through the Scaleform Translation functionality exposed by SKSE. If you have made an MCM before, this should be familiar.

In your skill configuration(s), set the name and description to keys that start with the $ sign, for example:

{
  "id": "myskill",
  "name": "$MySkill_Name",
  "description": "$MySkill_Description",
}

The actual name and description for each language can now be specified by providing strings files in Data/Interface/Translations. If your mod plugin is MyMod.esp, the file for English strings would be Data/Interface/Translations/MyMod_ENGLISH.txt. The contents would look like:

$MySkill_Name	My Custom Skill
$MySkill_Description	This skill does something.

Note the use of tab characters separating the keys and values. It is also imperative that the character encoding of the translation files is UTF-16 LE BOM in order to be loaded by SKSE.

Additional translations can be offered by suffixing the filenames with CZECH, ENGLISH, FRENCH, GERMAN, ITALIAN, POLISH, RUSSIAN, SPANISH and JAPANESE. There is no fallback to ENGLISH, so players who want to run their game in a different language will need to have the appropriate translation file available.