Tags
Creators
Details
1.1.1
Compatibility
Changes
This patch includes internal changes to background world unloading and adds a new option to the Clone Slime World effect.
Syntax Change
The Clone Slime World effect now supports an optional readOnly flag when cloning a world.
The syntax is now as follows;
clone (slimeworld|slime world) from %string% to %string% [readonly:as ReadOnly] [newsource: with [datasource|data source] %-slimeloader%]
- If readonly is not specified, the clone will use the same readOnly setting as the source world.
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:2tqRuEVl:mPA5L2y9"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:2tqRuEVl:mPA5L2y9"
}

