Tags
Creators
Details
Licensed ARR
Published 2 years ago
Updated 11 months ago
All versions
1.0.3
Release
Lavastone Biome 1.0.311 months ago 19
Uploaded by
Compatibility
Minecraft: Java Edition
1.21.8
Platform
NeoForge
Supported environments
Client and server
Changes
Changelog v1.0.3 - The "Risk & Reward" Update
This update fleshes out the toolset, adds new mechanics, and fixes several bugs regarding tags and drops.
🔥 New Features
- Added the Lavastone Hoe:
- Success (70%): Instantly harvests and cooks crops! (Wheat → Bread, Potato → Baked Potato, etc.).
- Failure (30%): The crop incinerates in a small explosion.
- Added the Lavastone Axe:
- Success (50%): "Superheats" the tree, felling logs instantly and converting them directly into Charcoal.
- Failure (50%): The axe overheats and explodes in your hand.
- Added Advancements System:
- Added a new advancement tab for Lavastone progression.
- Added advancements for obtaining each tool and experiencing their unique "effects."
- New Challenge: "Luck of the Devil" – A hidden challenge awarded only to players unlucky enough to survive a backfire explosion from every single Lavastone tool.
⚖️ Balance Changes & Tweaks
- Lavastone Sword Buff:
- Increased the success rate! Now has a 70% chance to explode the enemy and only a 30% chance to backfire on the user.
- Added Fire/Lava particles to explosions for better visual feedback.
- Lavastone Pickaxe Logic:
- Switched to a Block Tag system (
lavastone:ores_for_pickaxe) for better compatibility. - Standardized the rates to 70% Auto-Smelt / 30% Explosion.
- Switched to a Block Tag system (
🐛 Bug Fixes
- Fixed "Ghost Blocks": Fixed an issue where the Lavastone Pickaxe would smelt the ore but leave a glitched block behind.
- Fixed Explosion Targeting: Fixed a bug with the Sword where the "backfire" explosion would occur on the enemy instead of the player.
- Fixed Tag Detection: Resolved an issue where tools were checking for Item Tags instead of Block Tags, causing abilities to fail.
Enjoy the chaos!
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:B8GQr5yf:m84wl7PZ"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:B8GQr5yf:m84wl7PZ"
}

