ВЕРСИИ (5)

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_size` custom bStats chart ## ⚡ Improved * Migrated proxy registration from the legacy Redis Set to the `multiproxysync:proxyList` ZSET * 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-blog` to `net.time-cloud` * Java package changed from `top.timeblog` to `net.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+

## 🚀 MultiProxySync 2.2.0 This update introduces **Redis Pub/Sub-based real-time synchronization** and adds **MiniPlaceholders support**. ### ✨ Added - Added Redis Pub/Sub real-time sync for faster cross-proxy player count updates - Added MiniPlaceholders support - Added the `<multiproxysync_global_player_count>` placeholder ### ⚡ Improved - Improved player count refresh responsiveness across multiple proxies - Improved shutdown cleanup behavior so proxies publish an update after removing their own Redis data - Kept the original heartbeat sync as a fallback mechanism for stability ### 🐛 Fixed - Fixed an early-known synchronization timing issue where player count changes on other proxies were not always reflected quickly enough after player joins, leaves, or proxy shutdowns - Fixed extra Redis overhead caused by the placeholder implementation introduced in **2.1.0**

# 🚀 MultiProxySync v2.0.0 This release is a major upgrade for **MultiProxySync**. Version **2.0.0** introduces the first official public API release and restructures the project into separate API and plugin modules, making third-party integrations cleaner and easier. ## ✨ Features - **Official Public API** Other plugins can now directly access synchronized proxy and player data through the MultiProxySync API. - **Modular Project Structure** The project is now split into: - `multiproxysync-api` - `multiproxysync-plugin` - **Maven Central Support** The API is now available through Maven Central, so developers no longer need to install the API jar locally. - **Cleaner Integration Flow** External plugins can now access the API through `MultiProxySyncProvider`, making integration more straightforward. ## 🔌 API Capabilities The public API now provides: - all online proxies - all players across all proxies - players grouped by proxy - total global player count - player count grouped by proxy ## ⚠️ Notes - The API is read-only. - Redis connection handling remains internal to the plugin lifecycle. - Returned player identifiers are UUID strings. - This update is especially useful for integrations with other Velocity plugins.

### 🚀 MultiProxySync v1.3.1 This update introduces a major enhancement to **MultiProxySync**: a **public API**. In addition to global synchronization, plugins can now directly access synchronized player data across proxies. ### ✨Features * **Public API**： Introduces a public API allowing other plugins to access global player data (total count, grouped data, etc).

# 🚀 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.