Tags
Creators
Details
Licensed MIT
Published 10 months ago
Updated 3 weeks ago
All versions
3.6.0
Release
BS CustomJukebox 3.6.02 months ago 231
Compatibility
Minecraft: Java Edition
26.3
26.2
26.1.x
1.21.4–1.21.11
Platforms
Folia
Paper
Purpur
Spigot
Changes
[3.6.0] - 2026-08-31
Added
- Volume in decibels for the server, zone and personal commands:
-6dbis half,-12dba quarter,-20dba tenth — easier to judge by ear than the linear scale, where 0.5 does not sound half as loud. - Presets and percentages for zone and personal volume too, not just the server one:
silent,quiet,normal,loud,maxand values such as30%. - Volume feedback names what it did —
0.30 (30%, -10.5 dB)— and warns above 1.0 that the sound is already at full loudness and only carries further, since Minecraft widens the radius (volume * 16blocks) rather than raising the gain. /cjb zone volume <zone> <value> norestart, to let the current track finish at its old volume.ambient-zones.pause-during-disc, to keep discs and zone music layered.
Changed
- All three volume commands share one parser, so their presets and ranges cannot drift apart.
- The author prompt in the disc editor shows the formatting example itself, instead of pointing at the display name prompt that whoever opens the author field first never sees.
- Editor titles drop the namespace prefix a server's disc ids share:
Edit: music_disc.newbeginnings_themebecomesEdit: newbeginnings_theme. The prefix is read from the ids in use rather than assumed, socustom.or a multi-level one works the same; where ids do not all share one, nothing is stripped.
Fixed
- Colour codes in a disc's author field were printed instead of applied —
&eArtistreached the tooltip as the literal text<yellow>Artist. Legacy codes are now recognised with either marker (&or§) and in either case, so hex and gradients survive as well. The same fix covers everywhere else the two markers were mixed: fragment lore, the jukebox subtitle, GUI text. - A disc and an ambient zone played over each other. The zone now falls silent for the listeners who can hear a disc and returns when it ends — not between the tracks of a playlist, where the next one starts immediately.
- A zone's own volume followed the server volume for anyone with a personal volume set: at the shipped server volume of 4.0, a zone at 0.2 collapsed to a twentieth of the player's setting. An explicit zone volume is absolute now; only zones on
inheritfollow the server. /cjb music volumedid nothing until the current track ended — minutes, on a looping zone. It restarts what that one player hears, immediately./cjb volume ... restartignored ambient zones, restarting jukebox playbacks only. The same applied to/cjb muteand/cjb unmute.norestarthad no effect, because saving a zone restarted it before the flag was read.- Tab completion offered no quiet value.
/cjb zone volumesuggestedinherit, 1, 2, 3, 4, and since 1.0 is already full loudness, turning a zone down reliably ended at 1 and stayed loud. /cjb volumelooked broken to an admin with a personal volume set, which replaces the server volume rather than scaling it. The command now says which value wins and how to undo it.- Chat confirmations printed the markup they had just applied, while the item itself came out correctly coloured.
- Long names ran past the edge of the GUI — admin panel entries and all five editor titles are shortened now, measured in visible characters so a gradient's tags are not cut in half. The disc item players receive keeps its full name.
- Language files never gained messages added after they were first written; one long-running server was missing 170 of its 226. Missing messages are written in on every start, strictly additively — existing lines and comments are untouched.
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:YDoz2hx6"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:SFWdW3tI:YDoz2hx6"
}

