Tags
Creators
Details
2.2.0
Compatibility
Required content
Changes
Update: (v2.2.0, +2106 / -670) Layered Mine (replacing the old quality mechanism) Removed the common/rare/epic/legendary random generation mechanism (block.yml, MineralRarity) Added layers.yml: the mine goes from top to bottom as stone zone → calcite zone → granite zone → deepslate zone → netherrack zone → basalt zone → blackstone zone → end stone zone, with 1 layer of bedrock at the very bottom Each layer consists of base blocks (default 95%) + ores (default 5%), refreshed with vanilla-style probabilities (coal/iron/copper/emerald, amethyst, deepslate ores, raw ore blocks, nether gold/quartz/glowstone, ancient debris, bone blocks, gilded blackstone, various mineral blocks, etc.) Inheritance mechanism: minerals from the upper layer decay and are inherited layer by layer into the lower layer, and all values can be externally configured Mine caves and chests Caves are generated by random walks inside the mine (count/length/radius/chest probability are all adjustable) Chest loot (loot.yml): experience bottles (EXPERIENCE_BOTTLE + NBT, fixed experience 500/2500/10000), level-up balls (SNOWBALL + NBT, increase by 1/3/5 levels), NBT with the same name can stack, can be stored long-term, right-click to use Fixed chest placement logic (search downward for the cave floor) and item writing method (switched to real-time block entity inventory) Refresh mechanism Removed timed refresh: scans air ratio every 10 seconds, automatically performs a full refresh at ≥95% (executed in batches to avoid lagging the server) Added a generation version mechanism: after upgrading the plugin, old mines are automatically rebuilt, with no need to manually delete the world /goldminer reload reloads and refreshes all layers; /goldminer reload <layer> refreshes a single layer and supports Tab completion; pool/info remain compatible Broadcasts prompts to players inside the mine when refresh starts/completes (customizable in lang.yml) Compatibility Zero changes to the database structure, fully compatible with old player data
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:M2y0QIWW:mxir3rCC"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:M2y0QIWW:mxir3rCC"
}
