Links
Tags
Creators
Details
1.1.0
Compatibility
Changes
Client-side rework: Creating, saving, deleting an exporting workspaces now runs entirely on your own client.
Server-safe: The mod never reads or writes files on a server host anymore. All workspace files stay on your local PC.
Removed: the internal networking layer that handled file operations.
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:4nCbfE2p:UOjpVJrH"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:4nCbfE2p:UOjpVJrH"
}

