Tags
Creators
Details
1.0.1
Compatibility
Changes
This release strengthens backend-to-proxy communication, improves security, and updates compatibility with modern Minecraft server environments.
What's Changed
- Added compatibility with Minecraft Java Edition 26.3.
- Verified Paper backend communication with BungeeCord and Velocity proxies.
- Fixed stale backend messages and improved message handling.
- Fixed permission escalation vulnerabilities in command forwarding.
- Improved validation of incoming communication.
- Improved reliability of backend-to-proxy command execution.
- Improved error handling and connection stability.
- Modernized internal code and dependencies.
- Improved overall security and runtime reliability.
Compatibility
- Minecraft: Up to 26.3
- Backend: Paper
- Proxies: BungeeCord, Velocity
Notes
This is an important maintenance and security update. Updating is strongly recommended, particularly for networks using backend-to-proxy commands.
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:WAIcE2sc:KK7bdYA6"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:WAIcE2sc:KK7bdYA6"
}

