1.3.1.1-1.20.1
Compatibility
Required content
Changes
An emergency hotpatch made to deal with a bug on the bunny origin. I hadn't realized because the testing enviroment runs so smooth, but ANY amount of lag flings the bunny origin uncontrollably. this update should fix that.
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:EZUEpgEv:50dkTmWJ"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:EZUEpgEv:50dkTmWJ"
}

