Tags
Creators
Details
4.0.2-1.20.1
Compatibility
Required content
Changes
Bump to 4.0.2-1.20.1
Fixes an issue where the myLoot container does not have the same properties as the original container, but we try adding non-existing properties. Unfortunately, this means it's possible the myLoot container won't have all of the same features as the original, if it's some modded container with different properties.
For example:
[23:09:35] [Server thread/ERROR]: Encountered an unexpected exception java.lang.IllegalArgumentException: Cannot set property class_2746{name=ancient, clazz=class java.lang.Boolean, values=[true, false]} as it does not exist in Block{myloot:loot_chest} at net.minecraft.class_2688.method_11657(class_2688.java:122) ~[client-intermediary.jar:?] at org.spoorn.myloot.core.LootableContainerReplacer.lambda$registerTickCallback$2(LootableContainerReplacer.java:137) ~[myloot-4.0.1-1.20.1.jar:?]
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:kHc6jKsv:DdLXC7Bi"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:kHc6jKsv:DdLXC7Bi"
}

