Use custom biomes without datapacks or affecting your map data in Minecraft 1.16.2+
Tested versions:
1.16.5,
1.17.1
Highlights
- Fully supported Minecraft custom biome (worldgen format) (see
Wiki for more information)
- No datapacks are needed!
- Reloadable! No more server restarts to apply your new biomes
- Per-player biome display (based on permissions)
- Fake biome: this plugin does NOT modify your maps, so no worry about corrupting your savedata even if you made mistakes in biomes
- Powerful filters (see below)
All biome transformation happened asynchronously, (i.e. will not block the server thread). Also, biome information stored in 1,024 integers in each chunk, which could be modified within microseconds.
Configuration
The plugin has a single configuration file -
config.json, that controls all the biome transformation needed. See below for more information.
Custom biomes stored in the
biomes folder. Every biome is a separate JSON file, and the file name is the name of biome. For example,
biomes/toxic_ocean.json will create a custom biome named
everbiome:toxic_ocean. See
Wiki for details to create custom biomes.
Biome transformation
This plugin use biome transformations to change what players actually receive & see.
Each transformation contains a
condition that decides which part of the map should be changed, and a destination biome (
to field in config). Positions that satisfy
all conditions will be changed to the
destination biome.
The
destination biome could be any biome you like: a vanilla Minecraft biome, or a custom biome in any datapacks, or the biome you created with EverBiome. (Notice: only custom biomes created by EverBiome could be modified and reloaded without restarting the server)
The
condition supports the following parameters:
-
perm: The permission (or multiple permissions separated by |) needed for showing the current biome. The player will not see this biome if he has none of the permissions.
-
biome: The original biome. (eg. you can change all ocean biomes to a custom toxic ocean biome)
-
dimension: The world name (or multiple worlds separated by |)
-
x: The x-axis coordinate. Use Range format (See below) to select multiple coordinates. Notice: biomes in minecraft have a maximum resolution of 4x4x4, so the coordinate should be divisible by 4.
-
y, z: Similar to
x -
chunkX, chunkZ: The x(or z) axis coordinate of the chunk position. It's faster to use this if you want to change the biome of a whole chunk. Notice the chunk position is the block position divided by 16. Use Range format (See below) to select multiple coordinates.
-
inChunkX, inChunkZ: The x(or z) axis inside the chunk. Both in the range [0,15], (but also need to be divisible by 4). Use Range format (See below) to select multiple coordinates.
The Range format
- Select a single value
Example: select the (100,64,100) block:
Code (Text):
{"x": "100", "y": "64", "z": "100"}
- Select a range:
rangestart~rangeend
Example: select all blocks from x:-100 to x:100
Code (Text):
{"x": "-100~100"}
- Select multiples of a number:
remainder/divisor
Example: select all blocks with x-axis coordinate divisible by 100
Code (Text):
{"x": "0/100"}
Example: select all blocks with x-axis coordinate divide by 100 remains 64
Code (Text):
{"x": "64/100"}
- Select multiples of a number in range:
rangestart~rangeend/divisor
Example: select all blocks with x-axis coordinate divisible by 100 and between 1000~1200 (will select 1000,1100,1200)
Code (Text):
{"x": "1000~1200/100"}
Example: select all blocks with x-axis coordinate divide by 100 remains 64 and between 1000~1200 (Will select 1064, 1164)