ViaCheckConnection sends players a configurable message based on their Minecraft Java client protocol. Version 2.0.0 covers release protocols from 1.7.2 through 26.3 and provides plugins for Paper, BungeeCord, and Velocity. Maven generates the protocol table from the ViaVersion registry for Java Edition.
Use JDK 25 and run the Maven Wrapper from the project root. On Windows, run .\mvnw.cmd clean verify. On macOS or Linux, run sh ./mvnw clean verify. You can also run mvn clean verify with Maven 3.9.
| Platform | Plugin JAR |
|---|---|
| Paper | paper/target/viacheckconnection-paper-2.0.0.jar |
| BungeeCord | bungee/target/viacheckconnection-bungee-2.0.0.jar |
| Velocity | velocity/target/viacheckconnection-velocity-2.0.0.jar |
Run your platform on Java 25 or newer. Copy its plugin JAR into plugins/, replacing the previous ViaCheckConnection JAR if present, and restart. The common module is already included in each platform JAR.
- Paper and Velocity require ViaVersion in their
plugins/directory. ViaCheckConnection uses its API to read each player's original protocol. Paper sends the message when the player joins, and Velocity sends it after each successful backend connection. ViaVersion 5.12.2 - BungeeCord sends the message after each successful backend connection, including server switches. To use the ViaVersion API, install ViaBungee in
plugins/and ViaVersion inplugins/ViaVersion/. When ViaVersion is unavailable or returns an unknown protocol, ViaCheckConnection reads the handshake protocol from BungeeCord. ViaBungee 0.4.0
Stock BungeeCord accepts clients starting at 1.8. Velocity accepts clients starting at 1.7.2. BungeeCord protocols · Velocity compatibility
The plugin reports the protocol it sees. A network accepting clients across versions needs compatible server and proxy software and, where needed, protocol translation such as ViaVersion, ViaBackwards, and ViaRewind. Install ViaCheckConnection on the proxy when the proxy translates connections before handing them to Paper. ViaVersion · ViaBackwards · ViaRewind
The plugin creates config.yml in its data directory on first start. All three JARs bundle the same default file. Default config.yml
- Existing files and message overrides are preserved. Missing keys use bundled defaults. To customize the new versions, copy the corresponding entries from the default file.
- Versions with the same wire protocol share a message. For example, 26.1, 26.1.1, and 26.1.2 share
v26_1. If you set several keys for the same protocol, the primary key listed in the default file takes priority. - Use legacy
&color codes, set a quoted empty string to disable a message, or editunknown_versionfor unrecognized protocols. - Run
/viacheck reloadwithviacheck.use, or runviacheck reloadfrom the console. An invalid edit leaves the previously loaded configuration active.
© x9nico · Apache License 2.0