1.2
Compatibility
Required content
Changes
i know that it feels like its less optimized because of this update because the avarage tick time went up from the last release but that is because we allow more tnt entities at once right now but there are more optimizations at the moment to make it lower if i didnt add those extra optimizations it woudnt be as smooth as it is right now
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:3ohKpqO8:BWfrusxH"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:3ohKpqO8:BWfrusxH"
}

