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.
First, I'd like to say that this is a great effort, and makes modpacks much easier to manage.
I had an idea though. There used to be a mod called Starter Inventory, which has not been maintained in quite some time, but it basically just made it possible to start a new ssp world with a predefined inventory. I think a simple option along those lines would fit into this mod very well without really breaking the scope of the project, and would probably be extremely useful to the exact same audience that would need this mod. Just a thought.
Thank you so much, I'll be adding this to my next Modpack release.
does this also support default servers? Technic recently modified their launcher to filter out packs that include anything from the top level and break them.
Not at this moment, but I'll make it a thing at least for the 1.9.4 version.
Now added to the latest version for Minecraft 1.9.4.
Is default key configs broken? I've tried two times and it keep using the original values.
What version?
1.9.4
It works correctly for me. Are you running /defaultoptions saveKeys after setting up your key binds? You should see results via new keybind defaults in the Controls menu immediately.
Nevermind, found a bug that might have been the once you experienced. Fixed in next version.
I'm having a hard time understanding the local config format rules. What are B, I, S and D? What are the categories and sub-categories for? What does the asterisk(*) mean in the example file?
I just want to set my modpack so that ALL changes that a user makes to any of the cfg files are NOT overridden by updates. so would I do this like this
mod.cfg/*/*
for each of the config files?
Sorry if this sounds whiny at all, I am just very confused even after reading the documentation.
According to https://github.com/blay09/DefaultKeyConfig/issues/15 the local config feature seems to be broken at the moment and considering no one really ever used it I couldn't be bothered to fix it yet.
Anyways, the B,I,S,D prefixes are the same prefixes that are used in the configuration files. B is a boolean (true/false), S is a String, and so on. Also I don't think the local config feature is a good way of resetting *all* options - it's more meant for single options.
I may add a seperate thing where you can put files into a defaultconfig folder that will then get copied over on the first run.
Thanks for the reply! I like the idea of a default config folder. That would solve pretty much all of my problems.
A little help please! I have just created a modpack on Curse and thought I could use this to set the GuiScale from Auto to Medium.... Is this possible because if I save my config using the instructions above and then delete my options.txt file this seems to be the only setting that isn't picked up....
Cannot help think that I am missing something!
EDIT:
Bit of a hunt and I have found this in my log file!
Any ideas?
What version are you running on? This should have been fixed on version 3.0.7+.
Just updated the issues area on GitHub so shall continue the conversation here!
Can you just confirm for me that there is no working version for minecraft version 1.8.... The newer versions of the mod seem to be for versions above 1.8 only.
Default Options runs fine on Miencraft 1.8.9.
The 1.8.0 version of Default Options is no longer supported.
Fair enough.... I will have to wait for other mods to catch up. Thanks for the help!
Is it intentional that the modpack-update file doesn't get deleted after the first start of the modpack after the update and the user has to delete it manually if he wants to make changes?