Deposits

Note: EE does not come with any pre-configured deposits, and therefore creation of deposits should be completely done by the modpack developer from scratch.

  • Locate the emendatusenigmatica\deposit config folder inside the root config folder.

  • Create a *.json file inside this folder for each deposit you wish to add to the game.

  • You can create multiple deposits for the same material with different generation options.

Below you will find a more detailed break down of the Deposit Data object, and a brief explanation of each data field. An example of a complete deposit file can be found here.

Deposit Core module:

REQUIRED FIELD
"type": string // example: "type": "emendatusenigmatica:geode_deposit"

Determines the type of the deposit. At the moment, there are 5 available deposit types: "emendatusenigmatica:vanilla_deposit"

"emendatusenigmatica:sphere_deposit"

"emendatusenigmatica:geode_deposit"

"emendatusenigmatica:dense_deposit"

"emendatusenigmatica:dike_deposit"

with more deposits planned for future updates.

REQUIRED FIELD
"dimension": string // example: "dimension": "minecraft:the_end"

Identifies in which dimension should this deposit generation take effect. You can obtain the dimension resource location in-game by using /execute in and a list of dimension resource locations will be available for you.

"biomes": [ string ] // example: "biomes": ["minecraft:dark_forest", "minecraft:plains", "minecraft:savanna"]

A list object which contains a list of strings of biomes (both vanilla, and modded) in which this deposit generation should occur.

Leaving this field empty will flag all this deposit dimension's biomes as a valid biome.

This list should contain either a list of biomes, or a signle biome tag.

Used for registry of the ore generation features, and should be a unique identifier for each deposit.

This JSON object houses the deposit configuration, and based on the type of the deposit provided, one of the following modules should be used;

Vanilla Deposit Config module:

Vanilla-like ore distribution with Vanilla Deposit

Determines the material/block that should be used by this deposit for ore generation. The usage of block is beneficial for when you want to generate a specific block in the world, like a custom stone for example. If the field is set to material, then the value should be the id of a material file.

DO NOTE: Using material will only work if the material has ore as a processed type. Otherwise, the field should be set to block and its value should be he Resource Location of a block.

A list object which contains a list of strings of Strata entries. This field takes a list of strata ids as a value.

Determines the generation chance per chunk of the feature.

Determines the generation size of the feature.

Determines the minimum Y level in which this feature can generate.

Determines the maximum Y level in which this feature can generate.

Determines the placement type of this feature.

Options:

uniform is evenly distributed across the height range.

triangle favors the middle of the range.

Determines the general rarity of this feature's occurrence.

Options:

common attempts to generate based on provided chance per chunk.

rare averages once based on the provided chance to generate.

Sphere Deposit Config module:

Sphere Deposit with a Material Ore and an Amethyst Block

A list of objects which contains the material, tag, or block of the feature, and the weight of each object. A Sphere deposit can have an unlimited number of blocks objects.

  • "material" This field takes the material id as a value.

  • "block" This field takes the Resource Location of a block as a value.

  • "tag" This field takes a forge tag string as a value.

  • "weight" This field takes a numerical value which determines how likely this block object is to generate over other block objects in the same feature.

DO NOTE: Using material will only work if the material has ore as a processed type. Otherwise, the field should be set to block and its value should be he Resource Location of a block.

A list object which contains a list of strings of Strata entries. This field takes a list of strata ids as a value.

Determines the chance per chunk of the feature.

Determines the radius of the sphere feature.

Determines the minimum Y level in which this feature can generate.

Determines the maximum Y level in which this feature can generate.

Determines the placement type of this feature.

Options:

uniform is evenly distributed across the height range.

triangle favors the middle of the range.

Determines the general rarity of this feature's occurrence.

Options:

common attempts to generate based on provided chance per chunk.

rare averages once based on the provided chance to generate.

Determines whether this deposit should generate a Surface Sample.

A list of objects which contains the material, tag, or block of the surface sample, the weight of each object, and which strata block to be used for these surface samples.

A Sphere deposit can have an unlimited number of sampleBlocks objects.

  • "material" This field takes the material id as a value.

  • "block" This field takes the Resource Location of a block as a value.

  • "tag" This field takes a forge tag string as a value.

  • "weight" This field takes a numerical value which determines how likely this block object is to generate over other block objects in the same feature.

  • "strata" this fields takes the strata id as a value.

DO NOTE: Using material will only work if the material has ore as a processed type. Otherwise, the field should be set to block and its value should be he Resource Location of a block.

Geode Deposit Config module:

Geode Deposit for Quartz Ore and Clusters

A list of objects which contains the material, tag, or block of the feature, and the weight of each object. A geode deposit can have an unlimited number of blocks objects.

To generate a hollow geode, fillBlocks can be set to "minecraft:air"

  • "material" This field takes the material id as a value.

  • "block" This field takes the Resource Location of a block as a value.

  • "tag" This field takes a forge tag string as a value.

  • "weight" This field takes a numerical value which determines how likely this block object is to generate over other block objects in the same feature.

DO NOTE: Using material will only work if the material has ore as a processed type. Otherwise, the field should be set to block and its value should be he Resource Location of a block.

A list object which contains a list of strings of Strata entries. This field takes a list of strata ids as a value.

A list object which contains a list of strings of clusters.

