Default Options in All the Mods 11

Same as in the All the Mons 1.3.0 guide

Default Options is a behind-the-scenes tool for modpack makers. It lets a pack ship default game options and keybindings without overwriting the settings you've already changed every time the pack updates.^[1]

Normally, shipping an options.txt with a pack would reset your settings on every update. Instead, pack developers include a defaultoptions folder, which holds the defaults saved with the /defaultoptions command. That way you start out with the pack's settings, and your own changes stick around afterwards.^[1]

What it does for you

• On your first run, you start with the options the pack developer configured, and later updates won't override them.^[1]
• Keybinds set by the pack become new defaults, so any keybind changes you make persist through updates.^[1]
• The server list comes pre-populated with the pack's servers, and your own changes to it persist through updates too.^[1]

Version and requirements

This pack includes Default Options 21.1.8, the NeoForge build for Minecraft 1.21.1. It requires Balm, which has to be installed alongside it.^[1][2]

For pack makers

If you build your own pack, the workflow is simple: set up your options, keybinds and server list, then join a world and run /defaultoptions saveAll. That saves everything into the defaultoptions folder in the config folder, where it should stay. Leave the root options.txt and servers.dat out of the pack, and fresh installs will start with your defaults.^[1]

Where it fits in progression

It doesn't add items, blocks or gameplay, so there's nothing to craft or unlock. It simply works in the background to set up your first-launch options.^[1]

Unverified This mod is not on the ATM Star quest path, and no quests in this pack involve it. No in-jar guidebook was found for it either.

Same as in the All the Mons 1.3.0 guide

Good news: there's nothing to craft or gather for this mod. Default Options doesn't add items, and no recipes or quests in this pack involve it. Your first steps here are about what it does for your settings.^[1]

What it does for you

Default Options lets a modpack ship default options and keybinds without overwriting your own options.txt every time the pack updates. Instead of shipping that file, the pack ships a "defaultoptions" folder with the saved defaults.^[1]

• On your first run, you start out with the options the pack developer configured, and later updates won't override your changes.^[1]
• Keybinds set by the pack become new defaults, so any keybind changes you make persist through updates.^[1]
• Your server list is pre-populated with the one the pack provides, and your own changes to it persist on updates.^[1]

If you build your own pack

If you want to ship your own defaults, the mod requires Balm to be installed alongside it. Then follow these steps.^[1]

1. Configure the options, keybinds and server list the way you want them shipped.^[1]
2. Join any world and run "/defaultoptions saveAll". This saves your current options into the defaultoptions folder, which lives in the config folder and should stay there.^[1]
3. Leave options.txt and servers.dat from the root directory out of your pack.^[1]
4. Fresh installations, meaning ones with no existing options.txt, will now start out with your defaults.^[1]

Unverified The sources don't say which specific options, keybinds or servers this pack ships as defaults, so check your own settings on first launch.

Same as in the All the Mons 1.3.0 guide

Default Options is a utility mod for modpack developers, not a content mod. It adds no machines, multiblocks, power, fluids or item automation. Its whole job is to give players the pack's default options and keybinds on a fresh install, without overwriting their own changes on later updates.^[1]

How it works

Instead of shipping an options.txt directly, a pack ships a "defaultoptions" folder. That folder holds the defaults previously saved with the /defaultoptions command. The mod needs Balm installed alongside it.^[1]

• On the first run, players start out with the options the pack developer configured. Future pack updates won't override them.^[1]
• Keybinds set by the pack become new defaults, so changes players make to their keybinds persist across updates.^[1]
• The server list is pre-populated with the one the pack provides. Players' own changes to it persist on updates too.^[1]

Saving defaults (for pack makers)

1. Configure the options, keybinds and server list the way you want them shipped.^[1]
2. Join any world and run /defaultoptions saveAll. This saves your current options into the defaultoptions folder, which sits in the config folder and should stay there.^[1]
3. Leave the options.txt and servers.dat from the root directory out of your pack.^[1]
4. Fresh installations, meaning ones with no existing options.txt, will now start out with your defaults.^[1]

Unverified The sources don't say which options, keybinds or servers this pack ships as defaults, and the pack has no config files for this mod. Any further mechanics beyond the above are unverified.

All the Mods 11 0.8.0-beta ships Default Options 26.1.2.2, using the NeoForge build of the jar. The mod has been in the pack since 0.0.14 or earlier. Here are the changes from the mod's own changelogs, newest first.^[3]

• 26.1.2.2: Fixed options from the extra folder not being applied correctly on all Fabric mods, because Fabric mod initialization ran earlier. The changelog describes this fix for Fabric.^[4]
• 26.1.2.1: Added a defaultResourcePacks option, as a more stable alternative to a default options.txt.^[5]
• 26.1.0.1: Updated to Minecraft 26.1.^[6]

Why defaultResourcePacks matters

Some launchers manage options.txt on their own, so it becomes unclear whether its initial state is what the user intended. Resource packs now have their own option, so Default Options can manage them without interfering with an existing options.txt.^[5]