Tags
Creators
Details
All versions
5.9+build.3904
Release
5.9 build 390459 minutes ago 14
Compatibility
Minecraft: Java Edition
26.3
26.2
26.1.x
1.21.x
1.20.x
1.19.x
1.18.x
1.17.x
1.16.x
1.15.x
1.14.x
1.13.x
Platforms
Bukkit
BungeeCord
Folia
Paper
Purpur
Spigot
Sponge
Velocity
Waterfall
Supported environments
Dedicated servers only
Changes
5.9 build 3904
This build is a bugfix release for issues found in the previous release.
Change Log
Fixed security vulnerabilities
- (CVSS 4.3) /v1/sessions, /player/uuid/raw, and /v1/extensionGraph now check for access.player.self web permission properly. Previously anyone with only access.player.self could view any other player's data from these endpoints as if they had access.player web permission. This only affected logged-in users.
Data gathering
- Fixed statistics not being gathered on 1.12 servers due to old statistics format (see https://minecraft.wiki/w/The_Flattening_(Java_Edition) )
- Statistics are automatically translated from legacy format to newer one to remain comparable with newer servers running in the same network.
- Possibly fixed statistics json file read failing in some cases due to newline inserted in-memory before json parsing.
- If direct CPU usage is not available, Java 17 method is used rather than deprecated method.
- Fixed NPE related to PlayerGraphSampler and lastSeenColumnCount
Webserver
- Fixed Jetty overwhelming ForkJoinPool (Used for command execution on some servers) with thread access when processing requests. ForkJoinPool is a common resource any non-specified execution may run on in Java.
- Fixed HTTP 500 error from Jetty when X-Forwarded-For header was present and Use_X-Forwarded-For_Header setting was enabled (recommended with reverse-proxies)
Website
- Fixed page clock saying undefined NaN... when refreshing the page
Export
- Fixed Export printing warnings about deprecated endpoint calls
Other
- Dynamic thread allocation: Reduce the amount of idle threads when idle, increase when necessary.
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:wJQfHhxh:qpv50x7z"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:wJQfHhxh:qpv50x7z"
}

