Tags
Creators
Details
2.1.5
Compatibility
Changes
[2.1.5] - 2026-04-18
Fixed
-
Permission system completely overhauled: Players were incorrectly blocked in areas without explicit WorldGuard flags
customjukebox.useis now actually checked (previously only defined but never used)- WorldGuard now only checks for explicit
use deny- Areas without the flag allow jukeboxes - Specific error messages instead of generic βno-permissionβ (Region/Claim/Permission separated)
- New permission
customjukebox.bypass.protectionto bypass WorldGuard/GriefPrevention (default: OP)
-
Various bug fixes: Fixed several potential crashes and race conditions
- Thread safety for the playlist queue (synchronized methods)
- Safer file saving with
Files.move()instead of delete+rename (prevents data loss on Windows) - Null checks for metadata access, WorldGuard locations, and Adventure API colors
- ArrayIndexOutOfBounds protection in the Disc Editor for corrupt states
- UpdateChecker: JSON null safety and resource leak fix
-
Minor improvements:
- Mute state is now persisted in config.json (survives server restart)
- Location-based HashMap key replaced with string key (more reliable cooldown)
- Tab completion now shows subcommands even with empty input
- Category validation in the Creation Wizard (warning for non-existent categories)
- More efficient item distribution (a stack instead of a loop)
- Plugin tasks are now properly terminated on onDisable
Changed
- Paper API 1.21.11: Plugin now compiles and runs against Paper 1.21.11
- Resource Pack updated:
pack_formatset to 75 (1.21.11), sound namespace corrected - Default Configs:
versionfield added to config.json and disc.json - README: Detailed permissions documentation with tables and descriptions
Added
- Permission
customjukebox.bypass.protection(default: OP, included incustomjukebox.admin) - New error messages in all 4 languages:
no-permission-jukebox,no-permission-region,no-permission-claim
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:SFWdW3tI:YdS8ICTX"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:SFWdW3tI:YdS8ICTX"
}

