This page was last updated on 22 November 2024, 8:48AM
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.
