
MultiProxySync
Solve inconsistent player counts across multiple Velocity proxies.
- Загрузки
- 141
- Подписчики
- 3
- Обновлён
- 23 апреля 2026 г.
- Лицензия
- Apache-2.0
Опубликован 16 марта 2026 г.

🚀 MultiProxySync
Solve inconsistent player counts across multiple Velocity proxies.
📖 About
MultiProxySync is a plugin for Velocity proxy networks designed for multi-proxy setups that need global player count synchronization.
It uses Redis to synchronize player counts and player lists between multiple proxy nodes, so your whole network can show a more consistent and accurate online player count.
Starting from newer versions, MultiProxySync also uses Redis Pub/Sub to improve synchronization responsiveness.
When players join, leave, or when a proxy shuts down, other proxies can refresh their cached global player count much faster.
If your network uses more than one Velocity proxy and you want the player count shown in the server list to stay in sync across all entry points, this plugin is made for that situation.
It is especially useful if your proxies show different online numbers, player counts are not syncing correctly, or the number of players appears inconsistent across multiple proxy servers.
📷 Preview

✨ Features
Consistent Network-Wide Player Count
Keeps the online player count more consistent across all Velocity entry points.Faster Count Refresh
Player count changes propagate more quickly when players join, leave, or when a proxy shuts down.Automatic Cleanup
Stale data from crashed or offline proxies is cleaned up automatically.MiniPlaceholders Support
Automatically registers placeholder support when MiniPlaceholders is installed.Public API
Exposes synchronized proxy and player data for other plugins.Lightweight and Practical
Simple to configure and suitable for real production multi-proxy environments.
📦 Requirements
You will need:
- Velocity proxy server
- Redis database
Optional
- MiniPlaceholders
If installed, MultiProxySync will automatically enable placeholder support.
🛠️ Installation
- Download the latest
multiproxysync-pluginrelease - Place it into the
pluginsfolder of all your Velocity proxies - Start each proxy once to generate the configuration file
- Edit the generated
config.yml - Restart all proxy instances
📄 Configuration Example
plugin:
serverName: Proxy-01
enabled: true
redis:
host: 127.0.0.1
port: 6379
password: YourPassword
🔤 Placeholder
If MiniPlaceholders is installed, MultiProxySync will automatically register the following placeholder:
<multiproxysync_global_player_count>
This placeholder returns the synchronized total player count of the whole proxy network.
⚠️ Notes
- Every proxy node must use a unique
serverName - All proxy nodes must connect to the same Redis instance
- The plugin is disabled by default until
enabled: trueis set in the config
🔧 For Developers
MultiProxySync also provides a public API for plugin integrations.
If you want to use the API in your own plugin, please check the documentation on GitHub:
https://github.com/User-Time/MultiProxySync
💬 Feedback
If you run into any issues or have ideas for improvement, feedback is always welcome.
Ченджлог
2.2.0Релиз26.1, 26.1.1, 26.1.2 · 23 апреля 2026 г.
🚀 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
2.0.0Релиз26.1, 26.1.1, 26.1.2 · 12 апреля 2026 г.
🚀 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-apimultiproxysync-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 throughMultiProxySyncProvider, 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.
1.3.1Релиз26.1, 26.1.1, 26.1.2 · 10 апреля 2026 г.
🚀 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).
1.0.0Релиз26.1, 26.1.1, 26.1.2 · 16 марта 2026 г.
🚀 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.
Комментарии
Загружаем…