Tags
Creators
Details
10.2.0
Compatibility
Changes
Minecraft 26.3 beta
Initial Minecraft Java 26.3 beta builds of TunnelCraft 10.2.0 for Fabric, NeoForge, Forge, Quilt and Paper.
- Adds a native Forge integration and a Quilt distribution using Quilt Loader's Fabric compatibility.
- Includes the 10.2.0 bounded Java PNG decoder, transparent server banners, safe fallback for damaged images and banner texture cleanup.
- Includes persistent TCP/UDP forwarding, reconnect handling and IPv4 voice-service forwarding fixes.
Installation
Use Java 25 and install exactly one TunnelCraft JAR matching your loader:
| Build | Verified loader/API | Location |
|---|---|---|
| Fabric | Fabric Loader 0.20.1 + Fabric API 0.166.2+26.3 | mods/, client/server |
| NeoForge | NeoForge 26.3.0.103 | mods/, client/server |
| Forge | Forge 66.1.8 | mods/, client/server |
| Quilt | Quilt Loader 0.30.2 + Fabric API 0.166.2+26.3 | mods/, client/server |
| Paper | Paper 26.3 build 249 | plugins/, server only |
Every joining player needs a compatible TunnelCraft client mod, including when the host uses Paper. Forge and NeoForge do not need Fabric API.
Validation
107 Java tests passed. All five server variants were tested on Minecraft 26.3. The four modded servers passed actual TCP/UDP payload and relay/server restart checks; Paper passed plugin startup, advancement registration, banner/icon relay pings and clean shutdown. All four client loaders passed 36 PNG/framebuffer cases and 48 multiplayer-screen lifecycle checks in total on Linux with Mesa software OpenGL.
This release is marked beta for the new Minecraft 26.3 loader integrations. The uploaded JARs are the exact verified TunnelCraft 10.2.0 builds.
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:m7EB4M4H:4pJsJ2t7"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:m7EB4M4H:4pJsJ2t7"
}

