1.0.6
Compatibility
Changes
Doom Block 1.0.6 For Neoforge 1.21.1
# Doom Block 1.0.6 โ the Doom Block as a tactical toolIn version 1.0.6, I completely redesigned the "Doom" block: now it's not just a threat, but a full-fledged set of apocalyptic effects. Instead of the same type of damage, there are 11 unique scenarios where each block color activates its own mechanics.
What's new: 11 colors โ 11 effects
- ๐ด Red: Lava appears around the block.
- ๐ Orange: Ignites a creature for 30 seconds.
- ๐ก Yellow: Causes a lightning strike.
- ๐ข ** Green:** Gives a 10โsecond jump bonus (level II).
- ๐ต Blue: freezes a creature for 15 seconds.
- ๐ต Turquoise: Strangles the creature inside the blocks.
- ๐ต Blue: fills the area with water.
- ๐ฃ Purple: Destruction Wave โ Every 5 ticks destroys 2 objects within a 20 block radius. The effect increases, creating a cinematic "impending apocalypse."
- ๐ฃ Purple: Instantly revives the object.
- ๐ฃ Pink: Creates 1 burning dynamite.
- โช White: covers the area with snow.
The effects are triggered at every step โ choose the path wisely.
๐ Technical improvements and stability
- Checking properties on each tick: now the mod guarantees the correct disabling of lethality (kill = false disables killing_with_a_touch). This is important when testing builds and configuring maps.
- Purple block optimization: Damage from a wave of destruction is processed asynchronously through the server's work queue. The load is delivered in controlled portions โ this is how we maintain entertainment without sudden spikes in delay.
- Localization and UI: fixed texts for colored blocks, improved formatting and translations into Russian.
Important warning: server load
The new effects add a lot of dynamic events, which increases the load on the server.
- The purple block is the most resourceโintensive. Avoid accumulating several such blocks: the combined load can cause lags or failures.
- If a warning appears in the logs, "Can't keep up!` (the server is 4320 ms or 86 ticks behind), it is recommended to restart the world.
- To test new mechanics, use a separate world and disable the "kill" property, so you can safely experiment with combinations of effects.
๐ 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:DF5Y0Nmv"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:QUBRbxNS:DF5Y0Nmv"
}

