Documentation Index
Fetch the complete documentation index at: https://mintlify.com/lDEVinux/eaglercraft/llms.txt
Use this file to discover all available pages before exploring further.
EaglercraftBungee extends the standard BungeeCord console with Eaglercraft-specific commands for moderation and server management. These commands are typed directly into the EaglercraftBungee console window (the terminal opened by run.bat or run_unix.sh in java/bungee_command/).
Moderation Commands
Use these commands to manage username and IP bans. Bans are stored in bans.txt in the EaglercraftBungee directory and reload automatically when the file is saved on disk.
| Command | Description |
|---|
eag-ban <username> | Ban a specific username. |
eag-ban-regex <regex> | Ban all usernames matching a regular expression. The regex is matched against the username in lowercase. |
eag-ban-wildcard <pattern> | Ban usernames matching a wildcard pattern (e.g. *spam*, *grief, bad*). |
eag-ban-ip <ip> | Ban an IP address. Supports CIDR subnet notation (e.g. 192.168.0.0/8). |
eag-ban-ip <username> | Ban the IP of a currently connected player by their username. |
eag-unban <username> | Remove an existing username ban. |
eag-banned <username> | Check whether a given username is currently banned. |
eag-banlist | List all active bans. |
eag-reloadban | Manually reload bans.txt from disk. |
IP bans require a reverse proxy (e.g. NGINX) with forward_ip configured, otherwise EaglercraftBungee cannot determine the real client IP. See the server setup guide for proxy configuration details.
Rate Limiting Commands
EaglercraftBungee includes built-in DoS protection and configurable rate limiting. Rate limiting requires a reverse proxy with forward_ip configured; it is disabled by default without one.
| Command | Description |
|---|
eag-ratelimit reset | Reset the DoS protection state and clear all rate limit counters. |
config.yml under the ratelimit block.
Origin / Domain Commands
EaglercraftBungee can restrict which client origins (domains) are allowed to connect. These commands manage the local origin_blacklist.txt file, which reloads automatically when changes are detected.
| Command | Description |
|---|
domain <player> | View the origin domain of a currently connected player. |
block-domain <domain> | Add a domain (as a regular expression) to the local origin blacklist. |
block-domain-name <name> | Block a domain by name, adding it to the local blacklist. |
unblock-domain <domain> | Remove a domain from the local blacklist. |
EaglercraftBungee also maintains an automatically-updating global origin blacklist. You can disable it with enable_web_origin_blacklist: false in config.yml, or switch to a simple origin whitelist using origin_blacklist_use_simple_whitelist: true.
Standard BungeeCord Commands
All standard BungeeCord commands are available in EaglercraftBungee. The most commonly used are:
| Command | Permission | Description |
|---|
server <name> | bungeecord.command.server | Move a player to a named backend server. |
list | bungeecord.command.list | List all currently connected players. |
alert <message> | bungeecord.command.alert | Broadcast a message to all connected players. |
ip <player> | bungeecord.command.ip | Show the IP address of a connected player. |
reload | bungeecord.command.reload | Reload config.yml without restarting the proxy. |
end | bungeecord.command.end | Gracefully shut down EaglercraftBungee. |
Permissions
Command permissions are managed through the permissions block in config.yml. Operators defined there can use the corresponding BungeeCord commands in-game as well as from the console. Eaglercraft-specific eag-* commands are console-only and are not subject to the permissions system.
For a full guide on banning, origin filtering, and other moderation workflows, see the Moderation Guide.