Where YACL Config Files Live and How to Edit One Safely
Your settings live in the config folder of the instance you play, in one file per mod, usually JSON named after the mod. YACL itself keeps no master settings file. To edit safely: close the game, copy the file as a backup, change values in a plain text editor, and keep the file's structure exactly as you found it.

The config folder belongs to the instance
Every instance has its own config folder beside its mods folder. Two profiles running the same mod hold two separate sets of choices, which is why a setting changed in one pack does not follow you to another. Open the folder from the profile you play, using the same open-folder route as an install, and look inside config. That folder is the whole map; there is no second settings location elsewhere on the machine for these mods.
Inside, files are named for their owners. A mod's file typically uses the mod's id or name with a .json extension. ChatPatches, a mod whose documentation describes its YACL-based setup, keeps its settings in config under its own name in exactly this pattern. If you cannot tell which file belongs to your mod, sort by modified time and change a setting in game; the file that updates is the right one.
What YACL does with the file
YACL gives mod authors a serializer that reads the file when the mod starts and writes it when you save changes in the settings screen. The screen and the file are two views of the same values. That is why a change made in the screen appears in the file, and why an edit made carefully in the file appears in the screen the next time the game starts.
It also means the game is the file's usual writer. Editing while the game runs invites a lost edit: the game may overwrite your change when it saves on exit, using the values it loaded at start. Always edit with the game closed.
Before you edit: the backup habit
- Close the game completely.
- Copy the mod's config file into a backup folder named with today's date, outside the instance.
- If you plan several experiments, copy the whole config folder. It is small, and a full copy makes every experiment reversible.
A backup turns editing from a risk into a routine. Any change you dislike can be undone by copying the dated file back over the edited one, with the game closed in both directions.
Editing without breaking the structure
Open the file in a plain text editor, not a word processor. JSON is punctuation-sensitive: values sit in quotes, entries are separated by commas and groups are wrapped in brackets. Change only the value side of an entry, a number, a true or false, or the text inside quotes. Leave the names, commas and brackets untouched. Save the file with the same name and extension, and make sure the editor does not add a .txt ending.
If the game rejects an edited file, most mods log a parse problem and fall back to defaults, which looks like all your settings vanished. Restore the backup copy and the settings return. That forgiving behaviour is another reason the backup step is not optional.
Resetting one mod to defaults
To reset a single mod, close the game and move its config file out of the config folder. The mod writes a fresh file with its defaults on the next start. Your other mods keep their settings because their files are untouched. Compare the fresh file with your backup if you want to recover individual choices: copy single values across, keeping the structure of the fresh file.
Deleting the whole config folder is the blunt version of the same move. It resets every mod at once and is rarely necessary. Prefer the per-file reset unless several mods are misbehaving and you suspect a shared cause, such as a pack update that changed many formats at once.
Reading a JSON config without fear
Open a typical file and you will see pairs: a name, a colon and a value, grouped inside braces. Numbers are plain, switches are true or false, and choices are words in quotes. You do not need to understand the whole file to change one value safely. Find the name that matches the option you saw on the settings screen, change only what follows its colon, and leave every comma and bracket where it stands. If the name you want is absent, the mod may store that option under a group heading; search the file for a word from the option's label.
After an edit, the settings screen is your proofreader. Launch, open the screen and look at the option. The value you typed should be showing. If the screen shows a default instead, the game could not use your value, usually for a structure slip, and the backup file restores your previous state in one copy.
Config folders in packs
Packs ship config folders with the author's tuning already inside. Those files are part of the pack's tested set, like its library versions. If you reset a pack mod's config while troubleshooting, expect the pack's custom balance to go with it, and prefer restoring the pack's file from a fresh pack copy over running on defaults. Your backup habit covers this: back up the pack's config folder before the first change you make to any of it.
Config files and version control for the curious
Players who keep many profiles sometimes track their config folders with simple dated copies before big changes: before a pack update, before a settings experiment, before lending the setup to a friend. The folder is small and the copies are cheap. What matters is the naming: pack name, date and one word about the change. A shelf of those copies turns configuration from a state you fear losing into a history you can walk back through.
That history also documents taste. Comparing a config from months ago with today's shows which options you actually settled on, which is useful when a fresh install asks you to choose everything again.
Files you should not edit
Not every file in the config folder is a settings file you should touch. Some mods keep data files beside their settings: caches, saved presets from other players, or files the mod rewrites constantly while running. Edit the file whose name matches the mod and whose contents read as option names and values. If a file's contents look like long lists of world data or unreadable text, close it and leave it alone. The settings screen remains the safe interface for anything you cannot identify.
Finding one mod's file among many
A busy config folder holds dozens of files in several formats. To find one mod's file, sort by name and look for the mod's id or its plain name; most authors name the file after the mod, sometimes with a suffix marking client, common or server scope. If the name hunt fails, sort by modification time after changing a setting in the screen: the file that just changed is the mod's file, whatever it is called. That timestamp trick is the universal locator, and it works even when a mod stores its settings inside a subfolder named for the author or the modpack.
Once found, note the exact filename in the profile record. Config filenames are stable across a mod's versions far more often than its screen layout is, so the note stays useful through updates.
Client, common and server files
Mods that split their settings keep up to three files: client options that affect only your display, common options that shape gameplay, and server options for dedicated servers. On a single-player setup all three live in your instance. Knowing the split explains a setting that seems to ignore you: you edited the client file for an option the mod reads from common. The screen avoids the trap by showing each option in its proper place; hand editors must respect the split themselves, which is one more reason the screen is the recommended tool and the file is the diagnostic.
What a JSON file should look like
A healthy JSON config reads as a list of names with values: numbers, true or false switches, and short texts in quotes, grouped in neat brackets. If you open a file and see one endless line, that is normal minified formatting, not corruption. If you see the same option name twice with different values, or brackets that plainly do not close, the file has been hurt, usually by an interrupted write. Do not repair structure by eye. Let the mod regenerate the file, then re-enter your values in the screen, using the damaged file, opened read-only, as the list of what you had.
Moving settings between instances
A config file can travel. Copy the mod's file from one instance's config folder into another's, with both games closed, and the second instance picks up the same choices, provided both run the same mod version. Version differences are the catch: a newer mod may rename options, and unknown entries are ignored or rewritten on the next save. Copy, launch, open the settings screen and confirm the values arrived before you trust the transfer.


