[1.16.4/5] Need to document new config system for pack authors
Wizelf402 opened this issue ยท 6 comments
1.16.4 - 4.0.4.1
Forge Version: 35.1.37
So, I've been experimenting with using Dynamic Surroundings to add custom music and fog to the world for my modpack. I've replicated the required steps, but I couldn't find anything in my config file for "external configuration files", and when I started up the game neither the external configuration setup or my resource pack worked. Any help?
This is my current config, atm.
dsurround.zip
The layout of the config files have changed from 1.12.2. I haven't published docs on the new system. This folder gives you an idea of the layout and the files. Once you have the files you can drop them into a specific location on disk and it will find it. The path you want to drop them in would be ./minecraft/config/dsurround/config/dsurround/yourfileshere. Yes, the path is kinda wordy with the configs and dsurrounds. :)
Gotcha, gotcha. So, uh... how exactly do I go about usin' this? Is it the same format for stuff as before?
1.16.x does not have battle music. This would require server side support to make work. As for the format it is generally the same. Prior the config had a bunch of high level elements, such as "biomes" and "blocks". They were split into different json configs.
As for using, during mod load or connecting to a server, the config directory on disk is automatically checked. Using the example path ./minecraft/config/dsurround/config/dsurround/yourfileshere, the bolded folder is actually a mod ID. Since Dynamic Surroundings is installed, "dsurround" will always be processed. The configs underneath will be merged in with other config information.
If there is another mod, say "abc" that is installed, you could drop configs specific to "abc" in the path ./minecraft/config/dsurround/config/abc/yourfileshere. This is important because if Dynamic Surroundings has built in support for a mod, the configs on disk will replace (not merge) the configs provided by Dynamic Surroundings. This is so a mod pack author (or resource/client side data pack author) can easily override what DS has configured.
EDIT: For completeness, another mod could provide DS configs within its asset folders using the same general path scheme and file layout. As with configs on disk, if DS has built-in configs for that mod, the other mod will replace whatever DS has within its own assets. If there are also configs on disk in the config directory, those configs will replace both what DS has configured as well as any datapack configuration.
EDIT2: Figured I would throw this out there as well. As you develop the JSON files in the config directory you can dynamically reload while in game by reloading resource assets. (I can't recall the Minecraft key sequence to do this.) Once you are happy with the result, you can move those configs into a resource pack, with the JSONs to be loaded from client side assets. You can then release the resource pack for whatever purpose you have.
Gotcha... So, uh, another problem. Now that I'm using this, when I try to edit biomes.json in the external config, it just doesn't work. I've dumped biomes, but it just says "not hooked up"
this is what biomes.json looks like right now btw
[
{
"conditions": "biome.isEnd",
"_comment": "Adds custom white End Fog, baby!",
"fog": true,
"fogDensity": 1.0,
"fogColor": "250,250,255"
}
]