Mastering Network-Wide Player Bans with BungeeCord ProxyBan
Running a Minecraft server network means juggling multiple worlds, each with its own community and rules. When a troublemaker appears, you need a swift, consistent way to remove them from every connected server, not just one. That is where BungeeCord-ProxyBan steps in. This powerful plugin turns your proxy layer into a unified ban management hub, letting you enforce rules across your entire network with just a few commands. No more chasing griefers from lobby to survival to minigames.
What Exactly Is ProxyBan?
ProxyBan is a ban management system designed specifically for BungeeCord networks. Instead of installing separate ban plugins on each backend server, you place a single jar in your BungeeCord plugins folder. From that moment, every ban, unban, and reason applies globally. When a banned player attempts to connect, the proxy intercepts the login and disconnects them with a fully customizable message before they ever reach a game world. This saves server resources and keeps your moderation tidy.
Key Features That Make ProxyBan Stand Out
ProxyBan goes beyond a simple /ban command. Its flexibility lets you tailor punishments to your server’s culture. Here are the standout capabilities:
- Timed and permanent bans: Use durations like 1a (year), 2M (months), 3w (weeks), 4d (days), 5H (hours), 6m (minutes), or simply p for permanent. You can even combine them for precise control.
- Preconfigured ban templates: In the config.yml, you define ID-based reasons with preset durations. For example, “hacking” could be a permanent ban with a red warning, while “griefing” might be a 20-day timeout.
- Full color code support: Every reason message accepts the classic
&formatting, so your disconnect screen can match your server’s branding. - Dynamic unban date: Insert
%DATE%into any reason, and it automatically shows the exact moment the player can return. This reduces appeals and confusion. - Database-backed storage: Bans are saved in MySQL, making them persistent and shareable across multiple proxy instances if you scale up.
- Hot reloading: Edit the config or database settings and apply changes instantly with
/pbreload— no proxy restart required.
Installation Walkthrough
Setting up ProxyBan is straightforward, even if you are new to BungeeCord plugins. Follow these steps:
- Download the ProxyBan .jar file (ensure it matches your BungeeCord version).
- Place the jar into the plugins folder of your BungeeCord server.
- Start or restart the proxy. The plugin will generate a default config.yml inside the ProxyBan folder.
- Open config.yml and fill in your MySQL database credentials: host, port, database name, user, and password.
- Optionally, customize the BANS section with your own reason IDs, messages, and durations.
- Either restart the proxy or run
/pbreloadto connect to the database and activate your changes.
Many server administrators appreciate tools that simplify plugin management. A modern launcher like the one from foxygame.net can be a real time-saver here — it lets you browse, download, and install BungeeCord addons directly from its menu, so you can get ProxyBan up and running without manually hunting for jar files.
Command Reference for Daily Moderation
Once installed, your staff will rely on a handful of intuitive commands. Here is how each works:
- /pbban <username> [config ID] or [duration] [reason] — The core command. Use a predefined template ID like flying or 1, or specify a custom duration and reason on the fly. Remember, color codes need
&and you can include%DATE%. - /pbunban <username> — Lifts a ban immediately, allowing the player to rejoin the network.
- /pbconfig reload — Reloads only the config.yml, useful after tweaking ban templates without touching the database connection.
- /pbreload — Full reload of both config and database connection. Ideal when you change MySQL details.
Permission Nodes for Staff Roles
ProxyBan uses a simple permission system to control who can issue bans, unban, or reload settings. Assign these to your staff groups via a permissions plugin like LuckPerms:
- bcpb.ban — Grants access to
/pbban. - bcpb.unban — Allows the use of
/pbunban. - bcpb.config — Permits
/pbconfig reload. - bcpb.reload — Unlocks the full
/pbreloadcommand.
Distribute these carefully; giving reload permissions only to senior admins prevents accidental config wipes.
Deep Dive into config.yml
The heart of ProxyBan’s flexibility lies in its configuration file. Below is a typical setup with explanatory comments:
# database login information
DB:
host: 'localhost'
port: '3306'
database: 'proxyban'
user: 'root'
password: 'securepass'
# template ban reasons
BANS:
1:
reason: '&cHacking is not allowed on our server!'
time: '1a'
2:
reason: '&2Griefing is not allowed, keep that in mind when you return on %DATE%'
time: '20d'
flying:
reason: '&eFlying is not allowed on our server, you can return on %DATE%'
time: '2M'
Each entry under BANS gets a unique ID — it can be a number or a descriptive word like “flying”. The time field uses the same abbreviations as the command: a (years), M (months), w (weeks), d (days), H (hours), m (minutes), s (seconds), p (permanent). This structure lets you create dozens of ready-to-use punishment templates, ensuring consistency across your moderator team.
Why ProxyBan Beats Per-Server Ban Plugins
Without a proxy-level solution, you would need to sync ban lists manually or rely on complex database sharing between plugins. ProxyBan eliminates that headache. A single command propagates the ban instantly to all servers behind BungeeCord. Moreover, because the ban check happens at the connection stage, the player never loads any world, saving server RAM and CPU. For large networks with survival, creative, and minigame modes, this unified approach is a game changer.
Final Thoughts
BungeeCord-ProxyBan transforms network moderation from a scattered chore into a clean, centralized process. Its template system, timed bans, and color-coded disconnect messages give you full control over how you communicate with rule-breakers. The installation is painless, and the reload commands keep downtime to a minimum. Whether you run a small family-friendly network or a massive competitive hub, this plugin deserves a spot in your proxy’s plugins folder. Take the time to craft thoughtful ban reasons — they are often the last message a banned player sees, and a clear, firm note can prevent repeat offenses.