Tags
Creators
Details
2.0.0-rc.2
Compatibility
Changes
Internal Refactors
Refactored multiple SlimeLink internals for safer async behavior and cleaner event flow:
- Improved world-operation reliability and concurrency handling.
- Added shutdown cleanup for in-progress operation state.
- Improved main-thread handoff safety for sync-required world operations.
- Updated event registration flow and internal unload tracking for SlimeWorld events.
New Syntax & Feature Additions
Added new API coverage and usability improvements:
- Added SlimeWorld load/unload Skript events.
- Added world existence syntaxes (effects/expressions/conditions) for loader-backed checks.
- Added a dedicated unload event bridge so unload handling is reliable and SlimeWorld-specific.
- Updated slime world event filters to use world names (
string) directly:on slime world load of "my_world":
Reliability & Error Handling Improvements
Focused heavily on diagnostics and type safety:
- Fixed property assignment parsing issues caused by unparsed literals.
- Added robust value coercion/validation for Slime properties (clear expected-type errors).
- Improved user-facing Skript errors for loader/world operations.
- Improved loader-expression failure handling and surfaced clearer setup/config errors.
Examples & Documentation
Expanded examples to better reflect real usage:
- Added a comprehensive
SlimeExample.skflow covering loader/world lifecycle operations. - Included practical sequencing patterns (create/load/unload/delete with delays/waits).
Recommendations
Review scripts that chain world operations back-to-back (for example clone -> immediate load).
For best stability, wait for existence/load conditions between async steps.
Check updated docs on SkriptHub: https://skripthub.net/docs/?addon=SlimeLink
Support
For any issues with v2.0.0-rc.2, please open an issue on GitHub or join the Discord server:
https://discord.gg/B9k2xbrp
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:19HbYv9A"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:2tqRuEVl:19HbYv9A"
}

