Tags
Creators
Details
2.0.0-beta.1
Compatibility
Changes
After some long inactivity on this project, we're finally back with a major update that reworks a lot of the internal systems and provides no backward compatibility with V1.x
World Configs
I've removed the world config that saved information about the slime world such as the loader and properties. This was done to give the users more fine control over their worlds and reduced issues where the config would have world data but the world never existed in the data source.
Loader Changes and Syntax Changes
Almost every syntax has been changed, this is due to the rework of Loaders. Originally SlimeLink would handle and store each loader that the user initialized but this has now changed. Users will be in charge of creating their own loaders and storing it somewhere. You'll need to pass this loader into almost every syntax as we no longer store world data.
Internal Changes
A bunch of internal workings has been changed regarding how and when I would save and load SlimeWorlds. Now with most effects and expressions the world is created but never saved or loaded unless specified in the description. This again gives the user more fine control over what they'd like to do with the world.
Recommendations
If you're going to switch to this version then you'll want to have a look at all the new syntax on SkriptHub which you can find here; https://skripthub.net/docs/?addon=SlimeLink
Any previous scripts that you have that were written using V1.x will need updated as they will not work at all with this new version.
Support
If you're experiencing any issues with his new update then please open an issue or contact me on discord using the server below; 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:GMFVywPS"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:2tqRuEVl:GMFVywPS"
}

