Tags
Creators
Details
1.1.0
Compatibility
Changes
Vein mining for ores: break one block and the connected vein follows, with durability and enchantments handled the way vanilla would.
This release is also the first open source one: https://github.com/LucasTHCR/CaveMiner
Fixed
- Vein mining ignored every protection and logging plugin. Chained blocks were removed without a block break event, so WorldGuard, claim plugins and block loggers never saw them - a vein could be pulled straight through someone else's claim. Every block now fires its own event, and a block another plugin vetoes is skipped while the rest of the vein continues.
- Fortune had no effect. The bonus was read from the block after it had already been set to air, so it never matched. Drops now come from the block's loot table, which applies Fortune and Silk Touch exactly as vanilla does.
- Chained blocks dropped no experience at all. Coal, diamond, emerald, lapis, redstone and quartz gave experience for the one block broken by hand and nothing for the rest of the vein.
- Break particles never appeared - the option was read nowhere.
particles.enablednow exists in config.yml. - Bare hands ended the chain after the first block, although an empty tool list is documented as "any tool, or fist".
- The block that breaks the tool is mined instead of being lost.
- Statistics survive a restart and no longer overcount veins that stopped early.
Added
caveminer.use(default true) andcaveminer.reload(op) - there was no permission at all before/caveminer reloadand/caveminer stats, alias/cmmerge-deepslate-variantsso an ore pocket on the deepslate border stays one veinsound.nameaccepts bothBLOCK_STONE_BREAKandblock.stone.break
Changed
- The listener runs on
HIGHEST, after protection plugins have had their say. OnHIGHa plugin cancelling later came too late. - The vein search skips unloaded chunks instead of generating terrain on the main thread.
stats.ymlkeeps only online players in memory.
Requires Java 21. PlaceholderAPI is optional.
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:cxTKgGaj:ojnEMWSE"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:cxTKgGaj:ojnEMWSE"
}

