Tags
Creators
Details
1.1.2
Compatibility
Changes
This update introduces features for checking SlimeWorld existence and adds support for importing vanilla worlds into Slime format.
SlimeWorld Exists - Condition
A new condition allows you to verify if a SlimeWorld exists in the config. This is particularly useful for managing dynamic world systems, such as private worlds, where you need to decide whether to load an existing world or create a new one.
The syntax is as follows:
(slimeworld|slime world) named %string% (exists|1:doesn't exist)
Import Vanilla Worlds
You can now import existing vanilla worlds into Slime format, enabling their use as templates for future world creation.
The syntax is as follows:
import world with path %string% as (slimeworld|slime world) named %string% with [datasource|data source] %slimeloader%
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:kz5qGnNE"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:2tqRuEVl:kz5qGnNE"
}

