Synchronizing distributed Minecraft servers
Made with ♥ by Cerus and the Block Bind contributors
Block bind enables you to synchronize a bunch of independent Minecraft servers. Players can see each other and interact with one another regardless of which server they are playing on. This is a great solution for getting a bunch of players on one world: A single server would start to lag and / or crash very fast, but if you set up multiple servers and install Block Bind you will feel no lag at all.*
Block Bind is not a reverse proxy like BungeeCord.
We currently support Spigot 1.16.5 and Spigot 1.18.
* This has not been tested yet with many players and / or servers.
Block Bind utilizes the Pub/Sub functionality of Redis to communicate with other servers. Block Bind also uses the key value storage for temporary synchronized data.
We provide a Docker test environment that contains all dependencies and two 1.16.5 Spigot servers. Please take a look at blockbind/docker-testenv if you would like to check it out.
- (done in 1.0.0) Synchronize players (Movements, metadata etc)
- Synchronize block changes caused by players
- Synchronize block changes caused by other things
- Synchronize container transactions
- Synchronize other entities (Movements, metadata etc)
- Synchronize misc stuff (Chat messages for example)
Note: The roadmap is in no specific order.
Requirements
- At least two supported Minecraft servers
- A Redis server
- Java 16
- (Optional) Some sort of load balancer to distribute the amount of players on each server
Installation
- Install the corresponding implementation
- For Spigot servers: Drop the Bukkit plugin into the plugins folder of each server
- Restart the servers
- Edit the configs of the Block Bind implementation
- Restart your servers again