Topics

1. Video Tutorial

2. Introduction

3. Default in the example

4. Settings

   1. Name *

   2. Land, Sea & Shore Biomes *

   3. Cave, Lake & River Biomes

   4. Biome Zooming

   5. Ridge Biomes

   6. Spot Biomes

   7. Shore Ratio

   8. Rivers

Introduction

Regions are the JSON Equivalent of a Library Subsection, where the books are the biomes, and each biome can tell a story. In normal language; Regions are a way for you to map biomes in your world, and have a system that lets you control all biomes of a certain type (in this region) with a single file.

Default in the example

The region files can be found in the regions folder and usually have a descriptive name. We will be using the region "hot" as found in the example project:

{
    "name": "Hot",
    "landBiomes": [
        "desert"
    ],
    "seaBiomes": [
        "ocean"
    ],
    "shoreBiomes": [
        "beach"
    ],
    "caveBiomes": [
        "mountains"
    ],
    "lakeBiomes": [
        "beach"
    ],
    "riverBiomes": [
        "ocean"
    ],
    "landBiomeZoom": 1,
    "seaBiomeZoom": 1,
    "shoreBiomeZoom": 1,
    "caveBiomeZoom": 1,
    "lakeBiomeZoom": 1,
    "riverBiomeZoom": 1,
    "ridgeBiomes": [
        {
            "biome": "swamp-forest",
            "type": "LAND",
            "chance": 1
        }
    ],
    "spotBiomes": [
        {
            "biome": "oak-forest",
            "type": "LAND",
            "rarity": 1
        }
    ],
    "shoreRatio": 0.01,
    "rivers": true
}

Settings

1 - Name *

"name": "Hot"

The name of the region. It is best to keep / make this the same as the name of the file you are editing.

2 - Land, Sea & Shore Biomes *

"landBiomes": [
    "desert"
],
"seaBiomes": [
    "ocean"
],
"shoreBiomes": [
    "beach"
],

Here you specify the biomes in the world as they connect to eachother. "landBiomes" only connect to "shoreBiomes" and "seaBiomes" only connect to "shoreBiomes" as well. "shoreBiomes" connect land with sea.

3 - Cave, Lake & River Biomes

"caveBiomes": [
    "mountains"
],
"lakeBiomes": [
    "beach"
],
"riverBiomes": [
    "ocean"
],

These biomes are optional and have certain properties:

• "caveBiomes" can only spawn next to "landBiomes",

• "lakeBiomes" can spawn next to "landBiomes" and "shoreBiomes", and

• "riverBiomes" can spawn connected to all other biome types.

4 - Biome Zooming

"landBiomeZoom": 1,
"seaBiomeZoom": 1,
"shoreBiomeZoom": 1,
"caveBiomeZoom": 1,
"lakeBiomeZoom": 1,
"riverBiomeZoom": 1

All of the previous biome types have zooming factors to them. Making this number higher will make the biomes larger.

5 - Ridge Biomes

"ridgeBiomes": [
    {
        "biome": "swamp-forest",
        "type": "LAND",
        "chance": 1
    }
]

Ridge biomes are like real-life mountain chains:

These biomes have a few properties:

"biome": "swamp-forest"

"type": "LAND"

"chance": 1

6 - Spot Biomes

"spotBiomes": [
    {
        "biome": "oak-forest",
        "type": "CAVE",
        "rarity": 1
    }
]

Spot biomes are very similar to the Ridge Biomes, all settings for this are explained there. These biomes can make for very interesting looks in the world, such as this real-life example:

7 - Shore Ratio

"shoreRatio": 0.13

This affects how "deep" the shores (beaches) are compared to the land. Making this 1 will make for very, very deep shores.

8 - Rivers

"rivers": true

Places vanilla rivers in the world if turned to true and not if false.

Mastering

If you cannot find the settings you're looking for here, check out the Template Mastering Page

Topics

1. Video Tutorial

2. Introduction

3. Default in the example

4. Settings

   1. Name *

   2. Version *

   3. Environment *

   4. Regions *

   5. Fluid Height *

   6. Vanilla Ravines, Caves & Structures

   7. Biome & Region Zoom

   8. Focus

   9. Land Chance

   10. Ores

Introduction

Dimensions are json files and they are placed in the dimensions folder. Typically you only have one dimension file in your entire project. The dimension file is the first and highest level file Iris looks at when generating. It describes regions, and other base settings.

This file is the most impactful on your world as it controls every region, and every region controls every biome.

When working on a Biome or Region we recommend that you Focus the biomes that you are working (only 1 at a time), If you are working on the terrain, we recommend that you turn off Decorate as to be able to see it better. As for Regions- they are like the bag holding all the biomes, but you can have as many regions in the dimension file as you want, as long as they are not duplicated.

Default in the example

The dimension file is called example.json and can be found in the dimensions folder:

{
    "name": "Example",
    "version": 1,
    "environment": "NORMAL",
    "regions": [
        "hot",
        "hot"
    ],
    "fluidHeight": 63,
    "ravines": false,
    "vanillaCaves": false,
    "vanillaStructures": false,
    "biomeZoom": 1,
    "regionZoom": 1,
    "focus": "",
    "landChance": 0.625,
    "deposits": [
        {
            "minHeight": 1,
            "maxHeight": 256,
            "minPerChunk": 5,
            "maxPerChunk": 20,
            "minSize": 10,
            "maxSize": 20,
            "varience": 10,
            "palette": [
                {
                    "block": "andesite"
                }
            ]
        }
    ]
}

Settings

1 - Name *

"name": "Example"

Here you can specify the name of the dimension. This should be the same as the name of the file we are currently editing, so example, this file must, in turn, should be called the same as the project we are working in, again example. This can be anything you want (some limitations), but try keeping these three the same.

2 - Version *

"version": 1

This is where you specify the version of the settings. This prevents you from breaking stuff where it's not supposed to. You do not have to change this value, but it may be useful when you are editing and want to keep track of the current version.

3 - Environment *

"environment": "NORMAL"

This affects the type of world you are in and can be any of three: "NORMAL", "NETHER", "THE_END" for the Overworld, Nether and the End, respectively. (Affects the color of the sky and mob spawning defaults etc.)

4 - Regions *

"regions": [
    "hot",
    "hot"
]

Here you specify the regions which you want to have spawning biomes in your world. The names here are and must be the exact same as the names of the files in the regions folder.

5 - Fluid Height *

"fluidHeight": 63

Here you can specify the height of the water level. Ranges between 0 and 255.

