Links
Tags
Creators
Details
1.0.0
Compatibility
Changes
Tunneler TNT β Version 1.0.0
This release introduces two fully functional custom TNT variants designed for mining, clearing tunnels, and controlled directional blasting. Both TNT types include custom textures, entities, and behavior.
π₯ New TNT Types
Heavy TNT
A stronger alternative to vanilla TNT.
- Explosion strength: 7 (roughly midway between TNT and large charges)
- Fuse time: extended (gives you more time to escape)
- Destroys common terrain blocks (stone, dirt, deepslate, netherrack, etc.)
- Preserves all ores and valuable blocks
- Uses its own custom texture and renders correctly when primed
Tunneler TNT
A directional TNT that digs straight ahead like a mining charge.
- Creates a forward cylindrical tunnel up to 16 blocks long
- Radius: 4, with light edge noise for a natural, explosion-like shape
- Never breaks ores β leaves veins exposed
- Faces away from the player when placed
- Custom texture for all block faces + correct primed entity appearance
β Other Features
- All blocks have full blockstate, model, item, and loot table support
- Entities use
TntRendererfor vanilla-consistent animation, fuse, and visuals - Works in survival and creative modes
- Fully compatible with Minecraft 1.21.10 using Mojang mappings
π Known Limitations (for future updates)
- Explosion visuals (particles) are still vanilla TNT
- Tunnel shape does not currently scale or vary in diameter
- No sound or particle variations yet
β Summary
This first version establishes the core TNT behaviors, rendering, block models, and directional tunneling. Future updates can expand with new TNT types, mining utilities, particle effects, and configurable explosion options.
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:mfTOreiM:AMNFrpZ8"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:mfTOreiM:AMNFrpZ8"
}

