0.1.9
Compatibility
Changes
This update fixes a lot of issues, so recommended to update.
Changes
Change: use @intrinsic annotation to improve mod compatibility
Change: re-enabled mixin.collisions.movement optimization.
Change: re-enabled mixin.util.world_border_listener optimization.
Change: entity.collisions.movement: check block below entity before other collisions.
Fixes
Fix: remove incorrect chunk ticket creation.
Fix: block.hopper: broken interaction with modded non-BlockEntity Inventory blocks.
Fix: incorrect ordering of collisions causing non-vanilla entity movement behavior.
Fix: crash when moving hopper by piston with Quark Piston Moves Tile Entities feature.
Fix: massive tps drops occur when using Canary with Cracker's Wither Storm mod.
Fix: crash when entity feet are in the void.
Optional dependencies
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:qa2H4BS9:l0P3FJwx"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:qa2H4BS9:l0P3FJwx"
}

