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!