1.7.10
Compatibility
Required content
Changes
Modes, features, hopefully more compatibilities. Part of Create Simulated showcase discord pipeline.
This build may primarily work as a bridge due to a necessary patch that forced sable entity tracking to be dropped on fail that crashed 1/4 instances of others primarily.
This version was built to use Immersive Portals all rather than Irispatch.
Irispatch was an unauthorized fork that I didn't go through proper channels to release and as such much of the development of the last couple days focused on fixing compatibility in a new method.
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:gPVREzvs:iOrezLaz"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:gPVREzvs:iOrezLaz"
}






