DefaultSettings Mod — Guide

Mechanics

The mod operates by intercepting the game's startup sequence and checking for the existence of specific configuration files in the root directory.

The 'Local' Folder System

Instead of shipping options.txt or servers.dat in the root folder of a modpack, creators place these files inside the config/defaultsettings/ directory.

First Run Logic: When a player launches the modpack for the first time, DefaultSettings detects the absence of local configuration files and copies the defaults from its own folder into the root directory.
Update Preservation: On subsequent launches or modpack updates, the mod recognizes that the user has already established local settings. It will not overwrite these files unless specifically instructed to do so via the -of (Override Force) flag.
Profile Management: The mod can manage multiple profiles of settings, allowing creators to ship different configurations for different hardware levels (e.g., 'Low End' vs. 'Ultra' settings).

Modpack Creator Guide

To properly integrate DefaultSettings into a modpack, follow these steps to ensure user settings are preserved:

Configure the Game: Launch your development instance and set your desired keybinds, video settings (including Optifine or Iris shaders), and add any default servers to the server list.
Execute Save: Run the command /ds save. This creates a defaultsettings folder inside your config directory.
Verify Files: Ensure the following files appear in config/defaultsettings/: * options.txt (General game settings) * servers.dat (Server list entries) * keybindings.txt (Custom key assignments)
Exporting: When exporting your modpack, DO NOT include the options.txt or servers.dat files from the root .minecraft folder. Only include the config/defaultsettings/ folder.
Mod Configs: If you wish to ship specific mod configs as defaults, use /ds saveconfigs. This is particularly useful for mods like JourneyMap or sophisticated UI mods that store data outside the standard vanilla files.