Tags
Creators
Details
All versions
1.21.10-3.15.0
Release
The Block of Angel 1.21.10-3.15.04 days ago 8
Compatibility
Minecraft: Java Edition
1.21.10
Platform
NeoForge
Supported environments
Client and server
Changes
✨ New
- Added the Too Good to Be True advancement for transforming Diamond Ore or Deepslate Diamond Ore into Green Diamond Ore for the first time.
📝 Improvements
- Rebalanced monster summons when transforming Diamond Ore or Deepslate Diamond Ore into Green Diamond Ore with the Rod of Terra or its improved versions.
- Each transformation independently has a chance to summon monsters after a random delay of 2–40 seconds. Transforming more ore increases the overall chance of an encounter and makes an earlier first spawn more likely.
- On Easy: 50% chance to attempt one summon, with a nearby limit of one monster.
- On Normal: 60% chance to attempt one or two summons, with a nearby limit of two monsters.
- On Hard: 70% chance to attempt one to three summons, with a nearby limit of three monsters.
- No summons on Peaceful.
- Limits count all Illusioners and Drowned within 20 blocks of the transformed ore and are checked again before each spawn.
- Summons require a suitable position; if no valid Illusioner position is found, the game attempts to summon a Drowned in water instead.
- Updated the Green Diamond Ore tooltip to describe the summoning behavior.
- Updated the There Is Hope! advancement description with flavor text.
🐞 Fixed
- Fixed The Block of Devil transforming Deepslate Diamond Ore into the normal variant of Green Diamond Ore instead of its deepslate variant.
- Fixed Allays summoned by the Evoker's Amulet sometimes permanently escaping cleanup after chunk reloads, player death, or dimension changes.
- Completely reworked the Allay tracking system.
- Renamed Allays, Allays holding items, and leashed Allays remain protected from cleanup.
- Allays summoned before this update remain untracked.
- Fixed temporary entity and block cleanup timers running faster when multiple dimensions are loaded.
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:7X4T4qK0:VJtWZcJK"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:7X4T4qK0:VJtWZcJK"
}

