See GitHub change log for full details

See GitHub change log for full details

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.

Spoiler: NBT CHANGES

Example of what will be removed:

Code:

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:

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:
CHANGED:
- added pattern for `all boss bars` (all custom boss bars registered to the server)
- added missing "placed on" item flag
- hidden flags now defaults to all flags if not specified

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.

Spoiler: NBT CHANGES

Example of what will be removed:

Code:

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:

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

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.

Spoiler: NBT CHANGES

Example of what will be removed:

Code:

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:

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:
ADDED:
- Statistics
- Villager elements (level, experience, profession, type)
- Merchant elements (merchants, merchant recipes, trade select event)
- Update particle effect to include force
- New /skbee info command (used for debugging purposes)
- New update checker (will print in console if an update is available)
- Expression for getting ticks/seconds/minutes/hours from a timespan
- Potion change event
- Show demo screen effect
- Effect to load/unload a chunk (with optional ticket)
- Breed event, event values, expression for breed event entities (parents, baby, breeder)
- Advancement objects, event, expressions
- WorldBorder elements (including virtual world borders for players)
- Expression to get/set spell of a spell caster

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:

set nbt-block at player to furnace with nbt "{someNBT:1}"
give player a diamond sword with nbt "{myCustomNBT:1}"

Don't worry though, cause these simply can be replaced with the nbt compound from string expression:

Code:

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}

I'm not totally sure WHICH version of SkBee this change will happen, I just wanted to give everyone plenty of time to switch over to using NBT compounds.

Release News:
FIXED:
- Fixed an issue when merging NBT compounds of blocks/entities
- Fixed an issue when trying to remove a bound (error saying can not create bound)

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:

set nbt-block at player to furnace with nbt "{someNBT:1}"
give player a diamond sword with nbt "{myCustomNBT:1}"

Don't worry though, cause these simply can be replaced with the nbt compound from string expression:

Code:

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}

I'm not totally sure WHICH version of SkBee this change will happen, I just wanted to give everyone plenty of time to switch over to using NBT compounds.

Release News:
FIXED:
- Fixed a bug with `session.lock` when cloning a world
- Fixed an error when trying to save a non-keyed bossbar into a var, and vars loading on startup
- Fixed an issue when trying to set the lines/title of a scoreboard when a player is offline

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:

set nbt-block at player to furnace with nbt "{someNBT:1}"
give player a diamond sword with nbt "{myCustomNBT:1}"

Don't worry though, cause these simply can be replaced with the nbt compound from string expression:

Code:

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}

I'm not totally sure WHICH version of SkBee this change will happen, I just wanted to give everyone plenty of time to switch over to using NBT compounds.

Release News:
FIXED:
- fixed an error when trying to get block states from an empty structure object
- fixed an error with getting the player in an anvil prepare event

This is a fairly large update which includes a new BossBar system as well as a completely new Scoreboard system.

CHANGED:
- SkBee now only supports Minecraft 1.17.1+ and requires Java 17+
- New scoreboard system using packet based scoreboards. The old scoreboard system used team based scoreboards, which ended up screwing up vanilla team stuff. This new system sends scoreboard packets directly to the player, leaving all vanilla team stuff alone.
The syntaxes for this scoreboard system are the same, so if you are currently using SkBee boards, you won't have to change any of your code.
- Updated Team system. Since SkBee is no longer using team based scoreboards, this system has been re-written to use vanilla MC teams. And hopefully this fixes any issues that we had before, whether they be timing/loading issues, or issues with other plugins. Syntax is the same so no need to change your code.
- Updated NBT-API to support MC 1.19 NBT

ADDED:
- Added expressions to get the level/enchantment of an `enchantment type`
- Added the ability to send text components in action bars
- Added the ability to get/set font for text components
- Added the ability to send normal strings in `send component` effect
- Added a condition to check if a location is within 2 other locations
- Added ability to broadcast with components `broadcast component %component%`
- Added BossBar elements

FIXED:
- Fixed an issue with knockback victim/attacker expression where victim and attacker were backwards

REMOVED:
- Removed old structure elements
- Removed old particle effect patterns

FIXED:
- Fixed a bug when loading text components on Spigot due to a previous change that supported something on paper
- Fixed a bug with the "using" part of translate components
- Fixed an error for a null line when setting scoreboard lines