This mod can be used by Modpack developers to distribute default options and keybindings without overriding user changes on every modpack update.
Instead of shipping the options.txt directly, you will ship a "defaultoptions" folder in your modpack which contains the defaults previously saved through the /defaultoptions command.
This project is sponsored by Server.pro.
Need to host a modded server? Check out their plans here.
Features
- On the first run, users will start out with the options you configured - and future changes won't be overridden on updated
- Keybinds configured by the modpack will be set as new defaults, meaning changes made by users will persist even on updates
- The server list will be pre-populated with the server list provided by the modpack (and user changes will persist on updates, still)
Instructions
- 1. Configure the options, keybinds and server list as you would like them to be shipped in the modpack
- 2. Run /defaultoptions saveAll to save those options in the defaultoptions folder
- 3. Make sure you ship the defaultoptions folder, not the options.txt and servers.dat from the root directory
- 4. Fresh installations (meaning no existing options.txt) will now start out with your default options
If you are using FoamFix Anarchy Version, disable B:initOptions in the FoamFix config or else Default Options will not work. See this GitHub issue for more info.
Links
Can look into adding feature to allow multi keys? Alt and ctrl + a button, or __ + __
Meaning 'shift + b' to work, Vanilla doesn't allow this, only sort of does
- If you set that, but also have b set, hitting b will do both options
Currently there are no options I can find for this in forge 1.16.4/5, there is this fabric one only:
https://www.curseforge.com/minecraft/mc-mods/amecs
This would be amazing for modpackers, I've resorted to unbinding most keys bc simply, not enough viable options... ):
- Nor makes sense in my mind to bind a key randomly if not used much/at all, to make people have to go look for it anyways.. lol
In reply to ShootToKillSTK:
Forge already supports this out-of-the-box.
In reply to BlayTheNinth:
Really? It was not working for me, forge version 36.0.35, was having both activate when trying to do 'e' inventory then 'ctrl + e' for quark portable crafting, 'alt +e' not work either
I used the comment /defaultoptions saveKeys but it doesnt save my key bindings please help me
I used the comment /defaultoptions saveKeys but it doesnt save my key bindings please help me
When i type /defaultoptions_saveAll it saves options but it doesn't saves keybindings.
I go through the steps but a fresh installation only starts with Minecraft's default options. Where does the defaultoptions folder need to be? I have it in the configs folder.
Is it okay to do this more than once before shipping the modpack?
currently I get this error message:
As far as i can tell the Keybinds are not being saved. The keybind txt file has NONE behind everything even after running the command.
Every time i launch a fresh install with no options.txt, it doesn't set any of the default options, but if I go and click reset controls to defaults, then it sets them. Why is it not just doing this automatically? I have the Defaultoptions folder in the config folder in the modpack, yet it still doesn't save.
So if you use this with an older version of the game, will it also overwrite the controls if you open a different version of Minecraft? Maybe a version with Forge and a vanilla Minecraft install?
In reply to ennh1349:
If options.txt already exists, it will not overwrite anything. For keys, it will only overwrite the default key assignments (what you get when you reset a key to default).
Is this installed server side or client side?
In reply to pongpaktech:
Client-side only.
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?