⚡ New Features

Moderation History
Every punishment action is now recorded in a persistent punishment_history table.

• New commands:
  • /history <player> [filter] - view the full sanction history of a player
  • /staffhistory <staff> [timeframe] - view all actions performed by a staff member
• History tracks: action type, target, UUID, IP, admin, reason, server, timestamp, and rollback status
• Automatic cleanup via the new TimeBeforeHistoryExpires config option (in days)

Rollback System
A new system to safely undo recent moderation actions, with explicit confirmation required.

• Three rollback modes:
  • /epicbans rollback staff <staff> <time>
  • /epicbans rollback player <player> <time>
  • /epicbans rollback global <time>
• Requires /epicbans confirm before executing
• New config options: OnlyConsoleCanRollback and TimeBeforeHistoryExpires

IP History

• New command: /iphistory <player> - view the full IP login history of a player
• IP records stored in a dedicated player_ip_history table
• Existing registered IPs are migrated automatically on first launch

Smarter IP Tracking
New options to avoid incorrect IP updates on auth and lobby networks:

• ip_save_on_auth - waits for AuthMe login before saving the IP (Bukkit/Spigot)
• save_ip_on_server_switch - saves IP only on server switch (BungeeCord/Velocity)
• ip_save_ignored_servers - list of servers excluded from IP tracking
• Added a dedicated Bukkit listener for AuthMe integration

Improvements

• Improved database layer across all five drivers (H2, MySQL, MariaDB, PostgreSQL, SQLite)
• Improved player registration and IP tracking logic
• Improved warning system with better history and rollback compatibility

Fixed

• Fixed several IPBan and IPMute edge cases in ban resolution and rollback
• Fixed obsolete immune table. Immunity is now a column in registered

This update focuses on important bug fixes affecting Bukkit and Bungee environments.

Fixes

• Fixed tab-complete handling on Bukkit and Bungee
  • Correct argument suggestions
  • Proper handling of dynamic completions (e.g. /unban)
  • Improved cross-platform consistency
• Hotfix for /warn on Bukkit
  • Resolved execution issue affecting warnings
• Fixed auto-silent issue on Bukkit
  • Console punishments no longer randomly apply auto-silent
  • More consistent punishment behavior

Docs & guides:
EpicBans Wiki

Update to 2.2.2 for improved stability and correct tab completion behavior.

What’s new

EpicBans 2.2.1 is a maintenance and quality-of-life update focused on better moderation feedback, more control over notifications, and important fixes to punishment commands.

⚡ New & Improved Features

Improved /banlist & /mutelist Output

• Added many new placeholders usable in config.yml
• New placeholders include %admin%, %date%, %duration%, and more
• Fully customizable list formats for clearer moderation logs

Punishment Notifications Control

• New options to enable/disable notifications when:
– A punished player joins the server
– A muted player attempts to chat
• New permissions to control who receives these notifications

Command Hotfixes

• Fixed issues with the reason handling in /ban and /mute commands
• More consistent and reliable punishment reasons

Improvements & Fixes

• General optimizations and internal fixes
• Improved moderation experience and stability

Docs & guides:
EpicBans Wiki

Update to 2.2.1 to get better control, clearer lists, and cleaner punishments.

What's New

EpicBans 2.2.0 is a special Christmas update bringing important improvements and powerful new features for a safer, more flexible, and more intuitive punishment system

⚡ New Features

Punishment Limits

• You can now define maximum durations for temporary punishments (tempban & tempmute) per staff group;
• Staff with epicbans.limits.unlimited are not restricted;
• Durations exceeding the limit can be automatically reduced or blocked, depending on the configuration (adjust_excessive_durations);
• Permanent punishments are now also restricted by group limits, unless the unlimited permission is present.

Flexible Duration Input

• Punishments now support both combined and separated formats:
  • Combined: 7d
  • Separated: 7 day
• Makes issuing temporary punishments faster and more intuitive.

Unified Punishment Commands

• /ban can now behave like /tempban when a duration is specified:
  • Example: /ban player 1d
• The same applies to:
  • /mute
  • /ipban
  • /ipmute
• Example: /ipban player 1 week
• This greatly simplifies command usage while keeping full compatibility.

Improved /warnings Output

