Modules
Ban System
Template-based and free-form bans with a kick screen.
The ban system supports both predefined templates (with reason and duration) and free-form bans via /customban. The kick screen text is localized in messages-*.yml.
Configuration
BanSystem:
Enabled: true
Permission: "muteessentials.ban"
Templates:
1:
reason: "Hacking/Cheating"
duration: -1
display: "&c[1] &eHacking/Cheating &7(Permanent)"
2:
reason: "Griefing"
duration: 604800
display: "&c[2] &eGriefing &7(7 days)"| Key | Description |
|---|---|
Enabled | Master toggle. |
Templates | Map of template IDs to ban definitions. duration is in seconds, -1 for permanent. display is shown in GUI/list views. |
The admin GUI paginates templates (21 per page) and ships a ✎ Custom... button. The button prompts in chat for reason | duration (e.g. Hacking | 7d, Trolling | permanent). The duration parser accepts 1d, 12h, 30m, 15s, combinations like 1d12h, plain seconds, and permanent / perm / -1.
The kick screen text uses placeholders %REASON%, %DURATION%, %BANNER%, %DISCORD% and lives in messages-*.yml under BanSystem.KickMessage.
Commands
Permissions
| Node | Grants |
|---|---|
muteessentials.ban | All ban commands |
Notes
- Staff cannot ban players with equal or higher rank priority.
- Active bans are stored in
data.yml(underBannedPlayers), or in MySQL whenStorage.MySQL.Enabledis on.