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 and the multiplayer server list exactly how you want them to look for a fresh install.
3. Join any 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 and leave the root-level options.txt and servers.dat 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
    extra/
      journeymap/
        ...

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.