tool MCM Translation Text Generator

[BlackPainkiller]

MCM Translation Text Generator

View File

---

🎉Introduction🎉

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.

 

there are a lot of amazing mods here that has a long and massive MCM menu, I don't know about the need of translation here, but there might be someone need something like this, if it happens to be you, *cheers* my friend.

 

🌟 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.

 

🔧 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

 

👾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.

---

• Submitter
  BlackPainkiller
• Submitted
  06/23/2024
• Category
  Modders Resources
• Requirements

 

[icevapour]

wow！I’m so excited that I can’t put it into words。

[icevapour]

Something went wrong, and I had an MCM title that changed to the name of another one mod (I tried translating these two mods), but the other mod’s name didn’t change. Where did I go wrong?

it should be “联邦奴隶贩子”

Edited June 23, 2024 by icevapour

[BlackPainkiller]

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.

 

If anyone has downloaded the 1.0 version remember to update

 

Remember to restore the original backed up Config.back_up_time_tag file,

because if you have used version 1.0 to generate translation file then the "text" fields in config.json has already been replaced to $xxxxxx, so you need to restore it first before generating newer translation

 

Edited June 23, 2024 by BlackPainkiller

[gezelligheid]

I can't describe how excited I am.

[BlackPainkiller]

1 hour ago, gezelligheid said:

I can't describe how excited I am.

Seeing people truly get helped by this makes me happy too😝