Tags
Creators
Details
3.16.0
Compatibility
Changes
This update brings dialogs, some new components and a bunch of other things.
IMPORTANT
Just a reminder if you’re using Skript 2.14.0+ that SkBee no longer has particle syntax.
You will have to use Skript's new particle syntaxes.
🛠️ THIS UPDATE 🧑🏼🍳:
ADDED:
- Added dialogs (See Dialog Wiki for more info)
- Added a player connection type/classinfo. This will be used with the async config event and dialogs.
- Added an effect to freeze a player connection in the async config event, and unfreeze later.
- Added an effect to remove attribute modifiers by key
- Added an expression to get the values of a tag key
- Added an expression to get/change the damage type component of an item
- Added an expression to get/change the minimum attack charge component of an item
- Added a section to apply the attack range component to an item
- Added a section to apply the piercing weapon component to an item
- Added a section to apply the swing animation component to an item
- Added a section to apply the use effects component to an item
- Added an option in the raytracing expressions to filter entities by allowing (whitelist) instead of just ignoring (blacklist)
CHANGED:
- Updated the internals of the parse effect/expression to better handle the current event (Thanks @Fusezion)
FIXED:
- Fixed armour trim expression not applying trims to non-armour items
- Fixed the name of the jukebox classinfo in the docs
- Fixed some issues with the entity knock back event (see PR 896 for further details, thanks @Fusezion)
- Fixed an issue with checking custom NBT as a condition, it creating a new compound, and screwing up the ItemStack and possibly other features (Thanks @sovdeeth)
INTERNAL:
- Added more metrics to show Minecraft/Skript version per release of SkBee
- This will give us a better understanding of what we should be supporting
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:a0tlbHZO:rJ6N4qLc"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:a0tlbHZO:rJ6N4qLc"
}

