Commands

Default Options writes packaged defaults into config/defaultoptions when one of the following commands is run.

Configure your client first, join any singleplayer world, then run the command that matches what you want to capture. These commands are intended to be run from an integrated singleplayer world, not on a multiplayer server.

/defaultoptions saveAll

Saves all built-in default categories in one pass:

• config/defaultoptions/options.txt
• config/defaultoptions/keybindings.txt
• config/defaultoptions/servers.dat
• selected resource packs in the Default Options config

Use this when you are preparing a pack from scratch and want to capture the whole client setup at once, including a pre-filled list of multiplayer servers and selected resource packs.

/defaultoptions saveOptions

Saves non-key client options to config/defaultoptions/options.txt.

This is the right command when you want to update packaged gameplay, UI or graphics defaults without touching keybinds or the server list.

Built-in support also includes supported mod option files such as OptiFine and ViveCraft, which are loaded from the main config/defaultoptions folder together with the normal options set.

/defaultoptions saveKeys

Saves keybinding defaults to config/defaultoptions/keybindings.txt.

Use this after rebinding controls if you only want to ship a new default key layout.

Default Options treats this file as the packaged default key layout. Existing player changes are preserved when that key was already present in the player's options.txt, while new or previously unseen keybinds can still receive your packaged defaults after a pack update.

/defaultoptions saveServers

Saves the current multiplayer server list to config/defaultoptions/servers.dat.

Use this when you want fresh installs to start with a curated server list without changing other packaged defaults.

/defaultoptions saveResourcePacks

Saves the currently selected resource packs to the defaultResourcePacks config option.

Use this when you want fresh installs to start with a curated resource pack selection. Default Options stores resource pack repository IDs, so the resource packs themselves still need to be shipped normally with the pack. For file-based packs, the configured ID is usually file/<pack name>; plain file names can also be resolved when the matching file pack is available.