Tags
Creators
Details
Licensed MIT
Published last year
Updated 10 months ago
All versions
1.0.1
Release
Dust & Ores - 1.21.8 Forge - 1.0.111 months ago 36
Compatibility
Minecraft: Java Edition
1.21.8
Platform
Forge
Supported environments
Client and server
Changes
Changelog – v1.0.1
Multi‑loader support
- Fully reworked the project to support Fabric, Forge, and NeoForge using a shared common codebase.
Content split into an expansion
- Removed: Raw Diamond and Raw Netherite from this mod.
- Removed: Diamond Dust and Netherite Dust from this mod.
- These items have been moved to a new companion mod: “Dust & Ore: Raw Ore Expansion”.
Tooltip improvements
- Hammer tooltips now show accurate, per‑fortune output ranges for each crushing recipe.
- Raw ores that can be crushed now show contextual tooltips:
- “Hold Shift” hint by default.
- Detailed crushing info (including the resulting dust) when Shift is held.
- Tooltips respect
required_mod, so they only appear when the source mod for a recipe is actually loaded.
New enchantment: Ore Shatter
- Adds Ore Shatter, a hammer enchantment that lets you crush multiple adjacent ores at once instead of just a single block, making ore processing faster and more efficient.
Data‑driven crushing system
- Hammers and crushing recipes are now fully data‑driven via datapacks instead of hardcoded.
- The system supports crushing both items and blocks, giving packs and other mods more control.
Block placement safety
- When the player is holding a Crushing Hammer in the main hand, certain crushable blocks are prevented from being placed, reducing accidental block placement while crushing.
Unbreaking improvements
- The Unbreaking enchantment now correctly reduces hammer durability loss, making it fully functional with Crushing Hammers.
Optional dependencies
Any compatible version
Any compatible version
Any compatible version
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:LSvjwKKG:hqSN35FS"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:LSvjwKKG:hqSN35FS"
}

