WARNING: In a future release of SkBee, NBT related syntax that uses strings will be removed, and SkBee will focus on the use of NBT compounds.
This is mainly due to the mess of code I have had to write for string related NBT, and I want to work on cleaning this all up.
Example of what will be removed:
Code (Text):
set nbt-block at player to furnace with nbt "{someNBT:1}"
give player a diamond sword with nbt "{myCustomNBT:1}"
add "{SomeNBT:1}" to nbt of player
Don't worry though, cause these simply can be replaced with the nbt compound from string expression:
Code (Text):
set {_n} to nbt compound from "{someNBT:1}"
set nbt-block at player to furnace with nbt {_n}
set {_nbt} to nbt compound from "{myCustomNBT:1}"
give player a diamond sword with nbt {_nbt}
add nbt compound of "{SomeNBT:1}" to nbt compound of player
# OR
set {_n} to nbt compound from "{SomeNBT:1}"
add {_n} to nbt compound of player
This change will most likely happen in SkBee 1.18.0. I just wanted to give everyone plenty of time to switch over to using NBT compounds.
Release News: FIXED: - Changed pattern in "entity block storage" expression due to a conflict
- Appended "effect" to potion effect causes due to a conflict
- Fixed an issue with bossbar types loading
- Delay removing boards from players (fixes a bug when modifying the board when a player logs out, thus creating a new board)
- Fixed a bug with a missing constructor for MerchantRecipe in 1.17.x
- Changed the return of boss bar progress from integer to float (making it more precise)
- Fixed an error when running older builds of MC 1.17.1, and missing structure elements
ADDED: - Added an option in the config to disable the update checker
- Added player purchase event