-
Notifications
You must be signed in to change notification settings - Fork 22
Troubleshooting: *.ini files
FelisDiligens edited this page Jun 21, 2022
·
3 revisions
You may see this error message when starting the tool or switching profiles:
The error message means that one of your *.ini files could not be read by the tool.
If you edited the file before, you might have introduced a typo.
You have two options on how to fix it:
- Reset the file to default (easy), or
- fix the typo.
If you don't want to lose any settings, you'll need to fix the syntax error (aka. typo).
You can click on "\/ Show details" and then on "Open *.ini file in text editor":
To name a few typos:
-
Check if there's a missing bracket, e.g.
[General
should be[General]
-
Check if there are too many brackets, e.g.
[General]]
should be[General]
-
Check if there's an invalid
key=value
pair, e.g. a newline:
sResourceArchive2List=..., ..., ...,
something.ba2
- Everything has to be on one line:
sResourceArchive2List=..., ..., ..., something.ba2
- Check if there's a comment that doesn't start with a semicolon ';'.
; This is a valid comment
[AudioMenu]
fVal0=0.8 ; This is *NOT* a valid comment (at least not for the tool)
- Check if there's a key=value pair that is not separated by an equals sign '='.
; This is valid:
fVal0=0.8
; This is invalid:
fVal0 0.8
Nexus:
Wiki:
- Frequently Asked Questions
- Troubleshooting
- Mod Manager Guide
- NexusMods Integration
- Game Profiles
- Custom tweaks
Linux 🐧:
Contribute:
Development: