v1.0.0-alpha.4+1.21.1
Curse Maven Snippet
What's new
1.0.0-alpha.4 — Configs in subfolders
Fourth alpha. ConfigSwitch now looks inside the subfolders of config/,
not just at the files sitting directly in it.
Configs in subfolders are found
Plenty of mods keep their configs in a folder of their own — config/jei/,
config/NoChatReports/, config/ModernUI/. Those files used to be invisible to
ConfigSwitch; now they show up in the list and sync like any other config.
- A file is grouped by the folder it sits in, so
config/jei/blacklist.jsonlands in the jei group. - In a real 114-mod pack this brought in around two dozen folders that were previously missing from the list entirely.
Not every folder is yours to sync
Subfolders also hold things that shouldn't travel between packs. Those are left alone:
- Per-world and per-server data —
world/, folders named after a server - Caches and generated files — models, textures, resource packs
- Settings a modpack author ships with their pack — spawn rates, world generation, custom menus. Those are part of the pack, not part of your setup, and carrying them between packs would break the pack's balance.
Flat configs are untouched
If all your configs sit directly in config/, nothing moved: same groups, same
repository layout, same backups. Your existing repository works as-is — no
migration.
Known limitations
- Minecraft 1.21.1 only, Fabric only, Windows only
- Mod configs take effect after a game restart —
options.txtapplies immediately - A config whose name doesn't resemble its mod and that isn't in the built-in mappings still ends up in Uncategorized
- Some mods store their configs under a name that doesn't match the mod at all —
WTHIT keeps its files as
waila_*. Those can't be matched automatically - Classify only offers mods you have installed
All Relations
- All Relations
- Embedded Library
- Optional Dependency
- Required Dependency
- Tool
- Incompatible
- Include