Hopefully that helps a bit, it was the first that came in mind looking at the screenshots, it could be something else, too (maybe?).
#MCM CANNOT ACCESS MENU FILES MOD#
If the mod only has the localisation file for English, for example, but your game is in German, you could just try copy-pasting the existing English file and replacing the "ENGLISH" part of the name with "GERMAN", for example.
So it could be that either the mod does not have the localisation file for your specific game language (there is no fallback to English by default), or that the mod has the file, but you do not have it in the right place for the game to find it. But if/when there is no localisation file or key for the specific language, the system leaves the key string itself in the menu (because the key is what there really is written in the menu, the system just substitutes the key with the localised string value and the user sees the localised/replaced version), resulting in those dollar signs and obscure strings. So that both English and German versions get their own versions of the menu texts. $KEYB The intended text in German for KEYB $KEYB The intended text in English for KEYBĪnd in the German version $KEYA The intended text in German for KEYA With the localised key-value pairs in them, for example in the English version (where the key and value have tab between them) $KEYA The intended text in English for KEYA So that, instead of writing things like "Enable FeatureA" or "FeatureB Options" directly to the MCM menu scripts, mod authors can instead use keywords of sorts in their menus that will be localised based on the language of the user's game.įor example if there exists "SomeMod.esp", the author could use the localisation system to supply different texts for, for example, English and German version of the game by placing two files Data\Interface\Translations\SomeMod_ENGLISH.txtĭata\Interface\Translations\SomeMod_GERMAN.txt
#MCM CANNOT ACCESS MENU FILES MODS#
SkyUI extends the base game localisation system so that mods can use it in their MCM menus. Looks like it could be an issue with the localisation system for MCM menus.
0 kommentar(er)
