Links
Tags
Creators
Details
2.0.0+mc1.21-neoforge
Compatibility
Changes
Changelog [2.0.0+mc1.21-neoforge]:
-
Changed the version naming system. Mod versions now use this format: <mod version>+mc<minecraft version>-<mod loader>
-
Adjusted conditions for playing sound of block destruction
-
Fixed vanilla bug that caused the Ender Dragon to collide with its own fireball
-
Added handling for waterlogged blocks
-
Added mod config containing these settings:
dragonDebrisUpdateInterval - How often flying debris created by dragon should visually update.
dragonTransparentFluids - Whether dragon should fly through water and lava or destroy them.
destroyWaterloggedBlocks - If true, waterlogged blocks become debris and fly away.
deleteBlocksWithNBT - If true, blocks that contain NBT data will be deleted.
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:hsDp2t4Z:NgM8VVrb"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:hsDp2t4Z:NgM8VVrb"
}

