Tags
Creators
Details
Licensed Apache-2.0
Published 7 months ago
Updated last month
All versions
2.3.0
Release
MultiProxySync 2.3.0last month 60
Uploaded by
Compatibility
Minecraft: Java Edition
26.2
26.1.x
1.21.x
1.20.x
1.19.x
1.18.x
1.17.x
1.16.x
1.15.x
1.14.x
1.13.x
1.12.x
1.11.x
1.10.x
1.9.x
1.8.x
1.7.x
Platform
Velocity
Changes
This update reworks proxy health tracking, adds update checking and bStats metrics, and migrates the API package coordinates.
β¨ Added
- Added an update checker for new MultiProxySync versions
- Added bStats anonymous usage metrics
- Added the
proxy_network_sizecustom bStats chart
β‘ Improved
- Migrated proxy registration from the legacy Redis Set to the
multiproxysync:proxyListZSET - Proxies now register immediately on startup and refresh their heartbeat periodically
- Heartbeat timestamps now use Redis server time to avoid system clock differences between proxies
- Proxies inactive for more than 30 seconds are automatically treated as offline
- Proxy lists, player statistics, and API queries now only include active proxy nodes
- Improved shutdown cleanup by cancelling heartbeat tasks and removing the proxy from Redis
π API Migration
- Maven Group ID changed from
top.time-blogtonet.time-cloud - Java package changed from
top.timeblogtonet.timecloud - API method signatures remain unchanged
- Plugins using the API must update their dependency coordinates and Java imports
πΊοΈ Version Direction
- The 2.3.x release line will remain focused on player count and player list synchronization
- Future 2.3.x updates will mainly provide maintenance, bug fixes, and stability improvements
- New feature expansion will continue in 3.0.0+
Optional dependencies
Unavailable version
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:kfdZKrFS"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:kNCfAF9Y:kfdZKrFS"
}

