4.9.5
Compatibility
Changes
Fixed: Plugin crash on startup when display_name or lore are missing for items in the collective GUI.
⚠️ CONFIG RESTRUCTURE
New options were added to the main config and message files. Automatic expansion of other worlds When the main world expands, other worlds can expand automatically. The list and ratios are set in the config. Number of worlds: Any. You can add several worlds or remove the whole block so nothing expands automatically. Ratio format (1.X): 1.8 — Minecraft formula for the Nether (1:8). Overworld +1000 blocks = Nether +125 blocks. 1.1 — 1:1, the world expands the same as the main world.
Example in config:
automatically_expand_worlds:
world_nether: 1.8 # Nether — Minecraft formula
world_the_end: 1.1 # End — same as main world
To disable: Remove the entire automatically_expand_worlds block so nothing expands automatically. Config structure
The worlds section now supports automatically_expand_worlds and expand_worlds_names (optional display names for messages instead of raw world names like world_nether).
worlds:
world:
gui: "gui.yml"
max_size: 5000
collective_gui: "collective_gui_world.yml"
name: "Survival World"
automatically_expand_worlds:
# Worlds that expand automatically when this world expands.
# Key = exact world name on server (check your world/ folder for folder names).
# Any world works: Nether, End, void, custom, skyblock, etc. Just use its folder name.
#
# Value = expansion ratio in format 1.X (means 1:X).
# The number after the dot is the denominator. Formula: dependent_expansion = source_expansion / X
#
# Examples:
# 1.1 = 1:1 -> multiplier 1.0 -> overworld +1000 = dependent +1000 (same)
# 1.2 = 1:2 -> multiplier 0.5 -> overworld +1000 = dependent +500 (half)
# 1.3 = 1:3 -> multiplier 0.333 -> overworld +1000 = dependent +333
# 1.8 = 1:8 -> multiplier 0.125 -> overworld +1000 = dependent +125 (Minecraft Nether formula)
#
# Values outside 1.0-2.0 range are used as raw multiplier (e.g. 0.5 = half, 2.0 = double).
#
# Don't want automatic expansion? Remove automatically_expand_worlds block entirely. Old configs without it work fine.
# Want only Nether to expand? Remove world_the_end line below. Want only End? Remove world_nether.
world_nether: 1.8 # Nether. 1:8 = overworld +1000 blocks = nether +125 blocks
world_the_end: 1.1 # End. 1:1 = expands same amount as overworld
expand_worlds_names: # display names for automatically_expand_worlds (shown in messages instead of world_nether etc.). Optional.
world_nether: "Nether"
world_the_end: "The End"
The worlds section now supports automatically_expand_worlds and expand_worlds_names (optional display names for messages instead of raw world names like world_nether). Messages The expansion messages in the language files were updated to show boundaries for all expanded worlds (main + automatic). Everything should be clear from the config comments.
Projects on Modrinth are automatically available through a Maven repository for use with JVM build tools such as Gradle. To learn more about the Modrinth Maven API, click here.
Note: When available, you should use the creator's maven repo instead as it will have transitive dependency information that the Modrinth Maven API does not. You may also end up with duplicate dependencies if you use a mix of Modrinth and non-Modrinth Maven repositories for your dependencies, because the group identifier will be different when served through the Modrinth Maven API.
Maven coordinates:
Version ID:
build.gradle:
repositories {
exclusiveContent {
forRepository {
maven {
name = "Modrinth"
url = "https://api.modrinth.com/maven"
}
}
// forRepositories(fg.repository) // Uncomment when using ForgeGradle
filter {
includeGroup "maven.modrinth"
}
}
}
// Standard Gradle dependency
dependencies {
implementation "maven.modrinth:dIYHeADd:qHOQItSk"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:dIYHeADd:qHOQItSk"
}

