Skip to content

Commit f8b2510

Browse files
authored
Merge pull request #4 from davidmayr/patch-1
Mention the breaking readOnly bug fix and reword a change
2 parents 5ccc5e8 + ae6c6eb commit f8b2510

File tree

1 file changed

+3
-1
lines changed

1 file changed

+3
-1
lines changed

docs_asp/migrating.md

Lines changed: 3 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -14,7 +14,9 @@ Additionally, the NBT library has been switched from FlowNBT to Kyori NBT. As a
1414
you still need it for something else. If you're not using any additional Slime API methods or accessing extra data, there should be no changes needed.
1515
However, if you do, you'll need to adapt to the new Kyori NBT library. It's worth noting that Kyori NBT is immutable, so when you modify data (e.g. extra data), you'll need to update your code accordingly.
1616

17-
Another change is in how you get the Bukkit world. Instead of using `Bukkit#getWorld(String)`, you can now obtain the world through the `SlimeWorldInstance` now returned when calling `AdvancedSlimePaperAPI#loadWorld(SlimeWorld, boolean)`, using the method `SlimeWorldInstance#getBukkitWorld()`.
17+
Another change is in how you can get the Bukkit world. Instead of just using `Bukkit#getWorld(String)`, you are now also able to obtain the world through the `SlimeWorldInstance` now returned when calling `AdvancedSlimePaperAPI#loadWorld(SlimeWorld, boolean)`, using the method `SlimeWorldInstance#getBukkitWorld()`.
18+
19+
The `SlimeWorld#clone(String,SlimeLoader)` method always copied the `readOnly` property of the parent world or set it to `true` if the provided loader was `null`. This was changed with API 4.0. Cloned worlds are created with `readOnly` set to `false` by default unless the provided loader is `null`.
1820

1921
#### Slime Loaders
2022
Slime Loaders have been separated into different maven packages, so you can choose what loaders you want to bundle with your plugin:

0 commit comments

Comments
 (0)