All versions
1.2.0
Release
Better Veinminer 1.2.07 months ago 34
Compatibility
Minecraft: Java Edition
1.21.x
Platforms
Bukkit
Paper
Purpur
Spigot
Changes
[1.2.0] — 2026-03-14
Added
- Tier System — Players automatically progress through 4 tiers as they mine more blocks:
- Tier 1: 32 max blocks (0 blocks mined)
- Tier 2: 64 max blocks (100k blocks mined)
- Tier 3: 128 max blocks (500k blocks mined)
- Tier 4: 256 max blocks (1M blocks mined)
- Player Statistics — Track blocks mined, veinmines used, and current tier
- New Commands:
/bvm statsand/bvm tierfor player progression tracking - Ore Multipliers — Configure different drop multipliers for different ore types (e.g., diamonds worth 1.5x)
- Per-Ore Cooldowns — Optional: Set different cooldown times per ore type
- Permission-based Limits — VIP (
betterveinminer.vip) and Premium (betterveinminer.premium) tiers - Daily Limits — Optional: Prevent abuse by limiting veinmines per player per day
- Advanced Effect Settings — Customizable particle types, colors, speeds, and sounds
- Custom Messages — Fully customizable player notifications with placeholders
- EXP Rewards — Optional custom experience points for veinmining
- PlayerStats.java — New data class for tracking individual player progress
Changed
- Version bumped to 1.2.0 with major feature expansion
- pom.xml — Fixed XML syntax errors (typo:
<n>→<n>) - PluginConfig.java — Expanded from ~90 lines to ~300+ lines with comprehensive settings
- BetterVeinminer.java — Refactored to support tier system, stats, permissions, and daily limits
- config.yml — Completely rewritten with organized sections for each feature
- plugin.yml — Added 3 new commands and 2 new permission levels
Improved
- Much better tier progression system that rewards dedicated miners
- More granular permission-based control for VIP/Premium players
- Enhanced logging and player feedback with customizable messages
- Better code organization with dedicated helper methods
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:3Njs3FsV:dmAXvtsK"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:3Njs3FsV:dmAXvtsK"
}