6 - Vanilla Ravines, Caves & Structures

"ravines": false,
"vanillaCaves": false,
"vanillaStructures": false

These toggles can turn on true and turn off false vanilla ravines, caves and structures. Note that the ravines and caves do not have the decoration block you may have specified.

7 - Biome & Region Zoom

"biomeZoom": 1,
"regionZoom": 1

This setting zooms your biomes and region respectively. A higher number will give larger biomes & region respectively. Ranges between 0.0001 and 512.

8 - Focus

"focus": ""

This setting will normally not be used in your world, but is very useful when you want to see only one biome in your world. Setting this to any biome will make that the only biome that can spawn. Must be a valid biome.

9 - Land Chance

"landChance": 0.625

Here you can modify the ratio between ocean and land biomes in the world. Ranges from 0 (no land biomes) and 1 (only land biomes).

10 - Ores

"deposits": [
    {
        "minHeight": 1,
        "maxHeight": 256,
        "minPerChunk": 5,
        "maxPerChunk": 20,
        "minSize": 10,
        "maxSize": 20,
        "varience": 10,
        "palette": [
            {
                "block": "andesite"
            }
        ]
    }
]

In the "deposits" setting you can specify the ores you want to spawn in the ground. These ores have a few properties:

"minHeight": 1,
"maxHeight": 256

"minPerChunk": 5,
"maxPerChunk": 20

"minSize": 10,
"maxSize": 20

"varience": 10

"palette": [
    {
        "block": "andesite"
    }
]

"palette": [
    {
        "block": "andesite",
        "weight": 2
    },
    {
        "block": "diorite"
        "weight": 1
    }
]

"palette": [
    {
        "block": "oak_fence",
        "data": {
            "waterlogged": true
        }
    }
]

Mastering

If you cannot find the settings you're looking for here, check out the Dimensions Mastering Page.

Projects

For starters, projects are located in the packs folder (found at */plugins/Iris/packs). Each project contains dimensions, biomes, regions and more. Each project has its own VSCode Workspace.

Creating a new Project

Iris Studio is the system that allows you to easily design your own dimensions, or edit existing ones. To start using studio, first you will need to turn on studio in the settings and restart your server.

To start working with Iris Studio in a new project, we first have to create a new project. Do so with the in-game studio create command. In this command you specify a template, which is the baseline from where we start editing.

Once you run the command for your project, Iris will create a new project test world (called a Studio World) and should open VSCode with your project in it. After the first time, you can use the studio open command instead of the create command to re-open this project world & VSCode workspace. Once finished working on the Dimension, use the studio close command to delete the world and save your workspace progress.

Projects can be very complex or very simple. It's really how far you want to go. Below is a description of top level JSON object syntax and, further down, Iris types. This should be enough to get you set-up for basic editing.

Good luck and have fun :)

Basic JSON syntax

Creating Objects

You can easily create new objects by right clicking the folder of your project in VSCode, and creating the folder type if it doesn't exist. Then right click that new folder and click new file. Name it <name>.json.

Objects start like this:

{

}

Arrays look like this:

[

]

Variables look like this:

"variable": value,
"truthVariable": true

You will see these being used throughout, on top, and inside of one-another throughout the configurations.

Content Assist

Once you have created a new top level type, use CTRL+SPACE in VSCode to show options & documentation about each property in the workspace.

This feature is an absolute life-saver in many cases. Make yourself familiar with it, you will use it a lot.

Types

• Dimensions

• Regions

• Biomes

• Generators

• Objects

• Structures

• Loot

• Entities

Dimensions

Dimensions are json files and they are placed in the dimensions folder. Typically you only have one dimension file in your entire project. The dimension file is the first and highest level file Iris looks at when generating. It describes regions, and other base settings. See Dimensions.

Regions

Regions are json files and they are placed in the regions folder. Regions are comparable to biomes, but they contain groups of biomes, instead of a single one. For example, some regions in the Overworld pack are hot, temperate, or cold. In regions, you define the biomes for each region. See Regions.

Biomes

Biomes are json files and they are placed in the biomes folder. Biomes are what you would expect. They define block types, layers, objects and a lot of other stuff in the world. This is also where you reference noise generators to get your terrain shape. See Biomes.

Generators

Generators are json files and they are placed in the generators folder. Generators are Noise Generators. Noise generators take a coordinate x,z or x,y,z and convert it into a height value. You can explore different base noise styles by using the studio noise command. Generators can take multiple noise styles with additional options and are used to decide the shape of your terrain. See Generators.

Objects

Objects are a special type of file, iob and they are placed in the objects folder. Objects are the block schematics of Iris, comparable to World Edit schematics. You can use the object commands to create them easily. With objects you can also create sub folders inside the objects folder such as objects/trees/tree-1.iob. See Objects.

Structures

Structures are json files and they are placed in the structures folder. Structures reference multiple Objects to create a tiled village/mineshaft/stronghold-like generator. These can also be referenced to by Procedural Structures in the support Discord. You can design one easily by using the structure commands. See Structures.

Loot

Loot are json files and they are placed in the loot folder. Loot tables can be referenced when defining loot in different dimensions, biomes, regions and even structures. They decide which items spawn in the chests they are assigned to. See Loot.

Entities

Entities are json files stored in the entities folder. Entities can be spawned and have customized options for each entity object, such as armor, effects, attributes and more. See Entities.

Support

We offer support on our Discord. Ask questions you cannot answer using the Wiki there. We ask you to look on the Wiki for a solution for your issue before going there. Thank you for using Iris!

• The Volmit Software Team

Iris is a dimension engine

This plugin is not just a block-placer. Iris comes with additional features to make the experience feel special. Examples of these features are custom particles and mob spawns.

Iris comes with several tools designed to allow the manipulation and handling of world generation with ease and power. Additionally, Iris makes full use of the VSCode workspace system, allowing for handy tool-tips and autocomplete in VSCode.

A core philosophy of Iris is flexibility, meaning that Iris is capable of generating any terrain imaginable (within the technical limitations of Minecraft, sadly), while also catering towards those who just want pretty looking terrain without much fuss.

How Iris handles your worlds

For any given world, Iris takes a set of instructions and uses that to shape the world. You are in full control; whether that is determining which block should be placed at any given location, how biomes should be arranged, how structures should spawn, and so on, you decide everything!

Such a set of instructions is called a pack. The Overworld is an example of a pack. Iris world generation is handled on a per-world basis, meaning you can set up any multitude of worlds, each with their own custom pack, or have multiple worlds share the same pack if you so desire.

