Tags
Creators
Details
4.0
Compatibility
Required content
Changes
This update now brings you the Detominer pack now in its mod form, allowing for an even deeper environment control and higher creativity!
Features include:
- Full customization of what blocks you can detonate through the use of a dynamic auto-reloading config file
- Customizable block radius detonation from enchantment levels Detonate I up to Detonate III
- Third-party mods support with just a toggle in the config file, allowing for detonation on custom blocks
- Experience orbs now normally drop when mining certain ores
- Detomining can now break your tools when trying to mine blocks that are more than your tool's durability
- Using Detonate-enchanted tools now work in Creative mode
- The Detonate enchantment is now enabled for these 5 tools: Pickaxes, Axes, Shovels, Hoes, and Shears. However, only pickaxes and shovels have blocks pre-configured. You can add block support for other tools through the config
- Added block support for Magma Blocks on pickaxes
Detominer is a server-side mod, but can be also installed on your clients, allowing you to experience the mod in your singleplayer worlds. If used in a server environment, the config file can be found inside the config folder. But if its used in a client environment, you can easily access the config through the Mod Menu screen.
As always, if you have any suggestions or found some bugs, please report it on my GitHub issues page or you can contact me straight through my Discord server. Links are provided on this modrinth page.
Happy Mining!
Optional dependencies
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:qHDw2ffx:3d1pjj0l"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:qHDw2ffx:3d1pjj0l"
}

