YACL Settings Not Saving: Checks That Find the Cause
When settings revert, the screen is usually fine and the write is failing. Check in this order: did you confirm with the screen's save or done control, is the mod's config file being written in the right instance, is anything locking that file, and did the game close cleanly last time. One of those four explains nearly every case.

First, rule out the screen itself
YACL screens apply changes when you leave through their confirmation control. Backing out with Escape can discard edits on some screens, by design, the same way a settings page in any program may treat cancel as cancel. Make your change, use the Done or Save control the screen provides, then reopen the screen and look before you relaunch or change anything else.
Also test with a loud change: a toggle you can see from across the room, such as a HUD element switching off. Subtle slider changes invite false conclusions. If the loud change holds in the reopened screen but vanishes after a restart, the screen works and the file write is the problem, which is where the next checks go.
Find the file that should change
Settings live in the dependent mod's config file, inside the config folder of the instance you are playing. The file usually carries the mod's name and a .json ending. Open the instance's config folder, note the file's modified time, change a setting in game, close the screen properly and look again. A file whose timestamp does not move was not written, whatever the screen suggested.
If there is no file with the mod's name, you may be looking at the wrong instance. Players with several profiles regularly edit one instance's config while playing another. Run the profile identity routine from the installation category and repeat the timestamp test in the folder it proves is live.
What blocks a write
- The config file or folder is marked read-only, sometimes by a copied pack or a backup restore.
- The instance lives in a location your operating system protects, and the game lacks permission to write there.
- A sync or backup tool holds the file while the game tries to save.
- The disk is full or nearly full, so the write fails quietly.
- The game crashed or was force-closed after the change, before the mod's save routine ran.
Work down the list by testing, not by reinstalling. Copy the config file, rename the copy, and see whether the copy succeeds. Check the file's properties for a read-only flag. Start the game once as you normally do, change the setting, then close the game through its own quit option and check the timestamp again. A clean quit fixes the last cause on its own.
The two-instance trap
Launcher mod browsers and pack updates create a subtler version of the wrong-folder problem: the same pack installed twice, once by you and once by an update or import. You play one copy and edit the other, and both look identical in a file manager. The latest.log timestamp check separates them. Launch the game, close it, and see which instance's log and config files moved. Edit only that instance from then on, and consider deleting the stale copy to remove the trap permanently.
When the mod resets settings by design
A few behaviours look like failed saves but are the mod working as written. A mod may reset an option that conflicts with a server rule when you join a world, tie a setting to a specific world or profile, or migrate an old config format on update and move your values to a new file. The clue is selectivity: a write failure loses everything, while design resets lose one option or one group. Read the mod's changelog for config changes around the version you updated to, and check whether a new file appeared beside the old one.
The crash-log clue
When saves fail, the log often says so. Search the instance's latest.log for the mod's name near the moment you closed the settings screen or quit the game. Lines about failing to write or serialize a config point straight at the file and sometimes at the reason, such as a value of the wrong type after a hand edit. A hand-edited file with a typo can make every later save fail while the screen keeps opening happily, because reading tolerates what writing cannot merge. If you edited the file recently, restore the backup and test the screen again before deeper checks.
That sequence, edit then silent failure, is common enough to check first whenever a config file has been touched by hand. The screen is rarely the culprit in these cases; it is reporting values the file can no longer hold.
Permissions on shared and managed machines
On a family or school machine, the account playing the game may not own the instance folder, especially when a parent or an IT setup installed it. The game then reads mods happily and writes nothing. The symptom mimics a mod bug while belonging to the machine's setup. If the timestamp test shows no file in the config folder ever changes, including the game's own options, suspect permissions at the folder level and have the account that installed the game check ownership, rather than reinstalling mods.
The mod that saves on world exit
A few mods write their config when a world closes or the game quits, not when the screen closes. With those, the timestamp test must wait for a full quit, and killing the game from the task manager loses the session's changes even though every earlier check passed. If a mod's settings hold within a session and vanish across restarts, test the quit path deliberately: change, quit through the menu, relaunch, look. A clean result there separates a save-timing design from a write failure.
Server play adds a variant: a mod may defer to server rules for shared settings and save only your client-side choices locally. An option that resets on every join, while others hold, is behaving as designed for multiplayer, and the mod's page usually says which options the server owns.
Starting over on one mod's settings
When a config file is suspected corrupt beyond a single value, the clean reset from the config guide is the decisive test. Move the file out, let the mod write a fresh one, and set your key options again in the screen. If the fresh file saves normally, the old file was the fault, and your backup of it remains useful as a list of the values you meant, even if the file itself is retired.
The difference between not saving and not applying
Two complaints sound identical and are not. In one, the value reverts when you reopen the screen: the save failed. In the other, the value holds in the screen but the game behaves as before: the save worked and the application did not, because the feature needs a world reload, a dimension change or a restart to pick the value up. Separate them before fixing anything. Reopen the screen first. If the value stands, stop troubleshooting the file and look for what the feature needs to re-read its settings; the mod's description of the option often names the trigger. If the value reverted, the file investigation from the main guide is the right road.
This distinction matters beyond one setting. Half the settings folklore in modding comes from players repairing saves that were never broken, and occasionally breaking them in the process.
Permissions, sync tools and read-only traps
A config file can be made read-only by accident: a backup tool restoring attributes, a sync service locking files while it works, or an overzealous cleanup. The screen then saves into a file the system will not let it write, and the game may not complain loudly. Check the file's properties if the timestamp test fails on an otherwise healthy setup, and check whether a sync tool watches the instance folder; syncing a live game folder is a recurring source of half-written files. Moving the instance out of synced storage, or pausing sync during play, removes the whole class.
On shared computers, ownership adds one more variant: a file created by an administrator account may refuse writes from a standard account. The fix is account housekeeping, not mod housekeeping, and it is diagnosed the same way, by the timestamp that will not move.
When the whole profile's settings reset
If every mod's settings reset at once, suspect the profile, not the files. A launcher that recreates the instance, a profile pointed at a fresh folder after an update, or a game directory moved by a cleanup tool all produce a clean config folder wearing the old profile's name. The identity routine from the profile guide settles it: prove which folder the running game uses, then look there. Your old config folder usually still exists at the old path, and copying the mod config files from it into the live folder restores every setting in one motion.
A repair routine that keeps your setup
- Close the game fully.
- Back up the instance's config folder to a dated folder elsewhere.
- In the live instance, check the mod's config file for a read-only flag and clear it if set.
- Launch, change one loud setting, leave the screen by its Done control and quit the game normally.
- Reopen the config folder and confirm the file's timestamp moved, then launch again and confirm the setting held.
If the timestamp still refuses to move after those steps, note the mod, its version and the file path, and take that evidence to the mod's issue tracker. You have ruled out the common causes, and the detail you gathered is what a maintainer needs.


