Tags
Creators
Details
Licensed GPL-3.0-only
Published 7 months ago
Updated 3 days ago
All versions
2.2.2
Release
peyaj's CustomDiscs 2.2.2last month 11
Compatibility
Minecraft: Java Edition
26.2
26.1.x
1.21.x
Platforms
Paper
Purpur
Changes
Bug Fixes & Enhancements
- Fixed Server Resource Pack Overwrite Bug: Resolved a critical issue where the plugin's auto-generated resource pack would forcefully overwrite and delete the server's primary resource pack (from server.properties, ItemsAdder, or Oraxen) upon a player joining the server.
- Dedicated Pack UUID Assignment: Assigned a deterministic persistent Pack ID to the custom disc pack, ensuring that future runtime updates automatically overwrite only the disc layer without spawning duplicate packs in the client.
- Fixed Java Edition Audio Range: Fixed a severe calculation bug that caused Java players to hear custom music discs blasting at 100% max volume over massive distances (up to 192+ blocks). The audio now correctly and smoothly fades out linearly from the jukebox source based exactly on the
jukebox.rangesetting in your config! (Note: You will need to regenerate your resource pack for the smooth fade-out fix to take effect).
Configuration Updates
We have added a brand new resource-pack section to config.yml allowing server owners to fully customize Java pack delivery settings:
- replace-existing: false (Default) - Safely layer the pack instead of purging existing server packs.
- send-on-join: true - Toggle whether players are prompted on login.
- prompt - Configure a custom MiniMessage prompt (e.g.
<gold>Download Custom Discs</gold>) - required - Enforce mandatory pack download.
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:abKn8l6H:7xGS024B"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:abKn8l6H:7xGS024B"
}

