How to Set Up Global Bans Across a Network
Learn how to configure a global ban system that synchronizes punishments across all servers in your Minecraft network.
Why Global Bans Are Essential
If you ban a player on one server but they can still join others, your moderation is incomplete. Cheaters and rule-breakers will simply switch to a different sub-server. Global bans minecraft network setups enforce ensure that a single ban command removes a player from every server in your network simultaneously.
Choosing a Ban Plugin
Several plugins support network-wide bans. The most popular options:
- LiteBans: Stores all punishments in MySQL. Supports bans, mutes, warns, and kicks across all servers connected to the same database. Includes a web interface for viewing punishment history.
- AdvancedBan: Free alternative with MySQL support. Covers bans, mutes, and warns with cross-server sync.
- BanManager: Open-source, MySQL-backed, with a web UI and rollback features.
Setting Up LiteBans (Example)
Step 1: Install on Every Server
Place the LiteBans plugin jar in the plugins folder of every backend server and your proxy. Restart all servers.
Step 2: Configure the Database
Open plugins/LiteBans/config.yml on each server and set the MySQL connection:
storage:
method: mysql
mysql:
hostname: db.internal.example.com
port: 3306
database: litebans
username: mcnet
password: strong-password
Every server must connect to the same database. This is what makes global bans minecraft network-wide possible.
Step 3: Configure Sync
LiteBans uses either the proxy's plugin messaging channel or Redis to push ban notifications to all servers instantly. If you use Redis:
sync:
method: redis
redis:
host: redis.internal.example.com
port: 6379
password: your-redis-password
Without sync, bans are stored in the database immediately, but other servers might not enforce them until the player reconnects.
Ban Types
| Type | Effect | Scope |
|---|---|---|
| Ban | Player cannot join any server | Network-wide |
| IP Ban | Blocks all accounts from an IP | Network-wide |
| Mute | Player cannot chat on any server | Network-wide |
| Warn | Logged warning, optional auto-punishment | Network-wide |
| Kick | Removed from current server | Current server only |
Web Interface
LiteBans includes a web interface that reads directly from the database. Deploy it on a web server to let staff review punishment history, search by player name, and see ban reasons without logging into the game.
Best Practices
- Always include a reason with every ban. This helps staff review decisions later.
- Use temporary bans for first offenses and permanent bans for severe violations.
- Set up automatic escalation: for example, three warns trigger a temporary ban.
- Back up your ban database regularly. Losing your punishment history is a moderation nightmare.
Global bans minecraft network owners implement should work hand-in-hand with global chat moderation and synchronized permissions. A unified moderation system keeps your entire network safe with minimal staff effort.
See a polished network in action: Astroworld MC, IP play.astroworldmc.com, Java + Bedrock.