Tags
Creators
Details
1.1.0-1.17
Compatibility
Changes
Updates included version of Custom Portal Api to beta 46. This fixes a lot of portal bugs at the expense of severely changing the portal linking logic. Your existing portals will no longer connect to each other.
This also fixes compat with mods using the newer version of Custom Portal Api
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:LwFVdT1s:TYSqpUVn"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:LwFVdT1s:TYSqpUVn"
}

