Tags
Creators
Details
Licensed GPL-3.0-only
Published 2 years ago
Updated 3 months ago
All versions
0.20.0
Beta
Splendid Slimes 0.20.06 months ago 31
Compatibility
Minecraft: Java Edition
1.20.1
Platform
Forge
Supported environments
Client and server
Changes
0.20.0
Major update! Some sneaky bugs might be present!
- Reworked hunger mechanics: Slimes will lose half their hunger at 6am every morning so they can be fed once a day
- Added proper largo sucking and shooting with the Slime Vac
- Added ability for Slime Vac to shoot items from inventory without having to put in offhand
- Added trait: Pompous - Slime's favorite food no longer makes it drop double
- Added trait: Ravenous - Will only drop plorts when its hunger bar is full. Each food in its diet feeds a different amount.
- Added Ravenous trait to Bony slime
- Added Pompous trait to Minty slime
- Added forgiving tarrs config option that lets tarrs revive into their previous slime when killed and prevents them from despawning (default false)
- Added data field
ravenous_foodsfor the ravenous trait - Added rendering of incubating slime to Slime Incubator
- Added incubation time to Jade
- Added item capability to Slime Incubators (can insert slime hearts in via hopper)
- Added ghost traits Wormhole and Necromancer to better describe slime's command behavior
- Added ability for redstone signal to pause all machines
- Increased tick rate of Slime Feeder to 80
- Jade will now display wild status next to happiness instead of replacing it
- Fixed Owner being null on servers
- Fixed Slime feeders taking double items
- Fixed Slime info page not taking into account non-Splendid Slimes namespaces
- Fixed config syching of slime owner offline check and enable tarrs being switched
- Fixed slimes suffocating when shot out of vac in corner blocks
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:RptnuYO9:xmopbXpU"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:RptnuYO9:xmopbXpU"
}

