
MultiProxySync
This plugin enables multiple proxy servers to display the actual total network player count across all server lists.
🚀 MultiProxySync 🚀
The ultimate synchronization solution for Velocity proxy networks.
📖 About
MultiProxySync is a high-performance Velocity plugin designed for distributed proxy networks.
By leveraging Redis as a lightning-fast caching database, this plugin synchronizes player counts and player lists across multiple proxy instances in real-time. It perfectly resolves the issue of inconsistent "ping" player counts in distributed server environments.
📷 Preview

✨ Features
- 🔄 Multi-Proxy Sync: Seamlessly synchronizes player data across multiple Velocity proxy instances.
- ⚡ Redis-Powered: Stable and high-speed data sharing via Redis.
- 📊 Accurate Statistics: Provides real-time, accurate totals for your entire network.
- 🪶 Lightweight Design: Optimized for low resource usage—performance is our priority.
- 🔧 Simple Configuration: Quick deployment—ready to use out of the box.
📦 Requirements
- Velocity Proxy Server
- Redis Database
📦 Installation & Setup
1. Installation
- Download the
MultiProxySync.jarfile. - Place the file into your Velocity
pluginsfolder. - Start the server once to generate the configuration file.
- Stop the server and edit the configuration as needed.
2. Configuration
Open the generated config.yml and enter your Redis credentials:
plugin:
serverName: Proxy-01 # Must be unique for each proxy instance
enabled: true # Set to true to enable the plugin
redis:
host: 127.0.0.1 # Redis host IP
port: 6379 # Redis port
password: YourPassword # Redis password
Save your changes and restart the server to activate the plugin.
❗ Important Notes
- Redis is required for this plugin to function.
- All proxy instances must be connected to the same Redis database.
- The plugin is disabled by default. Please ensure you have configured your database settings and set
enabled: truein the config before expecting it to run.
💬 Feedback & Support
If you encounter any issues or have suggestions, please feel free to open an issue on our GitHub Issues page.
