A Library Mod for Structure configs

• Easy Structure Config System
• Data support
• Runtime Datapack
• Datapack Loading

First create the folder where you will put your files for cristellib.

• For modpack makers, it'll be in the instance folder, in config/cristellib/data.
• For modders, it'll be /data/cristellib.

In your folder you'll have to make another called structure_configs. In this folder you will create files which will add configs for the structures you want. To create a config create a new json file the name of the file will be the name of the config file later. The file structure should look like this:

{
  "name": "",
  "subPath": "",
  "header": "",
  "config_type": "",
  "comments": {
    "ancient_cities": "A dark city at the bottom of the World",
    "buried_treasures.spacing": "Set the spacing of the buried treasure structure set"
  },
  "structure_sets": [
    {
      "modid": "minecraft",
      "structure_set": [
        "minecraft:ancient_cities",
        "minecraft:buried_treasures"
      ]
    },
    {
      "modid": "t_and_t",
      "structure_set": [
        "towns_and_towers:towers",
        "towns_and_towers:towns"
      ]
    }
  ]
}

• "subPath" specifies the sub folder in the config folder where the file will be located. E.g. if you put there "cristellib" your config will be in /config/cristellib/.
• "config_type" specifies, if the config will be for editing the placement (PLACEMENT), or if it is for enabling/disabling (ENABLE_DISABLE) a structure (there is no combined version yet).
• "structure_sets" in this array you have to put every structure set, which should be in the config. The "modid" specifies in which mod container the structure set file should be searched, and the "structure_set" parameter defines the location.

• "name" changes the name of the config file.
• "header" is the text, which will be at the top of your config file.
• "comments" is a map where the keys indicate the location where the comment should appear.

In your folder you'll have to make another called data_packs. In this folder you will create files which will load the datapacks you want. In the folder you need to create a new json file with any name you like. The file structure of the file should look like this:

{
  "location": "modid:a_folder/pack_folder_name",
  "display_name": "Display Name of your Pack",
  "condition": [
    {
      "type": "mod_loaded",
      "mod": "wwoo"
    }
  ]
}

or like this:

{
  "packs": [
    {
      "location": "modid:a_folder/pack_folder_name",
      "display_name": "Display Name of your Pack that loads above the other one",
      "condition": [
        {
          "type": "mod_loaded",
          "mod": "waystones"
        }
      ]
    },
    {
      "location": ""modid:a_folder/pack_folder_name2",
      "display_name": Display Name of your Pack that loads below the other one",
      "condition": [
        {
          "type": "mod_loaded",
          "mod": "waystones"
        }
      ]
    }
}

• "location" specifies the mod file and the folder where the datapack is located. E.g. if you put there "towns_and_towers:resources/t_and_t_wwoo_tag_patch" cristellib will try to load a pack in the mod file "towns_and_towers" and in it's subfolder "resources/t_and_t_wwoo_tag_patch".
• "display_name" specifies the name of the pack shown in the datapack selection screen.

• "packs" an array that allows packs to be loaded in a specific order. The pack at the top will be loaded above the others and so on.
• "condition" in this array you put every condition which is required for the pack to load. "type" defines which type of condion comes next.

• "mod_loaded":
  • "mod" is the modid of the mod that must be present for this condition to be true.

If you need more conditions or you have other feature suggestions contact me!