Troubleshooting

Fixes for Settings Saver problems such as a missing menu button, settings that don't apply, a profile that switched back to default, and unknown versions.

Settings Saver writes everything it does to the game log (logs/latest.log, or the launcher's log window), on lines that start with [Settings Saver]. Most of the fixes below start there.

There is no Settings Saver button in Options#

Cause: the menu couldn't add its button on this Minecraft version and turned itself off. It logs this once. Or the menu was turned off with -Dsettingssaver.ui.disable=true in the Java arguments.

Fix: remove -Dsettingssaver.ui.disable=true if you set it. Otherwise check that you have the right jar for your loader and Minecraft version (see Installation). Syncing still works without the menu, and the profile, sync mode and excluded settings can be set in the config files.

The Config button in the mod list is greyed out#

Cause: Forge 1.13.2's mod list never enables mods' Config buttons.

Fix: use the Settings Saver... button in Options.

A new instance didn't get my settings#

Cause: the profile is empty, the instance already had an options.txt, or it uses another profile.

Fix: see Why didn't my new instance get my settings? Pressing Load settings from profile applies the profile to any instance.

Changes I make aren't saved to the profile#

Cause: sync is Off, the default. Settings Saver then only saves when you press Save.

Fix: press Save settings to profile, or set Sync to Auto. Changing the mode doesn't save the changes you made before it: press Save once after turning Auto on.

A setting keeps coming back after I change it#

Cause: the instance is on Auto + always apply, which applies the profile at every launch, or another instance with sync on saved its value to the profile after yours.

Fix: change the setting in an instance on Auto and let it save, or press Save. If this instance should keep its own value, add the setting to the profile's excluded settings.

Some settings didn't change after Load#

Cause: the game can't change some options while it runs. The menu names them after Load: Loaded '…'. Restart the game to apply: ….

Fix: restart the game. The values are already in options.txt.

The instance switched back to the default profile#

Cause: the profile it used was renamed or deleted, possibly from another instance. The log says Profile '…' does not exist; using default.

Fix: open the Profiles screen and pick the profile again (under its new name).

"This Minecraft version isn't known, so nothing was saved"#

Cause: Settings Saver couldn't detect the running Minecraft version, so it can't convert settings to or from its format. It writes nothing rather than risk a wrong file. The log says Minecraft version unknown.

Fix: report it with your launcher, loader and Minecraft version and the game log. Until then, on 1.10 and newer, Auto sync still saves your changes.

"Failed to start; your settings were not touched."#

Cause: an unexpected error while Settings Saver started. It never stops the game from launching: it turns itself off for this session instead.

Fix: the log has the error just below this line. Check that the store folder is writable (see Where your settings are stored), then report the error with the log.

"Couldn't read or write the settings files"#

Cause: a file in the instance or the store can't be read or written: the folder is read-only, the disk is full, or another program holds the file.

Fix: check the permissions and free space of the instance folder and the store.