If a world hasn’t been set up with Iris then don’t worry - only worlds which are set up with Iris will be affected by Iris. We're not destroying your existing worlds.

Specifics of a pack

An Iris pack is a collection of configuration files that define how Iris generates a world. Packs are designed to be highly customizable - allowing you to create and manipulate world generation to your liking - and packs are made easy to understand and have logical structures - allowing for easy yet powerful editing. If the Iris engine was a builder, then packs would be the blueprints that tell Iris what to do.

Packs are stored within the */plugins/iris/packs folder within your server’s files, and can be broken down into several folders, each containing a separate group of configuration files. This includes things like biomes, schematics, terrain generators and more. (We will cover the specifics later on!).

Using templates

If creating a pack is not your thing, Iris has you covered - The Iris team has created the Overworld pack. This, as a de-facto standard, comes bundled with Iris, and contains a set of stunning pre-made biomes, thousands of schematics, and utilises almost all of Iris’ comprehensive features. The Overworld pack, as well as other community curated packs, can be found on the Iris Dimension Collection, hosted on GitHub. You can use the Download Command to download the pack directly. You can then use the template parameter when creating a workspace / project you can edit: e.g. /iris std create myPack template=overworld.

Topics

1. Video Tutorial

2. Introduction

3. Default in the example

4. Settings

   1. Name *

   2. Derivative *

   3. Layers *

   4. Generators *

   5. Objects

   6. Decorators

   7. Slab

   8. Rarity

   9. Debug Color

   10. Loot

Introduction

Biomes are json files and they are placed in the biomes folder. Biomes are what you would expect. They define block types, layers, objects and a lot of other stuff in the world. This is also where you reference noise generators to get your terrain shape.

Default in the example

The template file is called templatefile.json and can be found in the template folder:

{
    "name": "Beach",
    "derivative": "BEACH",
    "layers": [
        {
            "palette": [
                {
                    "block": "sand"
                }
            ]
        },
        {
            "style": {
                "style": "STATIC"
            },
            "palette": [
                {
                    "block": "dirt"
                }
            ],
            "minHeight": 2,
            "maxHeight": 3
        }
    ],
    "generators": [
        {
            "generator": "vanilla",
            "max": 2,
            "min": -4
        }
    ],
    "objects": [
        {
            "place": [
                "tree/junglebush/3"
            ],
            "chance": 0.1
        }
    ],
    "decorators": [
        {
            "chance": 1,
            "palette": [
                {
                    "block": "dead_bush"
                }
            ]
        }
    ],
    "slab": {
        "palette": [
            {
                "block": "sandstone_slab"
            }
        ]
    },
    "rarity": 1,
    "debugColor": "#AAAAAA",
    "loot": {
        "mode": "ADD",
        "multiplier": 0,
        "tables": [tools1]
    }
}

Settings

1 - Name *

"name": "Beach"

The name of the region. It is best to keep / make this the same as the name of the file you are editing. This will only be seen when getting the name of the biome with the what biome command.

2 - Derivative *

"derivative": "BEACH"

The type of biome that Minecraft uses for a number of things:

• The name of the biome as seen in the F3 debug screen.

• The variants of colors in the leaf blocks as made by the client.

• The variants of colors of water in the oceans & rivers (for example swamp water)

• The default type of mobs that spawn in the biome unless overridden

• The environment sound effects that you may hear

This can be any vanilla biome.

3 - Layers *

"layers": [
    {
        "palette": [
            {
                "block": "sand"
            }
        ]
    },
    {
        "palette": [
            {
                "block": "dirt"
            }
        ],
        "style": {
            "style": "STATIC"
        },
        "minHeight": 2,
        "maxHeight": 3
    }
]

Layers dictate the topmost layers of blocks on the surface. They are stacked ontop of eachother. The order in which the block objects are pasted (the part between the outermost { and } ), is the order in which they are placed vertically: The sand in the top of the "layers" array will spawn on top of the dirt, which is at the bottom.

We will now go over the parameters in each of the layer objects (elements in the array):

"palette": [
     {
          "block": "sand"
     }
]

"palette": [
     {
          "block": "sand"
     },
     {
          "block": "sandstone"
     }
]

"style": {
    "style": "STATIC"
}

"minHeight": 2,
"maxHeight": 3

4 - Generators *

"generators": [
    {
        "generator": "vanilla",
        "max": 1,
        "min": -1
    }
]

The generators dictate the way the terrain is generated. You can combine multiple generators in one biome, they will then connect to form terrain you want. This is done by adding a second object to the array like this:

"generators": [
    {
        "generator": "vanilla",
        "max": 1,
        "min": -1
    },
    {
        "generator": "iris",
        "max": 1,
        "min": -1
    }
]

These are the required parameters:

"max": 1,
"min": -1

5 - Objects

"objects": [
    {
        "place": [
            "tree/junglebush/3"
        ],
        "chance": 0.1
    }
],

The objects array contains all objects that can spawn in the world. There are a couple of essential parameters to go over:

"place": [
    "tree/junglebush/3"
]

"chance": 0.1

For more information, see Mastering/Objects

6 - Decorators

"decorators": [
    {
        "chance": 1,
        "palette": [
            {
                "block": "dead_bush"
            }
        ]
    }
],

Decorators are similar to Objects in that they have similar required parameters. The "chance" functions the same and they have some corresponding spawning conditions, but Decorations are blocks, rather than schematics. Using decorators you can have dead bushes spawn around the biome, like in the example.

7 - Slab

"slab": {
    "palette": [
        {
            "block": "sandstone_slab"
        }
    ]
}

Slabs are literal slabs on the terrain that will cause a nice curve. Instead of blocky transitions you can have Iris place half slabs automatically. The required parameter is the "palette" array, which takes a "block".

8 - Rarity

"rarity": 1

The rarity can make certain biomes more rare. The higher the number, the lower the spawnrate (the more "rare"). Ranges from 1 to 512. See this as 100% / value chance of spawning for each location.

9 - Color

"color": "#AAAAAA"

The color is the color that represents this biome when using /iris studio map. It is in hexidecimal format and is not the color of the biome you see in game.

You can use a website with a hexidecamal color picker to get a color.

10 - Loot

"loot": {
    "mode": "ADD",
    "multiplier": 0,
    "tables": [global-tools]
 }

"mode": "ADD"

"multiplier": 0

"tables": [global-tools]

Mastering

If you cannot find the settings you're looking for here, check out the Biomes Mastering Page.

