Tags
Creators
Details
All versions
2.5.2
Release
CustomDiscs-SVC 2.5.26 months ago 2,970
Compatibility
Minecraft: Java Edition
1.21.x
1.20.6
Platforms
Folia
Paper
Purpur
Required content
Any compatible version
Any compatible version
Any compatible version
Changes
2.5.2
Added
- HTTP/HTTPS proxy support for LavaPlayer (only YouTube yet) via
providers.youtube.http-proxyinconfig.yml- Format:
[scheme://][user:pass@]host:port - Supports basic auth and both
http://andhttps://proxy schemes
- Format:
Fixed
- Server no longer lags on startup when
LavaPlayerManagerImplinitializes — all registrations (YouTube, SoundCloud, proxy setup) now happen asynchronously; disc playback waits for initialization to complete before starting data.ymlwas being rewritten on every autosave tick even when nothing changed — introduced a dirty flag so the file is only saved when data has actually been modifieddata.ymlwas not saved on plugin shutdownallow-hoppersconfig option is nowtrueby default
Security
DownloadSubCommand: reject URLs with non-http/https schemes (e.g.file://,jar://) to prevent local file read via download commandDownloadSubCommand: replacedcontains("../")filename check withPath.normalize()boundary validation to properly block all path traversal variantsHTTPRequestUtils: reject non-http/https schemes in all outgoing HTTP requestsLegacyUtil: validateLOCAL_DISCPDC value on read to prevent path traversal via NBT-edited disc items
Language
- Added
error.command.invalid-urlkey toen_USandru_RU - Removed unused key
error.play.no-permissionfrom both locales - Removed unused key
error.command.no-youtube-supportfromen_US
Dependencies
commandapi11.1.0 → 11.2.0packetevents2.11.2 → 2.12.0shadow(Gradle plugin) 9.4.0 → 9.4.1
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:1yowwDpk:skB3N5Lb"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:1yowwDpk:skB3N5Lb"
}

