Modpack Developer Tips

Taming modules.cfg

Due to the amount of content, granularity of content Charset provides, as well as my hesitancy to keep ideas which don't meet my standards around for very long, a fairly complex (relative to other mods) configuration system had to be built to faciliate all of this while not harming the experience for modpack developers and end users.

Charset's module configuration system is based around profiles. These provide a sane set of default settings for modpacks. There are four profiles:

The difference between TESTING and UNSTABLE really comes down to the level of initial testing/refinement a feature has received - UNSTABLE is far more likely to include features I consider unpolished. Which one you choose is up to you.

By the way - If you're unsure which profile to pick, you can always ask me!

In addition, you can manually force each module to be enabled or disabled in the "overrides" list - this is especially important as a few "niche" modules are off by default. They are marked as such, but their profile is still visible. The default setting for each override is DEFAULT, which means that Charset will decide whether or not to load the module itself, based on your profile configuration and whether the dependencies for a given module are present.