Video tutorial

To be added later

Structure of the Studio Wiki Pages

We will provide two types of tutorials: Understanding and Mastering. As these types suggest, Understanding is for the basic know-how of the files to be able to make quick changes and tweaks, whereasMastering contains all options with a short, more abstract, description of their respective effects to allow full control.

Both Understanding and Mastering have pages. These pages correspond with the types of objects as found in the "Overworld" pack like follows:

• Dimensions

• Regions

• Biomes

• Generators

• Objects

• Structures

• Loot

• Entities

Editing can be fairly simple in one and very complex in another area. We ask you to use the Wiki when you are in search for answers regarding editing Dimensions. If the Wiki is insufficient, unclear, incomplete, outdated, or you would rather talk to someone directly, the support Discord is always open for questions.

In the pages for each of the types you can find a video tutorial at the top if available for that section.

Hopefully these pages are enough to get the hang of the near-infinite possibilities you have with Iris. The sky is the limit (or the build height actually, ha-ha)!

Tips for testing

Sometimes you need to get to a biome you created and you may not be able to find it. Maybe you set it to be a rare biome or something else is causing low spawn rates. You can use the studio GOTO command to find your biome. This command can check 2,000+ locations per second without loading a single chunk.

You can also find out what a block you are looking at is, what an item in your hand is or what biome you are in.

Entities are, well, entities used within Iris. They can be any normal mob in minecraft and even customized.

Entity File

Entities should be located within the entities directory within your pack. Each should be named appropriately

{
    "type": "PANDA",
    "silent": true,
    "surface": "ANIMAL",
    "passengers": [{
        "type": "FOX",
        "customName": "&eUwU",
        "customNameVisible": false
    }]
}

The file above is for a panda that spawns with foxes on its back.

This can be referenced within Iris spawners or initial entity spawns in biomes/regions

• type - The type of mob. Should be from this list

• surface - What kind of surface should this mob be spawned on. See the table bellow:

Spawners

Coming soon. Requires Iris 1.6+

Initial Entity Spawns

In each dimension, region and biome, there is a section called entityInitialSpawns.

"entityInitialSpawns": [
    {
        "entity": "cow",
        "maxSpawns": 1,
        "minSpawns": 1,
        "rarity": 7
    },
    {
        "entity": "pig",
        "maxSpawns": 1,
        "minSpawns": 1,
        "rarity": 7
    },
    {
        "entity": "chicken",
        "maxSpawns": 1,
        "minSpawns": 1,
        "rarity": 7
    },
    {
        "entity": "sheep",
        "maxSpawns": 1,
        "minSpawns": 1,
        "rarity": 7
    },
    {
        "entity": "pandaUwU",
        "maxSpawns": 3,
        "minSpawns": 1,
        "rarity": 50 
    }
],

• entity - This is the name of the entity class to spawn. As you can see, we used the pandaUwU file used in the example above.

• minSpawns - Minimum about of mobs to spawn in the chunk if the chance to spawn passes

• maxSpawns - Same as above, but the max

• rarity - The 1 in <rarity> chance for these mobs to spawn in a chunk

This page will cover all advanced options for Objects within biome or region files. To see how to create an object and use it, see Understanding Objects

This tutorial will make use of multiple examples to provide you with the best understanding of how different parameters can be used in different scenarios.

Recap of the Basics

In case you forget everything you learned, here is what was shown previously:

{
    "chance": 1,
    "density": 2,
    "place": [
        "trees/oak/generic1",
        "trees/oak/generic2",
        "trees/oak/generic3",
        "trees/oak/generic4"
    ]
}

• chance - The chance to place this object in this chunk

• density - How many to place per chunk if the chance is successful.

• place - An array of objects to place

Easy enough, right? Lets get started then!

First Example

{
    "place": [
        "structures/ruins-greek-temple"
    ],
    "chance": 0.0005,
    "mode": "VACUUM",
    "carvingSupport": "SURFACE_ONLY"
    "translate": {
        "y": -4
    },
    "rotation": {
        "enabled": true,
        "yAxis": {
            "interval": 90,
            "min": 0,
            "max": 360,
            "enabled": true
        }
    },
    "edit": [
        {
            "find": [
                {
                    "block": "gold_block"
                }
            ],
            "replace": {
                "palette": [
                    {
                        "block": "chest",
                        "weight": 1
                    },
                    {
                        "block": "dirt",
                        "weight": 5
                    }
                ]
            },
            "chance": 1
        }
    ]
}

This example places a buried greek temple underground and replaces the gold blocks in it (placeholder chest locations) with either dirt or a chest to fill with loot.

Mode

"mode" is used to define how the object is placed.

There are more options to combine with mode bellow at Other Placement Options

Carving Support

Where should this object be placed? Supports SURFACE_ONLY, CARVING_ONLY and ANYWHERE, placing on the surface, in caves or anywhere, respectively.

Translate

Translating an object's position changes where it is placed on the terrain. Making this negative (on the Y-axis) will make the object place in to the terrain and making this positive will place it above the terrain.

You can also translate the X and Z if you really want to.

"translate": {
    "x": 0,
    "y": -10,
    "z": 0,
    "yRandom": 12
}

yRandom allows you to randomize the output of the translated Y value. This value is always positive, so in the example above, the Y will range from -10 all the way to +2

Rotation

Rotation allows you to randomly rotate your object when it's placed. We recommend always allowing rotation on the Y axis with intervals of 90 degrees to let it placed in all 4 directions.

"rotation": {
    "enabled": true,
    "yAxis": {
        "interval": 90,
        "min": 0,
        "max": 360,
        "enabled": true
    }
}

Valid axis are xAxis, yAxis and zAxis. Not specifying an axis will disable it by default

• enabled - Whether to enable rotation. It can also be enabled/disabled within an individual axis as shown above

• interval - Within the minimum and maximum range of degrees, what should the angle always be a multiple of. We recommend keeping this to 90.

• min - The minimum angle to rotate

• max - The maximum angle to rotate

Edit / Replace

The edit section allows you to edit an object's blocks and replace them with others. You can even use styles to change which blocks are chosen to replace.

"edit": [
    {
        "find": [
            {
                "block": "gold_block"
            }
        ],
        "replace": {
            "palette": [
                {
                    "block": "chest",
                    "weight": 1
                },
                {
                    "block": "dirt",
                    "weight": 5
                }
            ],
            "style": {
                "style": "STATIC"
            },
            "zoom": 1
        },
        "chance": 1,
        "exact": false
    }
]