If the innerBlocks has a budding block, these clusters will generate atop of them similar to the Vanilla Amethyst Geodes.

Example of Clusters

Determines the chance per chunk of the feature.

Determines the crack chance of the geode feature.

Determines the minimum Y level in which this feature can generate.

Determines the maximum Y level in which this feature can generate.

Determines the placement type of this feature.

Options:

uniform is evenly distributed across the height range.

triangle favors the middle of the range.

Determines the general rarity of this feature's occurrence.

Options:

common attempts to generate based on provided chance per chunk.

rare averages once based on the provided chance to generate.

Determines whether this deposit should generate a Surface Sample.

A list of objects which contains the material, tag, or block of the surface sample, the weight of each object, and which strata block to be used for these surface samples.

A Geode deposit can have an unlimited number of sampleBlocks objects.

  • "material" This field takes the material id as a value.

  • "block" This field takes the Resource Location of a block as a value.

  • "tag" This field takes a forge tag string as a value.

  • "weight" This field takes a numerical value which determines how likely this block object is to generate over other block objects in the same feature.

  • "strata" this fields takes the strata id as a value.

DO NOTE: Using material will only work if the material has ore as a processed type. Otherwise, the field should be set to block and its value should be he Resource Location of a block.

Dense Deposit Config module:

Dense Deposit for a single material ore

A list of objects which contains the material, tag, or block of the feature, and the weight of each object. A Dense deposit can have an unlimited number of blocks objects.

  • "material" This field takes the material id as a value.

  • "block" This field takes the Resource Location of a block as a value.

  • "tag" This field takes a forge tag string as a value.

  • "weight" This field takes a numerical value which determines how likely this block object is to generate over other block objects in the same feature.

DO NOTE: Using material will only work if the material has ore as a processed type. Otherwise, the field should be set to block and its value should be he Resource Location of a block.

A list object which contains a list of strings of Strata entries. This field takes a list of strata ids as a value.

Determines the chance per chunk of the feature.

Determines the size of the dense feature.

Determines the minimum Y level in which this feature can generate.

Determines the maximum Y level in which this feature can generate.

Determines the placement type of this feature.

Options:

uniform is evenly distributed across the height range.

triangle favors the middle of the range.

Determines the general rarity of this feature's occurrence.

Options:

common attempts to generate based on provided chance per chunk.

rare averages once based on the provided chance to generate.

Determines whether this deposit should generate a Surface Sample.

A list of objects which contains the material, tag, or block of the surface sample, the weight of each object, and which strata block to be used for these surface samples.

A Dense deposit can have an unlimited number of sampleBlocks objects.

  • "material" This field takes the material id as a value.

  • "block" This field takes the Resource Location of a block as a value.

  • "tag" This field takes a forge tag string as a value.

  • "weight" This field takes a numerical value which determines how likely this block object is to generate over other block objects in the same feature.

  • "strata" this fields takes the strata id as a value.

DO NOTE: Using material will only work if the material has ore as a processed type. Otherwise, the field should be set to block and its value should be he Resource Location of a block.

Dike Deposit Config module:

Dike Deposit are pillar-like of any combination of Materials or Blocks
Dike Deposit example using the min/max for its Diamond ore, where they only spawn between -64 and 16

A list of objects which contains the material, tag, or block of the feature, and the weight of each object. A Dike deposit can have an unlimited number of blocks objects.

  • "material" This field takes the material id as a value.

  • "block" This field takes the Resource Location of a block as a value.

  • "tag" This field takes a forge tag string as a value.

  • "weight" This field takes a numerical value which determines how likely this block object is to generate over other block objects in the same feature.

With Dike Deposits being a tall column of generation, an additional feature was added to this object where you can specify the min and max Y level of a specific material, giving you more Y Level control when mixing multiple materials in a single deposit.

  • "min" This field takes the minimum Y level value of this specific blocks entry.

  • "max" This field takes the maximum Y level value of this specific blocks entry.

DO NOTE: Using material will only work if the material has ore as a processed type. Otherwise, the field should be set to block and its value should be he Resource Location of a block.

A list object which contains a list of strings of Strata entries. This field takes a list of strata ids as a value.

Determines the chance per chunk of the feature.

Determines the size of the dike feature.

Determines the minimum Y level in which this feature can generate.

Determines the maximum Y level in which this feature can generate.

Determines the placement type of this feature.

Options:

uniform is evenly distributed across the height range.

triangle favors the middle of the range.

Determines the general rarity of this feature's occurrence.

Options:

common attempts to generate based on provided chance per chunk.

rare averages once based on the provided chance to generate.

Determines whether this deposit should generate a Surface Sample.

A list of objects which contains the material, tag, or block of the surface sample, the weight of each object, and which strata block to be used for these surface samples.

A Dike deposit can have an unlimited number of sampleBlocks objects.

  • "material" This field takes the material id as a value.

  • "block" This field takes the Resource Location of a block as a value.

  • "tag" This field takes a forge tag string as a value.

  • "weight" This field takes a numerical value which determines how likely this block object is to generate over other block objects in the same feature.

  • "strata" this fields takes the strata id as a value.

DO NOTE: Using material will only work if the material has ore as a processed type. Otherwise, the field should be set to block and its value should be he Resource Location of a block.

Last updated