mc1.20.1-0.3.1
Compatibility
Changes
Small update fixes a memory leak in hoppers, and fixes some other issues.
If you got into any issue when using Canary, please make sure to report it in the issue tracker from here.
To see the available configurable options, press here.
Additions
- New: allow the cached ominous banner to be used on Raid#pickUpItem() method.
- Change: cache Raid#getLeaderBannerInstance to be only one instance.
- Change: remove two duplicated accessors.
- Change: allow the hoppers use CanaryStackList.
- Change: hopper optimizations will be disabled automatically if easy villagers mod is loaded.
- Change: separate ServerChunkCacheMixin in other package in mixin.chunk.replace_streams.servercore_compat and disable it automatically if ServerCore is installed.
- Change: add BlockEntityMixin, NbtCompoundMixin($Type) and ObtainRaidLeaderBannerGoalMixin to canary.mixins.json.
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:bbZjBL8C"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:qa2H4BS9:bbZjBL8C"
}

