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.sk flow 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

Internal Refactors

Refactored syntax registration for improved maintainability and performance.

Dependency Updates

Updated Skript to version 2.14.1 for compatibility and latest features. Also changed the target Java version from 25 to 21 for wider compatibility.

Recommendations

Check out the updated syntax documentation on SkriptHub for details on any changes: https://skripthub.net/docs/?addon=SlimeLink

If upgrading from previous versions, review your scripts as some internal changes may affect compatibility.

Support

For any issues with this release candidate, please open an issue on GitHub or join the Discord server: https://discord.gg/B9k2xbrp

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

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%

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.

This is a little update that simplifies some of the work around Slime Loaders in the background, fixes an issue that occurs with world names and introduces a slight syntax change that isn't backward compatible.

Regarding the world names, I've implemented a check that validates names and follows the naming conventions set within Minecraft. World names now only allow the following to be included;

1. Lowercase letters
2. Numbers
3. Hyphens
4. Underscores
5. Periods
6. Slashes

Syntax Change

It was recently brought to my attention that the following syntax %slimeproperty% of %slimepropertymap% would conflict with existing Skript patterns causing errors when trying to use of patterns of other types.

This syntax has now been changed within the "Change Slime Properties" expression and "Check Slime Property" condition, the syntax is now as follows; slime property %slimeproperty% of %slimepropertymap%

Thanks to Jake for noticing this and providing a solution!

• Added "slime property" prefix to property expression by @JakeGBLP in https://github.com/danielmillar/SlimeLink/pull/2

Full Changelog: https://github.com/danielmillar/SlimeLink/compare/v1.0.0...v1.1.0