Tags
Creators
Details
1.0.0
Compatibility
Changes
🚀 MultiProxySync v1.0.0
This is the first official release of MultiProxySync. It is designed to resolve the inconsistency in player counts shown on the server list (Ping) across different entry points in a distributed Velocity network.
✨ Features
-
Global Real-Time Sync: Enables real-time player statistics synchronization across multiple Velocity proxy instances.
-
Distributed Architecture: Powered by Redis Sets for data storage and retrieval—lightweight, fast, and highly efficient.
-
Automatic Self-Healing: If a proxy node goes offline unexpectedly, stale player data in Redis is automatically cleared within 30 seconds, effectively preventing "ghost players."
-
Plug-and-Play: No complex commands required. Once Redis is configured and the server restarts, the plugin automatically takes over the player count display on the server list.
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:kNCfAF9Y:JIqTfhFA"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:kNCfAF9Y:JIqTfhFA"
}