"edit": [
    {
        "chance": 0.3,
        "find": [{
            "block": "cobweb",
        }],
        "replace": {
            "palette": [{
                "block": "void_air",
            }]
        }
    },
    {
        "chance": 0.2,
        "find": [{
            "block": "bookshelf",
        }],
        "replace": {
            "palette": [{
                "block": "oak_planks",
            }]
        }
    },
    {
        "chance": 0.85,
        "find": [{
            "block": "chest",
        }],
        "replace": {
            "palette": [{
                "block": "void_air",
            }]
        }
    },
    {
        "chance": 0.3,
        "find": [{
            "block": "stone_bricks",
        }],
        "replace": {
            "palette": [
                {
                    "block": "mossy_stone_bricks",
                },
                {
                    "block": "cracked_stone_bricks",
                }
            ]
        }
    }
]

• find - A Pallete array of blocks to find to replace

• chance - The chance a block in the find will be replaced.

• exact - If this is true, the find pallete must match the block found EXACTLY (so the block data must be the same and not just the material). Defaults to false.

• replace.pallete - The Pallete array of blocks to replace with.

• replace.style - The style to replace with. If not provided, STATIC is used.

• replace.zoom - How zoomed the style should be. Defaults to 1

Loot

We can define what loot to populate this object with when the object is placed. If we don't provide anything, the containers will just be filled from the loot tables provided by the biome/region/dimension

"loot": [
    {
        "name": "global-treasure",
        "exact": false,
        "filter": [
            {
                "block": "chest"
            }
        ],
        "weight": 1
    },
    {
        "name": "global-clutter",
        "filter": [
            {
                "block": "barrel"
            }
        ]
    },
    {
        "name": "trap",
        "filter": [
            {
                "block": "dispenser"
            }
        ]
    }
]

• name - The name of the loot table to use

• exact - Whether to match the filter pallete exactly (match block data as well as material)

• filter - A pallete array of all the blocks to fill. Blocks MUST be a container of some sort (chests, barrels, dispensers, etc)

• weight - The weight of this entry. If more than one entry are put in the array that have the same filter, higher weights will mean that entry will be picked more.

Scale

Scale allows you to resize an object. It can be scaled up and scaled down and the size can even be randomized. The scaling is done on pack load and the objects are cached, so objects are not scaled when cached, but rather, placed from a cached version of the scaled object.

We suggest you play with scaling using the paste command to figure out what you think looks best.

"scale": {
    "interpolation": "TRILINEAR",
    "maximumScale": 2,
    "minimumScale": 2,
    "variations": 1
}

• interpolation - The interpolation method. Should be either TRILINEAR, TRICUBIC, TRIHERMITE or NONE. If the names seem familiar, it's because they are the same interpolation methods a lot of image editing software use but in 3D (2D is Bilinear and Bicubic).

• minimumScale - The minimum size this object will scale to.

• maximumScale - The maximum size an object will scale to.

• variantions - If the scale range is randomized (from the range decided by the min/max), how many size variations should we cache in memory. Set this to 1 if you're planning on having a single size scaled object

Trees / Saplings

The option that allows you to regrow this object with saplings!

{
    "chance": 1,
    "density": 2,
    "trees": [{
        "sizes": [{
            "depth": 1, 
            "width": 1
        }], 
        "treeTypes": ["TREE"],
        "anyTree": false,
        "anySize": false
    }],
    "rotation": {
        "yAxis": {
            "min": 0,
            "max": 360,
            "interval": 90,
            "enabled": true
        },
        "enabled": true
    },
    "place": [
        "trees/oak/antioch3",
        "trees/oak/antioch4",
        "trees/oak/antioch5",
        "trees/oak/antioch6",
        "trees/oak/antioch7",
        "trees/oak/antioch8",
        "trees/oak/antioch9",
        "trees/oak/antioch10",
        "trees/oak/antioch11",
        "trees/oak/antioch12",
        "trees/oak/antioch13"
    ]
},

As states, adding a trees parameter allows you to regrow objects (like tree objects) with saplings.

The sizes parameter dictates the formation of saplings. You can put multiple sizes in here, but generally ,you want to keep both depth and width the same. Setting these both to 1 would mean it can be grown from a 1x1 sapling. Following the same logic, setting them both to 2 would mean a user needs to put the saplings in a 2x2 formation to grow this object/tree.

The anySize parameter will bypass any sizes specified when set to true, and will allow the object to be grown from any size sapling.

The anyType follows a similar style and when set to true, will allow the sapling to be grown from any type of sapling.

Types

treeTypes specifies what type of saplings can be used to grow the tree. Or more accurately, it dictates what kind of tree it should override when that tree is grown from a sapling (of the correct specified size)

There are some types not includes on this list as while they are tree types, they cannot be grown with saplings. These include SWAMP, TALL_BIRCH, TALL_REDWOOD, JUNGLE_BUSH and COCOA_TREE

Other Placement Options

These are other options to do with the object being placed that may come in handy

Bore

"bore": true,
"boreExtendMaxY": 1,
"boreExtendMinY": 1,
"smartBore": true

• bore - Makes the object place air before it is placed

• boreExtendMinY - Extends the range of the bore

• boreExtendMaxY - The same thing but the max the range of the extend bore can be

• smartBore - Will make Iris try find "pockets" that should be air using raytracing

Water

"onwater": true,
"waterloggable": true

• onwater - Whether to place on the top of the water rather than in the water. Useful for boat objects

• waterloggable - Will make any block that can be waterlogged automatically waterlogged if placed in water

Vacuum Interpolation

"vacuumInterpolationMethod": "BILINEAR_STARCAST_3",
"vacuumInterpolationRadius": 10

• vacuumInterpolationMethod - If using vacuum, what method should the terrain use to interpolate to the flat area.

• vacuumInterpolationRadius - The radius of the interpolation

Bottom / Meld / Overstilt

"bottom": true,
"meld": true,
"overStilt": 1

• bottom - Whether to place this object from the bottom up. Shouldn't be used with rotation.

• meld - Will only place the object in places where blocks already exist. This allows you to spawn dungeons with caves carving into them, but is very performance intensive!

• overStilt - If using stilt mode, this will extend the stilt into the ground by the number of blocks specified (1 would be stilt 1 block past the ground level).

Clamp

"clamp": {
    "minimumHeight": 0,
    "maximumHeight": 255
}

clamp allows you to make sure the object only spawns within the minimum and maximum y levels.

