[Knowledge of WolvenKit at BASIC level is required] Below we will explain how to translate any mod
This guide will teach you how to translate a mod. It will cover the following processes:
There are mainly two ways to translate a mod. One is to use WolvenKit, GIT and GitHub. On the other hand, the author of the mod provides the files (an Excel sheet for example) where the sentences to be translated are written.
You need a Wolvenkit Project with the relevant files from the original mod:
.wem
for audio translations
.json
for text translations
For how to get there, see Analysing other mods
Most mods will be using in-game files for this. You'll run into one of two cases:
The mod is only "pointing" at the original game files, and they're loaded from the player's local copy and will be in whatever language they're running.
TODO: Which file(s) defines those? If there is no original mod author and the mod links to in-game files, how can we custompath them?
If you want to translate them anyway, you need to add the audio files from your translated version to your Wolvenkit project and send them to the original mod's author.
Assuming that the original mod author did not rename the files, this makes it easier for you.
Add the file to your Wolvenkit project
Overwrite the original file
When you pack your mod now, it will use the translated files. If it doesn't, make sure to check your load order.
If you are lucky, you are translating this for someone else, and the person has given you an excel sheet. Otherwise, you need to edit the mod's .json
files (see #prerequisites).
When you are done translating you can contact the original mod author to see if they want to include your changes into the main mod.
If not, then you can pack your mod as a standalone addition and upload it independently. In this case, it is important to consider the Load Order: your mod has to load first.
Published: 19 Mar 2024 by Last documented edit: 19 Mar 2024 by
You can listen to audio files by simply selecting them in the Wolvenkit Project Browser and using the built-in audio player. See on the Wolvenkit wiki for a screenshot.
with each file name
You'l have no choice but to find the right file from hand in the sources, which means you have to for the extension .wem
.
The JSON files are actually encoded – this means that you have to edit them in Wolvenkit, or . (Yo dawg, I hear you like exporting as JSON!)