Compatibility
Server versions
Section titled “Server versions”PortBridge targets Minecraft 1.21.11+ on Paper and compatible forks. It compiles against Paper 1.21.11 and uses Bukkit lifecycle, configuration and event APIs plus Paper’s Adventure components. It does not use Minecraft internals or version-specific world APIs.
| Server version | Runtime Java |
|---|---|
| Paper 1.21.11 | Java 25 or newer |
| Paper 26.1–26.3 | Java 25 or newer |
The plugin emits Java 25 bytecode; building from source uses the Java 25 toolchain. Minecraft versions older than 1.21.11 are outside the supported range. Compatibility has been checked through Minecraft 26.3; future releases require another compatibility check. Folia and Spigot are not supported.
PortBridge requires Java 25 for its compiled classes, including on older server versions. The Paper installation reference lists the server software’s own Java recommendations.
Validation
Section titled “Validation”The source builds against the minimum API, and unit tests cover message validation, settings, retry behavior, archive handling, status packets and text layout. Isolated Paper smoke checks verify plugin startup, registered commands, permission errors, reloads and listener registration. The release notes list the exact server builds checked. These checks do not cover every intermediate fork or real internet route.
Version 1.0.0 passed these checks on Paper 1.21.11 build 132 / Java 25 and Paper 26.3 build 157 / Java 25. The unit suite passed all 44 tests.
Native Bore downloads
Section titled “Native Bore downloads”| Operating system | Managed architectures |
|---|---|
| Windows | x64, x86 |
| Linux | x64, ARM64 |
| macOS | x64, ARM64 |
Other targets require a compatible custom executable. Managed downloads use pinned SHA-256 verification. A custom executable is checked for usability and is outside managed release verification.
Network services
Section titled “Network services”PortBridge forwards Minecraft Java TCP traffic. It does not expose Bedrock, UDP query or other UDP services, and it does not preserve real player IP addresses. A relay can introduce latency. Disabling public health checks marks the connection as unverified; local status checks remain required.