These values are the Y level values that the object should be placed on. So if you have the minimum set to 60 and the maximum set to 65, and have an object 10 blocks high, it will still be placed on terrain 60-65 blocks high.

Iris in general is very user friendly, you just need to understand the basics. If you don't understand the basics, however, you will be in for a frustrating time in this section, and face lots of problems. We strongly suggest that you toy with the example dimension, region, and biome to familiarize yourself with VSCode, have created and built at least one dimension and know - or have at least read - most of the basics in Understanding.

These pages will feel more like Java Docs (if you know what those are).

  ______                 _   _                _    
 /  ____|               | | | |              | |   
 | |  __  ___   ___   __| | | |    _   _  ___| | __
 | | |_ |/ _ \ / _ \ / _  | | |   | | | |/ __| |/ /
 | |__| | (_) | (_) | (_| | | |___| |_| | (__|   < 
  \_____|\___/ \___/ \____| |______\____|\___|_|\_\

Support

We offer support on our Discord. Ask questions you cannot answer using the Wiki there. We ask you to look on the Wiki for a solution for your issue before going there. Thank you for using Iris!

• The Volmit Software Team

All Dimensional Key Value Parameters (Numerical Values)

These are the Boolean values that are toggle able in the dimension file. The ones below may not have their default values, but are just values set for the purpose of explanations.

    "version": 2,
    "biomeZoom": 0,
    "continentZoom": 0,
    "coordFractureDistance": 0,
    "coordFractureZoom": 0,
    "fluidHeight": 0,
    "dimensionAngleDeg": 0,
    "landChance": 0,
    "landZoom": 0,
    "lootTries": 0,
    "regionZoom": 0,
    "rockZoom": 0,
    "terrainZoom": 0,
    "seaZoom": 0,

Version

The Version of this dimension, Changing this will prevent you from accidentally upgrading your file and corrupting the world. The version of the configuration files in the pack.

Fluid Height

The fluid height for this dimension. The vanilla default is 63, this makes the base water level at 63

Dimensional Angle

You can rotate the input coordinates by an angle. This can make terrain appear more natural (less sharp corners and lines). This literally rotates the entire dimension by an angle. Try 12 degrees or something not on a 90 or 45 degree angle. Default Value is 0.0, Maximum allowed is 360.0, Minimum allowed is 0.0

Land Chance

The land chance. Up to 1.0 for total land or 0.0 for total sea This is the land to ocean percentage. The minimum is 0, and max is 1. Our recommendation is 0.625

Loot Tries

Try to fill a container with loot up to this many times to avoid too many empty chests. Defaulted at 5, the amount of times that a global loot table will be tried to place an item inside of a chest, increasing this will fill a chest with things, reducing it will empty. no lower than zero, no higher than 512* (you can go higher but why)

Coordinate Fracture Distance/Zoom

Coordinate Zoom: Higher = less frequent warping, Lower = more frequent and rapid warping / swirls. Coordinate Fracture Distance: Applies noise to the input coordinates. This creates the 'iris swirls' and wavy features. The distance pushes these waves further into places they shouldn't be. This is a block value multiplier.

Zooming

This zooms in the elements by a multiplier: Imagine using a crumpled ball of paper, then zooming into it. that's what this does.

****

Non-Numerical Dimensional Key Values (yeesh)

    "resourcePack": "",
    "environment": "NORMAL",
    "focus": "",
    "name": "Hello Iris",

Environment

The world Environment. This is fairly straightforward, only 3 possible options NORMAL, NETHER, and THE_END.

Focus mode (Helpful)

Keep this undefined or empty, setting this to a value will force the overworld to only generate that biome. Great for testing, Must be a valid biome. Focus mode allows you to have a specific biome be the only biome that shows up when you are making your biome. This was used in almost every step of developing the Overworld pack, and others. Below you would only see a desert

"focus": "hot-desert",

Name

The human readable name of this dimension Name of Dimension. no real explanation needed

All Dimensional Boolean Parameters (Boolean Values)

These are the Boolean values that are toggle able in the dimension file. The ones below may not have their default values, but are just values set for the purpose of explanations.

    "carving": false,
    "caves": false,
    "decorate": true,
    "debugSmartBore": false,
    "placeObjects": true,
    "postProcessing": true,
    "postProcessCaves": false,
    "postProcessingSlabs": false,
    "postProcessingWalls": false,
    "preventLeafDecay": false,
    "vanillaCaves": false,
    "vanillaStructures": false,

Carving

Carve Terrain or not Carving is a 3D Noise layer that will just CUT through mountains and terrain, making some neat cliffs in mountain regions. This has a reasonable performance hit, but is on by default- well worth it in out opinion.

Caves

Generate Caves or not. Literally just a true or false as to allow iris generate IRIS caves not to be confused with Vanilla Caves

Decorate

Generate Decorations or not. Literally just a true or false as to allow iris generate predefined decorators in each biome. Example: if you have a biome decorator that says to generate flowers, toggling this in the dimension will toggle it everywhere

Debug Smart Bore

Instead of filling objects with air, fill with cobweb so you can see This is to help show you where iris thinks blocks are, and are not. It places cobwebs in the air blocks to show you where the Structure module thinks it should Cut blocks and stuff out, without overwriting the other surroundings.

Place Objects

Disable this to stop placing objects in biomes This is the 'hand that gives, or the hand that takes away' in regards to objects. It prevents the placement of all iris schematics in biomes.

Post Processing

Use Post Processing or not. Post processing is the unessential, finishing touches that iris does to make the world more pretty, at the cost of a sleight performance hit. It is fine to leave this on. If you turn it off, you may not see the Slabber , Pot-Hole-Filler, Nipple-Remover, Stacker-Fixer working, this is because you just turned them off.

Post Process Caves

Use post processing in caves or not Post processing is the unessential, finishing touches that iris does to make the world more pretty, at the cost of a sleight performance hit. It is fine to leave this on. If you turn it off, you may not see the Slabber , Pot-Hole-Filler, Nipple-Remover, Stacker-Fixer working, this is because you just turned them off. See post processing for an explanation.

Post Processing Slabs/Walls

Add Slabs or walls to the post processor instead. Post processing is the unessential, finishing touches that iris does to make the world more pretty, at the cost of a sleight performance hit. It is fine to leave this on. If you turn it off, you may not see the Slabber , Pot-Hole-Filler, Nipple-Remover, Stacker-Fixer working, this is because you just turned them off. See post processing for an explanation.

Prevent Leaf Decay

Prevent Leaf Decay Whenever iris places a schematic, or anything leaf related- especially with big trees. We use this in iris Overworld Dimension for the trees we place.

Vanilla Caves

Generate Vanilla caves and Cave things Working vanilla caves that can intersect with iris caves. this creates some gnarly looking caves and ravines.

Vanilla Structures

Generate Vanilla Structures Currently not working in the way that you might intend, this for now is default to false because it cause instability, gen failure, and other sorts of issues. We plan to just make out own villages in the future.

Topics

1. Video Tutorial

2. Introduction

3. Default in the example

4. Settings

   1. Interpolator *

   2. Seed *

   3. Composite *

   4. Setting

   5. Setting

   6. Setting

   7. Setting

   8. Setting

   9. Setting

Introduction

Generators are json files and they are placed in the generators folder. Generators are Noise Generators. Noise generators take a coordinate x,z or x,y,z and convert it into a height value. You can explore different base noise styles by using the studio noise command. Generators can take multiple noise styles with additional options and are used to decide the shape of your terrain.

Default in the example

The Generator file is called generator.json and can be found in the generators folder:

{
    "interpolator": {
        "function": "BILINEAR_STARCAST_9",
        "horizontalScale": 41
    },
    "seed": 12345,
    "composite": [
        {
            "style": {
                "style": "IRIS",
                "zoom": 0.87,
                "fracture": {
                    "style": "IRIS_HALF",
                    "zoom": 0.295,
                    "multiplier": 18
                },
                "exponent": 1.125
            },
            "seed": 54321,
            "bezier": true,
            "exponent": 1.125
        }
    ]
}

Settings

1 - Interpolator *

"interpolator": {
    "function": "BILINEAR_STARCAST_9",
    "horizontalScale": 41
}

The interpolator describes the way Iris connects this biome to another. It is the way this biome is placed inside the other biome. Below is a screenshot of an example of a more radical version where, as you can see, the mountain biome is being placed into the beach / desert biome.

The interpolator uses two settings which must both be specified:

"function": "BILINEAR_STARCAST_9"

"horizontalScale": 41

2 - Seed *

"seed": 12345

The seed is a number you can pick which randomises the algorithms behind the functions. Changing this value may lead to completely different outcomes, but never predictably so.

3 - Composite *

"composite": [
    {
        "style": {
            "style": "IRIS",
            "zoom": 0.87,
            "fracture": {
                "style": "IRIS_HALF",
                "zoom": 0.295,
                "multiplier": 18
            },
            "exponent": 1.125
        },
        "seed": 54321,
        "bezier": true,
        "exponent": 1.125
    }
]

The composite is the main generator of the biome this generator is used for. We again see seed, which functions similarly to the previously explained Seed and will not be handled here again.

This function can completely change the way your terrain looks, from very spiky to smooth. Note that this does not affect the height of the terrain, this is done in the Biome under Generator.

Style

The style is the actual noise configuration for this generator. This has the greatest influence on the terrain.

"style": {
    "style": "IRIS",
    "zoom": 0.87,
    "fracture": {
        "style": "IRIS_HALF",
        "zoom": 0.295,
        "multiplier": 18
    },
    "exponent": 1.125
}

"style": "IRIS"

"zoom": 0.87

"fracture": {
    "style": "IRIS_HALF",
    "zoom": 0.295,
    "multiplier": 18
}

"exponent": 1.125

Other

"bezier": true

"exponent": 1.125

4 - Setting

"Setting": value

Explanation

5 - Setting

"Setting": value

Explanation

6 - Setting

"Setting": value

Explanation

7 - Setting

"Setting": value

Explanation

8 - Setting

"Setting": value

Explanation

9 - Setting

"Setting": value

Explanation

Mastering

If you cannot find the settings you're looking for here, check out the Template Mastering Page

General information

Objects are Iris' schematics. They are used to place objects in the world.

They cannot be directly modified, so this will be a short guide on how objects can be:

• Created,

• Edited,

• Added to the world, and

• Imported from EWG

Create a new object

You can create a new object by building one in game and then saving it. The object can be any size under 512 x 256 x 512. Note that sizes that large will be heavy on the server to place.

After building the object, you can select it using the wand (get a wand using the wand command) and then save it using the save command. You can modify your selection with the other commands in the object command section.

We recommend checking out the video above to see what they do precisely.

Editing an object

You cannot directly edit an object from a file, but you can edit it in-game. You can do so by using the paste command, editing the structure and then using the same set of steps as with Create a new object above.

Adding an object to the world

Within every dimension, region and biome, there is an array of objects that can be spawned. It will often look something like this:

"objects": [{
    "chance": 1,
    "density": 2,
    "place": [
        "trees/oak/generic1",
        "trees/oak/generic2",
        "trees/oak/generic3",
        "trees/oak/generic4"
    ]
}]

• chance - The chance to place this object in a chunk. Max is 1

• density - How many to place per chunk if the chance to place in this chunk is successful.

• place - An array of objects to place. If multiple are specified, a random one is chosen.

You can add as many objects to this section as you like. Biomes often have lots and lots of different objects to spawn, all with different chances and densities.

If you want more information on editing objects, check out the Mastering Objects section below

Import and object from EWG

You can import objects from Epic World Generator by putting .EWG schematic files in the */plugins/Iris/convert folder and using the convert command.

Post Processing

Use Post Processing or not. Post processing is the unessential, finishing touches that iris does to make the world more pretty, at the cost of a sleight performance hit. It is fine to leave this on. If you turn it off, you may not see the Slabber , Pot-Hole-Filler, Nipple-Remover, Stacker-Fixer working, this is because you just turned them off. (More on Post Processing )

Environment

The world Environment. This is fairly straightforward, only 3 possible options NORMAL, NETHER, and THE_END.

Regions (Essential)

Define all regions to include in this dimension. This is essential for any dimension file. The listings in here are required for you to see any kind of impact or biomes generate.

IF YOU WANT ANYTHING TO GENERATE YOU NEED TO HAVE BIOMES IN REGIONS, AND REGIONS IN THE DIMENSION FOLDER!

Caves

Generate Caves or not. Literally just a true or false as to allow iris generate IRIS caves not to be confused with Vanilla Caves

Focus mode (Helpful)

Keep this undefined or empty, setting this to a value will force the overworld to only generate that biome. Great for testing, Must be a valid biome. Focus mode allows you to have a specific biome be the only biome that shows up when you are making your biome. This was used in almost every step of developing the Overworld pack, and others. Below you would only see a desert

"focus": "hot-desert",

Name

The human readable name of this dimension Name of Dimension. no real explanation needed

Carving

Carve Terrain or not Carving is a 3D Noise layer that will just CUT through mountains and terrain, making some neat cliffs in mountain regions. This has a reasonable performance hit, but is on by default- well worth it in out opinion.

Version

The Version of this dimension, Changing this will prevent you from accidentally upgrading your file and corrupting the world. The version of the configuration files in the pack.

Post Overview

We highly recommend that you familiarize yourself, and toy around with them before diving straight into the heavy lifting- that is, dimensional manipulation. (that sounds funny) But in all seriousness the Dimensional file is likely the hardest of the files to learn, as all are relatively self explanatory in most other circumstances.

Tutorial Video

Astrash's written tutorial

This is a tutorial based on Astrash written tutorial in discord.

Jigsaw pieces are basically objects with jigsaw connectors plus some other stuff. A jigsaw piece is just a config file, with an object attached to it - multiple pieces could share the same object (if that's what you want to do)

Pieces can be created with /iris jigsaw create <name> <pack> <object>, this is where you place your connectors. When you use that command, a copy of that specified object will spawn in the world, with that copy, right click block faces to add connectors, and shift right click to remove.

Once finished you can use /iris jigsaw save to save that jigsaw piece, and a config file will be automatically generated with your connectors.

Connectors are stored as json objects, and have some key properties. For now the only important parts you have to worry about are "pools", "position" and "direction".

INSERT CODE EXAMPLE HERE

Once you create a piece, there will be a folder called jigsaw-pieces in your pack folder, which will be automatically set up with the essentials for a piece, the only thing you really need to change is the "pools" option, which is where you tell Iris what you want that connector to attach to

Now try creating a test object the way any object would be made, maybe something like square like so

Just for the sake of learning, try make 3 pieces like so

The next step after you have your pieces is to create a Jigsaw structure, here is an example of the stronghold structure. Ensure you make a folder called jigsaw-structures and create a new json file titled after your structure. This could be called anything you want. Copy the config here and fill out the piece with the one you have already made

The piece you put in the structure is essentially your starting piece, where the jigsaw system will expand outwards from. You should only have one jigsaw structure file per structure (note you could also provide several starting pieces). Once this is made, try out /iris jigsaw place <name of jigsaw structure file> - if you did everything correctly, you should have a single piece spawn in the world.

The next step is defining a Jigsaw pool. A jigsaw pool is basically a group of jigsaw pieces, defined in a file.

First of all, create a folder called jigsaw-pools, then similary to the structure setup, make a json file named whatever you'd like (for example i use path for my group of path pieces in the stronghold)

Within that file you just created, simply list out pieces you've created like so

Continuing on with pools, when Iris picks a connector to continue the structure, it will take a look at that connector's configured "pools" option, and see what pieces it can place next. So in order for a connector to place stuff, you will need to define pools (as outlined above) to that list for each connector

As an example, when iris looks at this connector, it will look at "pools", see the "stronghold/paths" pool, and pick a jigsaw piece from that list to connect to. Once it picks a piece from that list of pools, it will check 1. if it has a valid connector, and 2. if that piece will collide with any other piece. If check #2 fails, then Iris will try place another piece from the pool. If none of those pieces can be placed, then Iris will simply not place anything at the connector.

Also another thing to note - if a piece is set up with a connector inside its bounding box, then you will most likely need to set innerConnector to true, since it will check for collision with its self in addition to other pieces

Here is an example of multiple pools, note that:

• the green pool also has a piece in it that connects to a purple pool

• the purple L pieces are free to rotate on all axes ("rotateConnector": true) whereas all other pieces only rotate on the Y axis

If you have any further questions or get stuck and want to get some help, please ask on Discord.

The information below is a variant of the Biome tutorial, and we would recommend that you familiarize yourself with that first. this would then make more sense especially the complexity will become less complex.

Parameters:

• Name - What is the biome called in-game, filename refers only to what internal schema know

• Layer - What blocks makeup the biome floor, and sub-terrain (not including caves)

• Objects - This lists the 'things' that you want to place all over the place eg: trees, rocks, etc...

• Generators - The way the terrain Height-map is designed

• Derivative - This sets the Vanilla Color, Mob spawn, Weather, and some other event

Many of these here will give you a world that 'looks' like a normal world, but Iris is able to give you so much customization that you can have many types of variants that can look otherworldly.

These are some examples of other uses of the defaults:

Recap:

Much of what you have seen above, IS used in the example projects, when it comes to what a final project biome looks like, they would look like something like this

Post Overview

What's Covered Here:

• Style

• Blocks

• Drops

• Deposits

• Loot

• Palette

• Slope

• Generator

• Objects (too many options!)

• Text

• Rarity

• Regions

Style/Generator Breakdown

Style/Generator Explained:

Style/Generator is the 4-D (that's one more D than 3D) rules that draw the carve layer. Static is a commonly used style, with any multiplier, or zoom- it is easy noise. IRIS, is our home-brewed Style that we use in places all over the Overworld

Blocks Breakdown

Blocks Explained:

Style is the 4-D (that's one more D than 3D) rules that draw the carve layer. Static is a commonly used style, with any multiplier, or zoom- it is easy noise. IRIS, is our home-brewed Style that we use in places all over the Overworld

Drops Breakdown

Drops Explained:

Drops are the items that are dropped when broken, or are tossed into chests as loot. If you were linked here, that means the things here are referenced in whatever module you are looking into

Deposits Breakdown

Deposits Explained:

Deposits are the ores, or clumps of stuff that is spawned in the ground. like Dirt patches, or Ores. This is a great way to set ores, This also supports custom blocks- Using the palette you can have whatever spawn, from custom blocks to doors can be deposits. This can be set in the Dimension, Region, and Biome.

Palette Breakdown

Palette Explained:

The palette is the set of blocks that are included in the parent function's list of parameters. you can have as many as you want as long as everything is properly labeled.

Fluid Breakdown

Fluid Explained:

Fluid layers are a simple way to set a sort of water-layer or anything-layer in the parent. upi can put blocks here, but its built for fluids.

Slope Breakdown

Slope Explained:

Slope is the generator that determines the direction/form of the parent function.

Loot Breakdown

Loot Explained:

Slope is the generator that determines the direction/form of the parent function.

Objects Breakdown

Objects Explained:

Objects have loads of edits, and things you can do with them. (Psycho caused this) but this is one of the biggest, if not the biggest set of information and toggles that you can do.

Text

Rarity