Tags
Creators
Details
1.0.7
Compatibility
Changes
-
Added deterministic per-chunk structure placement so spawn decisions remain stable across reloads.
-
Added queued main-thread generation with a configurable structures-per-tick limit.
-
Added optional protection checks for protected areas when a compatible protection plugin is available.
-
Added configurable mob encounters with entity, count, glowing, and difficulty-scaling controls.
-
Added advanced custom loot handling with weighted entries, amount ranges, and enchantments.
-
Added persistent structure metadata, bounding boxes, generated entities, and changed-block awareness.
-
Added safe structure removal that restores only unchanged blocks.
-
Added structure regeneration through the administration command.
-
Added radius-limited locate results and expanded structure management commands.
-
Added configurable performance, protection, encounter, and difficulty settings.
-
Fixed empty biome lists incorrectly disabling sunken shrines and sunken graveyards.
-
Fixed abandoned quarries being filled with stone instead of being excavated.
-
Fixed surface structures being placed one block below the terrain surface.
-
Fixed piglin villages validating one location but generating at another location.
-
Fixed piglin village houses overlapping because only their centers were checked.
-
Fixed desert temple traps failing to activate by placing the pressure plate below the floor without a trigger path.
-
Fixed ruined-house containers being placed below the playable floor.
-
Fixed watchtower containers being placed inside the upper structure instead of on the accessible platform.
-
Fixed custom loot configuration failing on YAML numeric types other than Integer.
-
Fixed invalid custom loot materials and malformed entries from interrupting loot generation.
-
Fixed optional protection integration from requiring the protection plugin to be installed.
-
Fixed queued structure generation waiting for the persistence interval before being processed.
-
Fixed existing entities inside a generation area from being removed as if they were generated encounters.
-
Fixed stale container data being discarded when another world loads.
-
Fixed outdated desert biome names in the default configuration.
-
Fixed command metadata and permissions to include regeneration and safe structure management.
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:f4Vseh0Y:6GZLypCJ"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:f4Vseh0Y:6GZLypCJ"
}

