Frequently Asked Questions

All iris questions that we can think of will be put here

There is a table of contents on the right.

When to update Iris

Updating Iris is not like any other plugin. To draw a comparison between Iris and Minecraft - When you update your server's Minecraft version, it will result in any new chunk that is generated to not be aligned with existing chunks, in every vanilla world.

Iris generates worlds for you as well, and it has the same problem. The difference is that Iris updates a lot, and Minecraft barely, which makes users think it is safe to update, when in reality, it may do more harm than good.

A quote from our lead developer:

Generally, it's not possible to do something like that without ending up with hard borders / having to edit millions of chunks possibly. By changing the biome map, everything changes. Things that were a desert are now a forest. I could blend it by using an interpolator, but... ignoring the intense CPU [required for] that, it would still look terrible, because it would still look like a wall, just smoother, and the biomes would still be cut-off. Just update when you're ready to make a new map, it's not a big issue 😛

So, when should you update Iris?

You should only update Iris when you are ready to delete or recreate all Iris worlds. If you are thinking about updating Iris in any other case, contact support to discuss it first.

Make a backup before proceeding. Thank yourself later.

You can now update the Iris plugin. If you are sure you want to update Iris, make sure to also update the Overworld pack on your server.

How to update Your Pack

Updating should only be done when needed, or when you are ready to update the content from the latest release. This goes for both the Plugin as the Overworld pack.

Read When to update Iris first.

For new worlds

/iris download <packName> overwrite=true

This command does not update the current Overworld that is in any active Iris world, but only the one in the */plugins/Iris/packs folder. Thus, it only applies to new worlds. This is also why you need to make sure you are ready to delete all existing Iris worlds and create new ones.

Updating loaded worlds can cause terrible transitions between old and new chunks, among other issues, which is why the option below is advised against.

Generated Worlds

NOT RECOMMENDED - Use at your own risk. Know what you are doing. This can and likely will cause issues in your world! You must back-up before doing this. We will not provide support if you did not.

/iris update-world

Uninstalling Iris

There are many things Iris controls which will break when you uninstall the plugin. A lot of these features may cause issues in survival servers, so we strongly recommend keeping Iris installed.

Features that are likely to break:

New chunks will not be custom: New chunks will be normal vanilla chunks which do not align properly with existing chunks. Removing these manually can be difficult if you wish to amend it.
Custom height modifications: Iris is responsible for setting the max height to something different than vanilla. If you remove Iris, this will not be ensured with every world, and you may end up with mountains cut-off at the new - wrong - build limit.
World Shifting: A less probable bug, but one that can still seriously mess up your worlds is that certain parts of the world may be shifted up 64 blocks. This allows people to get below the bedrock, breaks the terrain and can even cut player-built buildings in half.
Custom leaf decay systems: Iris spawns custom trees which have leaves which are too far away from logs without them decaying. Iris controls leaf decay systems and uninstalling the plugin may result in leaves being removed where they shouldn't.
Strongholds cannot be found with eyes of ender: Iris allows you to directly control how many strongholds can spawn and how far apart they are. Because we don't follow the same method as vanilla, eyes of ender require Iris to be installed to lead to the correct locations. If you uninstall Iris, eyes of ender will lead to locations where there is nothing (where vanilla would place one)
No mob and animal spawns: Iris does not spawn mobs when it generates chunks, but instead has its own spawning system to evenly distribute mobs/animals over the entire server. These mobs will no longer spawn. Mobs that spawn in structures like silverfish and guardians will no longer spawn.
Custom particle & sound effects will disappear: There are custom particles & sound effects which will no longer be (dis)played and replaced by (boring) vanilla defaults. Iris uses these to add biome immersion, and all of this would be removed.

If you decide to uninstall Iris because of issues with server performance (Iris seems to be causing lag), please contact support first, so we can search for a solution. We would then love to see a timings report, /timings report.

How to change the seed in Iris

Iris worlds, as opposed to normal vanilla worlds, generates new worlds with the same seed every time. To change this seed, you have to add it to the server.properties file, which you find in your main server directory (*/server.properties). Just locate the level-seed= setting and add any number behind it, at random. Every time you change this, and generate a new Iris world, you will have new random generation.

Out of bounds error

To fix it, let the server restart when you see Iris warning about biomes in the console. We ask you to restart in the error at the bottom, so please do so. Want to know why? See Why does Iris restart the server?

Manually downloading the Overworld

Stop the server
Remove */plugins/iris/packs/overworld (the folder), if it exists
Download the pack from our Github manually.
Place it in the same folder as before, */plugins/iris/packs/overworld
Unzip the folder
Rename the resulting folder to overworld
Follow the getting started tutorial as normal

Restart after downloading a pack

Since Iris uses datapacks for a lot of its biomes (for colors, sounds, etc.), we generate a datapack for each pack that is installed. Since datapacks need to already be installed upon server startup, while Iris is not ready by that time on the first install, Iris needs to reload the server. This is only needed once.

Iris uses Datapacks to make amazingly colored biomes such as the Sakura biome:

Which permission nodes does Iris offer?

The only permissions are iris.all & iris.studio and probably only YOU (the server owner) should have them.

Red logo on startup (Mac only)

Set in the settings.json Configuration -> General -> useConsoleCustomColors to false

Biomes larger / smaller

In this diagram, you see what settings affect biome sizes. To make biomes larger, you can increase the zoom on the region's specific biomes here, which will make the collection of biomes that are in a category larger. You can also change all biome & region sizes to be larger, this setting is found here.

Change object spawn chance

To reduce the number of times an object spawns in a single area, follow the following steps:

1. Find the name of the object by getting an Object Dust with /iris object dust and clicking the object. Remember this name, we need it in step 4.

2. Find the name of the biome by running /iris find

3. Open the configuration file for the biome by locating it in the */plugins/iris/packs/overworld/biomes folder. Each of the folders in there is for one region. The name of the region is included in the name of the biome. Open the biome file. (If you are in a studio world, you can use /iris studio editbiome to directly open the file)

4. Find the "objects" section, which looks similar to the following (more or fewer settings may be present)

"objects": [
    {
        "place": [
            "folder/subfolder/1",
            "folder/subfolder/2",
            "folder/subfolder/3"
        ],
        "chance": 0.1,
        "density": 2,
        "mode": "MIN_HEIGHT"
    }
]

In here, there are 2 options to take into account, chance and density.

Chance dictates the fractional chance of an object spawning per chunk, if it is 0.1, it has a 1 in 10 or 10% chance of spawning. You can decrease this number to decrease the number of times it spawns.

Density dictates the number of times the object spawns if the chance roll was successful. So, for example, if the 10% chance of the example is successful, there are going to be 2 objects of the objects included in the place list, in that chunk. You can decrease this number to see less clusters of objects spawning.

Another option is to remove one or more of the objects from the list under place, this will remove that object from the biome entirely. Note: Do not remove all objects from the list. Instead, set the chance to 0.

Disable Iris' Spawn System

You can disable the Iris spawn system in the config *\plugins\iris\settings.json and look for "ambientEntitySpawningSystem": true, and "markerEntitySpawningSystem": true, and set those to false

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

PreviousMMOItems Next常见问题

Last updated 9 months ago