DefaultSettings - Usage

Attention! This guide is outdated and may only be used for Minecraft versions below 1.16!

Disclaimer:

This mod is for modpack creators only! It doesn't add items, entites, blocks or any type of structure. Still here? Alright, then proceed down below.

Installation:

It's fairly easy to install DefaultSettings, all what you have got to do is place the mod's jar file in your installation's "mods" folder (1.6+) or place it in the "coremods" folder (1.4+). In case you're using the Curse client, DefaultSettings can be updated quite simply - so no problems there.

First Startup:

As you start up the mod for the first time, it will show you a quick tutorial - skip it when following this guide further.In the following it's highly advised to open the DefaultSettings GUI once to get familiar with it's layout. But better don't click too many buttons. “If my calculations are correct, when this baby hits [512 clicks] per hour, you're gonna see some serious s***.”

Ok, let's do some default setting'ing:

While setting up your pack you don't even have to mess with DefaultSettings. But once you're ready to ▶️ export ◀️ your pack, it's coming into play. Let's start simple with default keys (keybindings), options (like FOV, sounds and FPS) and servers. Those three can be accessed via the default "Save" tab. Clicking on the buttons adds them to your pack. In case you change those - let's suppose you change your FOV - you click them once again. Then you can override the originally saved version. Depending on which of those three available features you activate, your users will get those settings on The First Boot Of The Pack! After that they can change them locally, they won't get overridden by a pack's update (e.g. that normally happens with modpacks on Twitch). But if you as the pack's creator change the keys, options or servers - those will then Get Shipped To The Users! So stuff only get's overridden on your user's end once you actually change the files.

And what about that weird Config Tab?

First off, if you're not interested in shipping Configs with DefaultSettings, then DON'T skip this guide right here! Read the "Profiles" and most importantly the "Export Mode" section!

Comparable to the "Save" Tab, the "Config" Tab does the same thing - just with configs. This means that you can select certain config files and folders. Those will be treated like the stuff from the "Save" section. This means that ONLY the selected entries will be shipped once, and won't get overridden unless you as the pack's creator edit them.A search bar and also a bulk selection button should help you in the process of marking which configs should be managed by DefaultSettings and which not. Remember: Configs which aren't selected will be overridden on the user's end with every packupdate.

Did someone say Profiles? I wonder to what degree you can eat it:

First off, if you're not interested in Profiles with DefaultSettings can manage, then DON'T skip this guide right here! Read the "Configs" and most importantly the "Export Mode" section!

When opening the "Profiles" Tab for the first time, you'll see a default profile. That one is marked by a little blue circle - meaning that your users will use that profile by default. If you now want to have multiple sets of configuration your users can play your pack with, then simply add a new profile. After selecting the new profile, you have to restart your client and are ready to go. The default profile is now deselected and you can edit your fresh one. By rightclicking a profile's entry in the list you can also manage it - e.g. rename or delete it. With the same move you can also make every profile the new main profile, marking that one with the little blue circle.

Heck, how do I export the stuff now? I'm confused 🙁:

First off, maybe consider reading the "Configs" and "Profiles" section first before exporting the pack.

Okay, it's quite simple. Once you're ready to export your pack just activate the "Export Mode" with the left sidebar menu. As a consequence, you can no longer interact with most of the GUI - that's intended. Now export the pack as you normally would. Make sure that you don't export the "ds_private_storage.json" (.minecraft/ds_private_storage.json) though, that would break the pack. After you have finished, disable the export mode again to proceed using the pack. Et voilà, you did it! Now just activate the "Export Mode" only again for the next update - which should be exported just like the first one!

Shared Configs / Options:

Coming Soon ~