How to Ship Default Configs to Players in a Distributed Modpack

When you hand your modpack to other people, you want them to start with your tuned settings rather than whatever a mod generates on first launch. Configured Defaults makes this possible by treating the configureddefaults folder as a template that fills in anything missing.

Preparing the Pack

Set up your own instance the way you want players to experience it. Tune every config, then copy the resulting files into configureddefaults using the same relative paths they occupy in the live directory. Include options.txt if you want to control keybinds, video settings, or language from the start.

Why It Works for Distribution

Because the mod only copies files that do not already exist, players who later edit a config keep their changes on subsequent launches. New mods you add to the pack in a future update will also pull their defaults from the folder instead of generating random ones, which keeps everyone consistent.

Packaging Notes

Keep the configureddefaults folder inside the instance you distribute, not buried in a separate archive players have to extract manually. Verify the paths are relative to the game root, not absolute, so the pack works regardless of where someone installs it. Test by launching a clean copy of the pack and checking that your settings appear without any manual copying.