If you are using FoamFix Anarchy Version, disable B:initOptions in the FoamFix config or else Default Options will not work. See https://github.com/blay09/DefaultOptions/issues/25 for more info.
Useful Links
Setting up Default Keys
- Configure the keys how you'd like them to be in the default configuration
- Run the "/defaultoptions saveKeys" command: the file defaultkeys.txt will be saved in the config folder
- Make sure to ship the defaultoptions folder inside the config directory, and NOT the options.txt from the root directory in your modpack. Victory!
Check the Controls GUI to see that the default settings have updated. Players will now start with these keys by default.
Setting up Default Options
- Configure the options (e.g. FOV, video and audio settings) how you'd like them to be in the default configuration
- Run the "/defaultoptions saveOptions" command: the file defaultoptions.txt will be saved in the config folder
- Make sure to ship the defaultoptions folder inside the config directory, and NOT the options.txt from the root directory in your modpack. Woohoo!
Fresh installations of your pack (=> no existing options.txt) will now get the default options you specified.
Setting up Default Servers (Minecraft 1.9.4+)
- Set up the servers how you'd like them to be in new installations
- Run the "/defaultoptions saveServers" command: the file servers.dat will be copied into the defaultoptions folder
- Make sure to ship the defaultoptions folder inside the config directory, and NOT the servers.dat from the root directory in your modpack. Victory!
Setting up Default Configs (Minecraft 1.9.4+)
If you want to set up your modpack in a way that lets users change specific config files without having them overwritten by updates, you can put those files into the defaultoptions folder rather than the config folder. Those files will only be copied over into the config folder on the first run of the pack. Sadly Minecraft's mod configurations aren't standardized enough to provide a more complex solution without having lots of breakage.
Is this installed server side or client side?
what's the benefits of using this vs options.txt and optionsof.txt and the config folder?
In reply to Wohlf_craft:
If you as a modpack author publish a pack with options.txt included, every time the modpack updates all users will also have their options.txt overwritten again, undoing any changes to keybinds or options they may have made.
In reply to BlayTheNinth:
Is there a way to manually reset it if a pack user is having issues?
In reply to BlayTheNinth:
In reply to BlayTheNinth:
And how does the defaultconfigs work?
In reply to Wohlf_craft:
The pack user can just delete the options.txt file generated for them, then it will regenerate from the default options.txt.
Default configs are no longer a part of Default Options in 1.14+, as Forge itself now provides default configs. They're basically just copied into the config folder on first startup.
For 1.14, does this mod copy world/server configs?
In reply to thegiggitybyte:
No, as Forge now has native handling for that in its defaultconfig folder.
In reply to BlayTheNinth:
Ah. I wasn't aware that was the purpose of that folder. Thank you.
Sorry this is a dumb question but what does the author mean by "Make sure to ship the defaultoptions folder inside the config directory, and NOT the options.txt from the root directory in your modpack." I couldn't really find videos on how to use this mod.
In reply to chris221d:
When you're making a modpack, you select the files to be included with the modpack. What I mean is to not include the options.txt from within the Minecraft folder there.
Can I use it in my modpack. I will leave a credit in the list of mods
defaultoptions saveServers or /defaultoptions saveServers only gives me unknow command any ideas forge latest version of 1.12.2 and if you want more info lemme know any help is appriciated
I am already trying this mod for a while now but I can't get it to work like it should I guess. I make all my key configs and the options like music and video settings and then I go in game and execute the commands. The two configs (options and keybinds) are created in the defaultsettings folder in my config folder but when I play with a new instance without any configuration file, it is not taken from the mod. Only some controls are taken (not even all) but the options don't change, not the music, not the video settings, not the FOV. What am I doing wrong? The configs have to be in "modpack/config/defaultsettings" right? And I don't need to rename them or something?
Hello
Does your mod makes a config file of the keys only or graphic/sound options too please ?
In reply to Finelarme9:
It can create a default for the options.txt (which contains graphic/sound options etc.) as well.
In reply to Finelarme9:
judging by the splash image above, I think it supports everything
That is exactly what I was looking for. Perfect.
Is it possible to define the "java memory" that will be used in game with such mod ?
In reply to Finelarme9:
The memory to be assigned to Java must be configured before Minecraft launches, at which point the mod isn't loaded yet, so it's not possible.
In reply to BlayTheNinth:
Ok I understand. Java settings are the 1st step before running the game. Anyway your mod is awesome. Thank you again.