Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

'$MOD_CONFIG' shown in settings instead of 'Mod Config' #12

Open
ghost opened this issue Dec 7, 2017 · 2 comments
Open

'$MOD_CONFIG' shown in settings instead of 'Mod Config' #12

ghost opened this issue Dec 7, 2017 · 2 comments

Comments

@ghost
Copy link

ghost commented Dec 7, 2017

Not sure why, but all the text added by this mod is affected. Looks like this: https://imgur.com/a/XTGgP

@ghost ghost changed the title '$MOD_CONFIG' shown in settings instead of '$MOD_CONFIG' shown in settings instead of 'Mod Config' Dec 7, 2017
@reg2k
Copy link
Collaborator

reg2k commented Feb 25, 2018

This happens if loose files support is not enabled in the Fallout 4 INI configuration.

MCM's strings (translation files) are not loaded if loose files are not enabled, resulting in pre-translation strings like $MOD_CONFIG appearing in place of Mod Config.

Please follow step 4 in the following link to enable the loading of loose files:
http://wiki.tesnexus.com/index.php/Fallout_4_Mod_Installation

Proposed solution moving forward is to warn the user on game start if MCM detects that loose files are not enabled.
See issue (reg2k/f4mcm#3).

@closms
Copy link

closms commented Jan 6, 2024

The link above (tesnexus.com) doesn't work. This link helped me get this working (MO2 specific) https://redawt.github.io/f4-frost-guide/mo2.html#enable-loose-files

In a nutshell, add this to Fallout4Custom.ini

[Archive]
bInvalidateOlderFiles=1
sResourceDataDirsFinal=

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants