1.2.0
Compatibility
Changes
Major Update โ 1.2.0
Arctic's Vein Miner receives its biggest update yet, fixing critical multiplayer issues and adding new configuration options for server owners and modpack developers.
๐ง Bug Fixes
- Multiplayer Pattern Sync โ Pattern selection is now properly synced to the server. Previously the server ignored your selected pattern and used its own, causing mismatched mining behavior.
- Config Loading โ Config values now apply correctly from startup instead of defaulting to off until the config event fired.
- Break Event Safety โ Added null player guard to prevent rare crashes from non-player block breaks.
- Client State Reset โ Pattern state now properly resets on logout, preventing desync on reconnect.
- Double Registration โ Removed duplicate event handler registration that could cause unexpected behavior.
โ๏ธ New Config Options
requireToolโ Optionally enforce correct tool for extra blocks. Default: off.respectHarvestLevelโ Optionally enforce harvest tier requirements. Default: off.enableSoundโ One break sound for the whole cluster instead of per-block. Default: on.showClusterBreakParticlesโ Single particle burst at the start block. Default: off.breakDelayTicksโ Spread vein breaking across ticks to reduce server load spikes. Default: 0 (instant).
โจ Improvements
- HUD Branding โ Mod ID and Version number now displayed in the HUD.
- Rebrand โ Mod ID updated to
avm, cleaner internal structure and asset organization. - Network Protocol v2 โ Updated sync packet to support pattern ID transmission.
๐ง Compatibility
- Minecraft 1.20.1
- Forge 47.4.0+
- Java 17
- Install on both client and server for full multiplayer support.
This update focuses on stability and multiplayer correctness. More features and improvements coming in future updates.
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:DO03xtcE:NAuXxVuF"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:DO03xtcE:NAuXxVuF"
}

