1.0.8
Compatibility
Changes
Doom Block 1.0.8 For Neoforge 1.21.1
Whatโs new in version 1.0.8? ๐ฅ
Weโve focused on stability, precision, and smarter interactions โ turning Doom Block from a chaotic hazard into a finely tuned tool. This update addresses key edge cases, refines behavior for multi-effect setups, and introduces new controls for performance and visibility. Every block now behaves exactly as intended, even in complex builds.
โ Whatโs new: stability fixes and refined interaction logic
Weโve resolved critical interaction and state-handling bugs to make Doom Block more reliable:
- Right-click (ะะะ) behavior is now fully consistent across all block states โ no more missed inputs or unresponsive blocks.
- Invisible Doom Block now correctly applies invisibility to entities walking over it, without breaking the effect mid-movement. This makes stealth setups predictable and trap designs more reliable.
- When multiple properties are enabled on a Doom Block of any color, each effect now runs independently with its own logic. Previously, overlapping properties could disable the block entirely; now, every effect works as intended, enabling layered trap designs.
๐ฎ Fine-tuned property control: the particles toggle
Weโve added a new property to help you balance visibility and performance:
- The
particlesflag controls whether particle effects appear when a Doom Block is activated. - Set
particlestofalsefor optimized builds โ this disables particles entirely, reducing server load and improving FPS in large-scale setups. - Set
particlestotrueto clearly indicate when a Doom Block is active. This is ideal for testing, teaching, or when you want players to notice the blockโs state at a glance.
๐ก Tip: Use particles=false on servers with many Doom Blocks to keep performance smooth. Switch to true during testing to confirm activation visually.
โฑ๏ธ Smarter ticking: every 10 ticks, no exceptions
To keep behavior consistent and reduce unnecessary load, weโve standardized the update cycle:
- Every Doom Block now updates its state every 10 ticks (0.5 seconds), regardless of its current properties or effects.
- This ensures that effects like invisibility, damage, or color-based logic stay synchronized without overloading the server with constant checks.
- The fixed tick interval also makes timing-based traps and puzzles more predictable and easier to design.
๐งฑ Under-the-hood improvements: BlockEntity foundation
Weโve introduced a BlockEntity for Doom Blocks to support future features and keep current behavior stable:
- The BlockEntity stores the blockโs current state (active/inactive, properties enabled, particle setting, etc.) so that it persists reliably across world reloads.
- This lays the groundwork for upcoming features like stored items, custom effects, and more advanced logic โ all while keeping current mechanics stable.
- State data is now saved and loaded cleanly, so your builds retain their intended behavior after restarting the world.
โ ๏ธ Important warning: performance and stability
With the new ticking logic, particle control, and BlockEntity support, Doom Block is more powerful than ever โ but itโs still a high-impact mod:
-
Avoid activating hundreds of Doom Blocks in a small area at once, especially with
particles=true. -
If your server logs show warnings like:
[20:52:31] [Server thread/WARN] [minecraft/MinecraftServer]: Can't keep up! Is the server overloaded? Running 4320ms or 86 ticks behind itโs a sign the server is struggling. We recommend reducing active Doom Blocks, setting particles=false, or testing in a separate world first.
Always test new configurations in a dedicated test world before deploying them in your main server or shared builds.
๐ก Tip: safe testing with layered toggles
When designing setups with the new features:
- Start with particles=false to keep performance smooth while laying out your design.
- Enable properties one at a time to confirm each effect behaves as expected.
- Test Invisible Doom Block separately to see how it interacts with movement and other effects.
- If something feels off, break and re-place the block โ this ensures a clean state and helps isolate any unexpected behavior.
๐ 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:SoBwNLpq"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:QUBRbxNS:SoBwNLpq"
}

