Links
Tags
Creators
Details
0.5.0-rc.2
Compatibility
Changes
Fixed since 0.5.0-rc.1
- Fixed a WebSocket lock-order deadlock when closing slow consumers after outbound event backpressure.
Requirements
- Paper 26.2 and Java 25; server-side only.
- Folia, Spigot, Bukkit-only and Purpur servers are not claimed compatible.
- Notice is optional and is only needed for the Notice integration actions.
Validation
This upload is the unchanged JAR from the GitHub 0.5.0-rc.2 release. Its checksum matches the published SHA256SUMS and the JAR retained with the Paper test server. Archive integrity, plugin metadata, shaded dependencies and bundled notices passed packaging verification.
Retained results, reviewed on 2026-09-18, contain 31 successful checks on Paper 26.2-111-main@f570646 with Java 25.0.1+8-LTS-27. Coverage includes REST authentication and scopes, idempotency, rate limits, metrics authentication, JWT validation, relay results and event acknowledgements, WebSocket authentication, reconnect replay and slow-consumer closure. The server log records normal Bridge disable and server shutdown. These are existing runtime results, not a new test run.
This remains a Beta release candidate. The complete stable-release gate is still open, including documented default-configuration startup, full restart acceptance and executor/socket leak checks.
Plugin SHA-256:
6850feb0b4d30d4faaf9f5073eab266f69a7234c2367df130782fc5d70fd0b41
Installation and upgrade
Use this version in place of 0.5.0-rc.1 and apply the update through a normal server restart. Back up configuration and credential files first. See the quick start.
WebSocket, JWT, relay, metrics and mutating actions remain disabled by default. Keep local action and event allowlists narrowly scoped.
Optional dependencies
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:vdbb0fEL:5vvDYMwP"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:vdbb0fEL:5vvDYMwP"
}

