Getting Started

The normal pack-author workflow looks like this:

1. Start from a clean client profile with the same mods and config versions that will ship in the pack.
2. Configure options, keybinds, resource packs and the multiplayer server list exactly how you want them to look for a fresh install.
3. Join a singleplayer world and run /defaultoptions saveAll.
4. Add any extra defaults that are not covered by the built-in handlers to config/defaultoptions/extra.
5. Include config/defaultoptions in the pack, but leave the root-level options.txt, servers.dat and defaultoptions.journal.json out of the exported files.
6. Test the pack on a fresh instance before release.

The resulting structure should look like this:

config/
  defaultoptions/
    options.txt
    keybindings.txt
    servers.dat
    optionsof.txt
    optionsviveprofiles.txt
    extra/
      journeymap/
        ...

optionsof.txt and optionsviveprofiles.txt (for Optifine and Vivecraft) are only created when those supported option files exist in the configured instance.

The extra folder is optional, but when you use it the folder structure inside it must match the real Minecraft game directory.

For example, JourneyMap defaults belong in config/defaultoptions/extra/journeymap/..., not directly in config/defaultoptions.

After copying an external mod's files into extra, remove anything that should not become a packaged default, such as log files, caches or user-specific data folders.