How to Share Your Mod Settings and Pack Config With a Friend
Share settings by copying the config files of the mods involved, not your whole instance. Your friend needs the same mods at the same versions. Send the files from your config folder with a note of the game and mod versions, and have them back up their own config folder before dropping yours in.

What actually carries your settings
Your choices live in the config folder of your instance, one file per mod. The settings a YACL screen shows are written to the owning mod's file when you save. To share your setup for one mod, you need that mod's file. To share a whole pack's tuning, you need the config folder, or the parts of it your changes touched.
Files outside config rarely belong in a settings share. The mods folder carries the mods themselves, which your friend should get from the pack or the publisher so versions match exactly. Saves carry worlds, not settings. Options files from the game itself hold your video and control choices; include the game's options file only if your friend asked for those too.
Match versions before files
Config files are read by a specific mod version. A file written by one version usually loads in a nearby version, but option names change as mods evolve, and an ignored name means a silently lost setting. Before sending anything, agree on the pack version or the individual mod versions, and have your friend install those first. The cleanest case is the same published pack release on both machines; then the files are guaranteed to speak the same language.
Write the versions in your message with the files: game version, loader and the mod versions the configs came from. That note takes a minute and saves your friend from guessing when a setting does not appear.
Send and install, step by step
- Close your game and copy the chosen config files into a clearly named folder, for example lakeside-settings with the date.
- Send that folder by whatever channel you and your friend already use.
- Your friend closes their game and backs up their own config folder before touching anything.
- They copy your files into their instance's config folder, replacing the matching names.
- They start the game, open the settings screens and confirm the expected values are showing before playing.
The backup step on their side matters as much as the copy on yours. If a value behaves differently on their machine, for example a resolution-dependent HUD position, they can restore their file and adjust only that option.
What to leave out
- Account and session data. Nothing in a settings share needs anything from the launcher's account files, and those should never travel.
- Server lists with private addresses you would not post publicly. The game's server list lives outside the mod config files; share an address deliberately, not by accident inside a bulk copy.
- Files for mods your friend does not run. Extra config files are ignored, but they clutter the folder and confuse later troubleshooting.
- Your whole instance folder as a zip. It mixes versions, saves and settings into one heavy bundle nobody can audit.
A small, named set of files with a version note is the share that works. It is also the share your friend can verify, which keeps trust intact when something needs adjusting.
Agreeing the ground rules first
Settings carry taste. A friend may want your HUD layout but not your difficulty tweaks, your keybind choices but not your graphics values. Before sending a whole folder, ask which parts they want, and send per-mod files for just those. Small shares get installed; a forty-file dump gets postponed and then forgotten. The per-file structure of the config folder is a feature here. Use it.
Name the files' owner mods in your message, in plain words, so your friend can match them without decoding filenames. A line like the file named after the map mod holds the map settings prevents the one mistake that ruins an otherwise clean share: the right file in the wrong game's folder.
When you are the receiver
Receiving a config is the mirror discipline. Back up first, install second, verify third, and thank fourth. If a shared file misbehaves, restore your backup and set the one or two values you actually wanted by hand, reading them from the shared file as a reference. Files are a transport, not a contract; your setup stays yours.
Sharing a whole pack setup, not just settings
Sometimes a friend wants your entire setup: pack version, added mods and settings together. Share it as a list plus files, not as a copy of your instance. The list names the pack and its version, the mods you added with their versions and the library builds you settled on. The files are the config folder. Your friend builds the same set through their own launcher, which guarantees their folders and records agree, then drops in your config. The result is identical where it matters and clean where copies would have carried your machine's clutter.
That method also respects the pack author's work: the pack itself travels through its own channel, and your additions are visibly yours.
Preset files other players publish
Some communities share preset config files for popular mods. Treat a stranger's preset like any downloaded file: read it before installing, in a text editor, and confirm it contains only option names and values for the mod you expect. A JSON config cannot run code, but it can contain surprising values, such as links in text fields a mod displays. A minute of reading is the whole security review, and it doubles as a preview of the settings you are adopting.
What to send, as a checklist
A complete share has four parts. The pack's name and exact version, so your friend builds on the same base. The list of mods you added or removed, with versions, including the library build you settled on and why. The config files themselves, zipped from the instance's config folder, limited to the mods whose settings you mean to share. And one line of instructions: install the pack, add the listed mods, launch once, quit, then drop these files into the config folder and launch again. That order matters: launching once first lets each mod write its default file, so your shared file replaces a real file rather than landing in a folder the game has not built yet.
Send the checklist as text, not as a screenshot, so versions can be copied exactly. Numbers in screenshots get misread; numbers in text get pasted.
Receiving a shared config graciously and safely
On the receiving side, keep your current config folder as a backup before overwriting anything, even when the sender is trusted and the setup is identical. Versions drift between friends more often than either expects, and a file written by a newer mod version can contain options yours ignores, or miss options yours needs. After installing, open each affected screen once and skim the values. The screens show you what actually landed, in the mod's own terms, which is a kinder verification than comparing file text.
If a shared setting behaves oddly, remove just that mod's file and let it regenerate, then re-enter the two or three values you cared about by hand. Sharing is a shortcut, not a contract.
Licences and credit when sharing wider
Sharing a config with a friend is one thing; publishing a tuned setup for strangers is another. Config values are yours to share, but a pack's files and a mod's assets are not, so publish your changes as a config and a list, never as a re-uploaded pack. Credit the pack and the mods by name with their versions. That practice keeps you inside every licence involved and, not incidentally, makes your share more useful, because readers can rebuild it on current versions instead of inheriting your frozen files.
A shared config is a snapshot, not a subscription
Send a config as a finished snapshot of your choices today, and receive one the same way. Neither side should expect the file to track future changes; when your tuning moves on, send a fresh copy with a new date in the name. Snapshots with dates cannot be confused with each other, and the receiver can always tell which of your setups a file belongs to. Most sharing confusion is really version confusion wearing a friendly face.
When settings refuse to travel
If a setting does not appear after the copy, work through three checks: the file landed in the live instance's config folder, the mod versions match on both sides, and the option still exists under the same name in that version. The settings-not-saving guide's timestamp test confirms whether their game is reading the file at all. A file that updates when they change a setting in game is the right file; if their changes save but yours never showed, the option name changed between versions and the value must be set again by hand.


