Repository navigation
Compatibility
Check compatibility for the particular release you download. The development branch can contain support that has not appeared in a release yet.
For Fabric, download compatibility.json from the same release as the JAR. Check your Minecraft version in gameVersions, then check the relevant entry under runtimes for its depends requirements. This JSON file is a reference document and does not need to go in the mods folder.
For Forge, NeoForge, and Spigot/Paper, check the version requirements declared by the artifact and its download listing. Support on one loader does not establish support on another.
The Java requirement declared by Raknetify2 is its minimum. Minecraft or the loader may require a newer runtime. Choose a Java version that satisfies all three.
Use the same Raknetify2 release on the client and the server or proxy accepting its connection when possible. Check the release notes before mixing releases. Encrypted RakNet connections require support for the authenticated encryption protocol at both ends. Original Raknetify and Raknetify2 builds from before that protocol was introduced cannot make these encrypted connections to updated peers.
Raknetify2 carries Minecraft's existing game protocol. Connecting different Minecraft versions requires a compatible protocol translation setup.
The build workflow includes compatibility checks involving Polymer, Krypton, PacketFixer, and Fast IP Ping. Those checks cover the versions and combinations selected by the workflow. Check a release's associated build results when investigating a particular combination.
For a failure in a larger modpack, follow the troubleshooting guide. Include the complete mod versions in your report.