Velocity & BungeeCord
Set up ClothesPlus for cross-server skin synchronization on proxy networks.
Overview
ClothesPlus supports cross-server skin synchronization on Velocity and BungeeCord proxy networks. When a player changes their outfit on one server, the changes are reflected on all other servers in the network.
Requirements
- MySQL configured and shared across all backend servers (see MySQL Setup)
- ClothesPlusVelocity plugin installed on the proxy (for full sync)
- Same ClothesPlus version on all backend servers
Setup
1
Configure MySQL
Set up MySQL on all backend servers pointing to the same database. Follow the MySQL Setup guide.
2
Enable Velocity sync
In config.yml on each backend server:
```yaml config.yml velocity: enabled: true ```
3
Install proxy plugin
Place the ClothesPlusVelocity plugin JAR in your proxy's plugins folder.
Place ClothesPlusVelocity.jar in velocity/plugins/
Place ClothesPlusVelocity.jar in bungeecord/plugins/
4
Restart everything
- Restart your proxy
- Restart all backend servers
5
Test
- Join server A, equip an outfit
- Switch to server B
- Your outfit should persist across the server switch
How It Works
- Player equips overlays on a backend server
- The change is saved to the shared MySQL database
- The proxy plugin broadcasts the update to all connected servers
- Other backend servers fetch the updated skin data
- All players see the updated skin across the network
Skin resets (/clothes reset) are also synchronized across servers when Velocity sync is enabled.
Troubleshooting
- Verify all servers point to the same MySQL database
- Check that
velocity.enabled: trueis set on every backend server - Ensure the proxy plugin is installed and loaded (
/velocity pluginsor/bungee plugins) - Check console logs for MySQL connection errors
- The proxy plugin may not be installed — install ClothesPlusVelocity on your proxy
- MySQL connection may be intermittent — check connection pool settings