How to Stop New Mods From Generating Their Own Configs

Adding mods to an existing pack often means each one writes a fresh config with values you did not choose. Configured Defaults prevents this by supplying your own files before the mod gets a chance to create its defaults.

Pre-Seeding the Config

Before launching with a new mod, run the pack once so the mod generates its config, then tune that file to your liking. Copy the tuned file into configureddefaults at the matching path, for example configureddefaults/config/modname.toml. On the next clean launch, the mod finds the file already present and uses it instead of writing its own.

Handling Server and Client Sides

Some mods split configs into common, client, and server files. Mirror each one into configureddefaults under the same names so all three are seeded. For servers, place the folder at the server root; the mod behaves the same way there.

Keeping It Maintained

When you update a mod and it adds new config keys, your old file may be missing them. The mod will not merge keys, so review the generated file after an update and fold any new options into your template. This keeps your pack's behavior predictable and avoids surprises where a mod silently falls back to defaults for options you never set.