• The result of the /warnings command has been significantly improved:
  • Full list of warnings;
  • Expiration time for each warning;
  • Staff member who issued each warning;
  • Additional useful details for moderation.
• Provides a much clearer and more informative overview.

ServerAdding in Broadcasts

• When punishing a player for a specific server, the ServerAdding message is now included in broadcasts;
• Can be enabled or disabled via config.

️ DupeIP OnlyIf Filter

• DupeIP checks on join can now trigger only under specific conditions:
  • BAN, MUTE, WARN, ONLINE, or ALWAYS
• Controlled via the new OnlyIf config key;
• Allows more precise and flexible dupe account detection.

Improvements & Fixes

• Fixed a minor bug when punishing players for a specific server;
• Better handling of silent punishments and cross-server messages;
• Improved banlist, mutelist, and warnlist handling;
• Minor bug fixes and performance optimizations.

Notes

• TemplateError has been moved to config.yml (no longer in messages_*.yml).

Update from 2.1.0 → 2.2.0 to enjoy this Christmas update and significantly improve your moderation workflow!

EpicBans Update 2.1.0

What's New

The EpicBans 2.1.0 update introduces major improvements, bug fixes, and new features designed to enhance both server performance and administrator experience.

✅ New Features

1. Developer API
   • A complete, developer-friendly API to interact with EpicBans programmatically;
   • Retrieve punishment lists, apply/remove punishments, and integrate with other plugins;
   • Manage bans, mutes, warns, and more via code;
   • See the EpicBans API Documentation for detailed usage examples.
   
   
2. Templates
   • Predefined punishment templates for faster and consistent moderation;
   • Configurable in templates.yml;
   • Full guide available here: Punishment Templates Wiki
   • Example:
   
   
   Code (YAML):

   templates :
     # Template for severe cheating violations
     Cheating : # Example: /ban Player @Cheating
       type : BAN # Permanent ban
       reason : "Unfair Advantage (Cheating)"
       time : 0 # Permanent ban (time is ignored for PERMANENT type)
       unit : seconds # Unit (ignored for permanent punishments)
       permission : "epicbans.template.cheating" # Required permission to use this template
       server : "*" # Applies to all servers
       isSilent : false # Broadcast the punishment
   
     # Template for temporary ban for toxicity
     Toxicity : # Example: /tempban Player @Toxicity
       type : TEMPBAN # Temporary ban
       reason : "Toxic Behavior (Harassment/Hate Speech)"
       time : 7 # Duration of punishment
       unit : days # Time unit
       permission : "epicbans.template.toxicity" # Required permission
       server : "*" # Applies to all servers
       isSilent : false # Broadcast the punishment
   
     # Template for spamming in chat
     Spam : # Example: /warn Player @Spam
       type : WARN # Temporary mute
       reason : "Chat Spam/Flood"
       time : 0 # Duration of punishment
       unit : seconds
       permission : "epicbans.template.spam" # Required permission
       server : "*" # Applies to all servers
       isSilent : true # Silent punishment (staff only)
   
     # Template for advertising violations
     Advertising : # Example: /tempban Player @Advertising
       type : TEMPBAN # Temporary ban
       reason : "Unauthorized Server Advertising"
       time : 30 # Duration of punishment
       unit : days # Time unit
       permission : "epicbans.template.advertising" # Required permission
       server : "*" # Applies to all servers
       isSilent : false # Broadcast the punishment
   • Templates provide staff with quick access to predefined punishments (reason, duration, type).
   
   
3. New Time Unit: Year
   
   
4. Silent Punishments Permission
   • Added the new permission:
   
   epicbans.silent
   
   • Required for staff to execute punishments silently (using the -s flag).
   • Without this permission, staff attempting to use silent punishments will receive the NoPerms message.
   
   
   
5. Automatic MiniMessage → Legacy Color Fallback
   • Messages now automatically detect and convert color codes when mixing MiniMessage and Legacy formatting;
   • Prevents display issues when both systems are used in the same message.

Bug Fixes

• Fixed a rare issue where server=... could incorrectly appear in the punishment reason when applying server-specific punishments.

⬆️ Upgrade to 2.1.0

Upgrade now to take advantage of:

• The new Developer API,
• Punishment Templates,
• Better time unit handling,
• The silent punishment permission system,
• And improved message compatibility.