If you've ever felt frustrated while translating a mod's Config.json file because it lacks an "interface/translation" text file that XTranslator can use, then this tool is exactly what you need. It can automatically create $keywords and generate the corresponding translation file based on them.
You don't need it, but that's exactly what this app is for.
Permissions and credits
Credits and distribution permission
Other user's assetsAll the assets in this file belong to the author, or are from free-to-use modder's resources
Upload permissionYou are not allowed to upload this file to other sites under any circumstances
Modification permissionYou are allowed to modify my files and release bug fixes or improve on the features so long as you credit me as the original creator
Conversion permissionYou can convert this file to work with other games as long as you credit me as the creator of the file
Asset use permissionYou are allowed to use the assets in this file without permission as long as you credit me
Asset use permission in mods/files that are being soldYou are not allowed to use assets from this file in any mods/files that are being sold, for money, on Steam Workshop or other platforms
Asset use permission in mods/files that earn donation pointsYou are allowed to earn Donation Points for your mods if they use my assets
Console modding permissionThis mod will not be available on Bethesda.net for console users
Author notes
This author has not provided any additional notes regarding file permissions
File credits
This author has not credited anyone else in this file
Donation Points system
Please log in to find out whether this mod is receiving Donation Points
Changelogs
Version 1.1
Add options to include special html format such as <p>example</p>, but MCM does not support in translation_xx.txt
This is added only because there are some mods using too much special html format, and it will still be a pain if it's not included in translation_xx.txt
Add 3 options to setting menu
You can choose between exclude/include/include but remove format.
First 2 are pretty straight forward, "include but remove format" will remove all special html format in the text.
For example,<p>example</p> to simply example, you'll loose the fancy format it got, but have the chance to translate it directly.
I recommend you only choose "exclude" or "include but remove format" as the format will not work after it's converted to translation_xx.txt
Version 1.05
Fixed a minor bug delete cause CTD and not deleting correct item.
Version 1.04
Fixed a minor bug delete only effects translation file not Config.json.
Version 1.03
Fixed a bug where you can't really change keyword prefix
Improve UI layout to be more comfortable
Version 1.01
Fixed a major bug where I just found out that MCM will only recognize the keyword instead of the .txt file name, Causing conflicts between two mods. T
So basically, whenever multiple modules use the same keyword, they will display the keyword from the last loaded .txt file only.
To ensure it works correctly, you NEED to update to this newer version.
Version 1.0
Add 8 languages for UI.
Fixed options only generate if there is an id for it
Add support for generate different ModNamd_xx.txt language .txt files
Add a setting menu
Version 0.9
Keywords are generated either by ID or type and are color-coded based on their quality:
White: Good keywords, generated by ID or display name.
Yellow: Average keywords, generated by page info and type.
Red: Poor keywords (though I haven't encountered these yet, they might appear).
you can edit keywords and undo changes. Edited keywords will be marked in green.
Please note: descriptions cannot be edited here. It's better to edit them in Xtranslator.
When saving, the app will look for an "MCM" folder in the data directory, regardless of whether you're using a mod organizer. If it doesn't find one, it will save in the current directory with a time-stamped backup.
Donations
No donations accepted
🌟 About 🌟 Mod Name: MCM Translation Text Generator Ever felt lost in translation with Mod Configuration Menu (MCM) without a translation text? from what I see recently there are many translations uploaded. If you find this tool helpful and you like it, don't forget to endorse~
🔧 Features 🔧
Automated creation of keywords and translation files for MCM Config.json, saving you from manual labor, which I already did a lot.
The keywords are generated first by ID, then by type. If neither of those exists, it falls back to using the page and section number.
It automatically generates the interface/translation/modname_en.txt file based on its location path. If the Config.json file is in the correct data folder structure, the file will be created there. Otherwise, it will be created in the same location as the Config.json file itself.
You can choose to generate between all modName_xx.txt language codes that's supported by Fallout 4.
Now with UI language support in English, Chinese, Japanese, Korean, French, Dutch, Russian, and Spanish—all translated by ChatGPT—if there's an incorrect part, simply open the exe location/lang/yourlanguage.txt.
📝 Details 📝 I made an application because I felt there might be a need, even though tools like Simple MCM Json Translator exist. However, it can't always handle the disorganization that happens in MCM menu structures after updates. Importing older versions' configs didn't consistently align the texts correctly, even with minor differences. After dealing with these long and never-ending config files, I had the idea for this application. Now, you can generate translation files, then use Xtranslator to translate or import a comparison MCM file of older version. Since the keywords are generated by a pattern, the chance of errors is low. Just ensure you do a quick check in Xtranslator when importing a comparison file. Enjoy!
📖How To Use📖
Open this App
Drag Config.json file of the mod you want to generate translation file.
A quick check on the keywords, recommend leaving them as it be, it will be easier if mod author released a new version when you need to update again.
Change the mod name prefix field to any prefix you like.
Click save.
Open Xtranslator, select "Load MCM/Translate file".
Choose the mod folder you just generated from, there should be a new Interface folder.
Locate to Interface/Translations folder, you should see the generated modName_xx.txt files in there.
Load them in Xtranslator, start to translate and all done.
⭐If there is a mod Update and MCM has changed⭐
Don't delete your old file, either make a copy or install new mod as a different folder name that won't replace the original modName.txt
Repeat the above to generate modName.txt for the mod's latest version.
Open Xtranslator, select "Load MCM/Translate file" again.
Choose the latest modName.txt.
Go to "Tools", select "Load MCM/Translate (Compare)".
Choose the old version modName.txt for comparison.
Xtranslator should automatically replace texts with same keywords, and if you didn't edit them in the first place, they should 90% all be the same.
Translate and all done
Note: if folder isn't like Data/MCM/modName/Config.json, app can't detect the correct mod name and will only generate translate_xx.txt 📜 Changelog 📜 1.1 update:
Add options to include special html format such as <p>example</p>, but MCM does not support in translation_xx.txt
This is added only because there are some mods using too much special html format, and it will still be a pain if it's not included in translation_xx.txt
Add 3 options to setting menu
You can choose between exclude/include/include but remove format.
First 2 are pretty straight forward, "include but remove format" will remove all special html format in the text.
For example,<p>example</p> to simply example, you'll loose the fancy format it got, but have the chance to translate it directly.
I recommend you only choose "exclude" or "include but remove format" as the format will not work after it's converted to translation_xx.txt
1.05 update:
Fixed a minor bug delete cause CTD and not deleting correct item.
1.04 update:
Fixed a minor bug delete only effects translation file not Config.json.
1.03 update:
Fixed a bug where you can't really change keyword prefix
Improve UI layout to be more comfortable
1.01 update:
Fixed a major bug where I just found out that MCM will only recognize the keyword instead of the .txt file name, Causing conflicts between two mods.
So basically, whenever multiple mods use the same keyword, they will display the keyword from the last loaded .txt file only.
To ensure it works correctly, you NEED to update to this newer version.
1.0 update:
Add 8 languages for UI.
Fixed options only generate if there is an id for it
Add support for generate different ModNamd_xx.txt language .txt files
Add a setting menu
👾Known Issues👾 It doesn't work when there is a "setting.ini" in the same folder with Config.json, and says MCM version 1 or 2. Don't know why, might because it's from old version of MCM, if you have solution please comment. But most of the mods don't have that file and not using old version MCM, So test before use, I'd say 90% of mods would work, but there will be exceptions, who knows.
👏 Credits 👏 Me, All the lost souls when translating directly from Config.json
✨ More ✨ This isn't finished yet, but it's usable for its intended purpose. Let me know if you encounter any bugs.