1.0.7
Compatibility
Changes
Doom Block 1.0.7 For Neoforge 1.21.1
Whatโs new in version 1.0.7? ๐ฅ
Weโve upgraded the Doom Block for smarter, more tactical gameplay โ with refined controls, a new stealth variant, and stricter performance safeguards.
โ Command overhaul
The /doomblock command now uses a 5โargument syntax:
/doomblock radiusX radiusY radiusZ doom_blocks Boolean
This gives you precise area control and lets you toggle killing_with_a_touch in one line.
๐ฑ๏ธ Stalactite toggle
Enable killing_with_a_touch instantly by rightโclicking an active Doom Block with a Stalactite in your main hand.
A visual pulse confirms the change โ no commands needed.
๐ป New Invisible Doom Block
This stealth variant makes entities inside its zone invisible โ even while moving or interacting.
The effect lingers based on the blockโs last state, making it ideal for traps.
๐ Cleaner property handling
Breaking a Doom Block resets its properties: killing_with_a_touch wonโt carry over.
Reactivate it with the Stalactite to keep setups intentional.
โ ๏ธ Performance & stability warning
Dense Doom Block setups (especially combined with Redstone, lava, and water) can cause heavy load and extreme block updates per tick.
- In extreme cases, this may freeze the game completely โ if the interface stops responding, a device reboot is the recommended recovery step.
- Avoid activating many Doom Blocks in a small area at once.
- Test new configurations in a separate world first.
- Watch for server warnings like โCanโt keep up!โ โ they signal overload.
๐ก Testing tip
Lay out blocks with kill = false, toggle killing_with_a_touch only when ready, and activate Invisible Doom Block last to keep testing safe.
๐ Compatibility
- Platform: Minecraft NeoForge 1.21.1.
- Loader: NeoForge only (Forge and Fabric are not supported).
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:QUBRbxNS:325h1dTf"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:QUBRbxNS:325h1dTf"
}

