EpicBans 🔨 Punishments System 2.4.0

EpicBans 2.4.0 is a major compatibility and infrastructure release. It adds new platform and integration support while substantially reworking the punishment, database, identity, notification, and migration layers introduced in previous releases. The main goals of 2.4.0 are safer multi-server consistency, stronger identity handling, better migration reliability and broader platform support.

Added

Sponge support

EpicBans now supports Sponge 8 through Sponge 11, covering Minecraft 1.15.2 through 1.20.6. Sponge versions older than 8 or newer than 11 are not targeted by EpicBans 2.4.0.

Geyser / Floodgate integration

Added native Bedrock-aware identity handling for servers and networks using Geyser and/or Floodgate. Supported detection modes: AUTO, FLOODGATE, GEYSER.

• Detects Bedrock players through the available Geyser/Floodgate API
• Stores and resolves Bedrock aliases without relying only on the username prefix
• Allows prefixless staff lookups for known Bedrock players
• Prioritizes exact usernames and UUIDs
• Refuses ambiguous prefixless aliases
• Can hide the configured Bedrock prefix in user-facing messages
• Safely reconciles aliases and legacy name-based data when the prefix changes

Persistent staff notification digests

The staff notification system has been reworked into a persistent, database-backed system. Notifications:
Enabled: true
DisplayMode: DIGEST
MaxEntriesPerLogin: 10
GroupSimilar: true
MarkAsReadAfterDisplay: true
OnJoin: true

• Unread administrative events can remain in the database
• Pending events can be displayed when authorized staff join
• Repeated actions involving the same player can be grouped
• Digest rows can be limited per login
• Overflow events are counted
• Events are marked as read only after successful display
• Digest messages are included in English, Italian, and French

/epicbans notify

Staff members with epicbans.notify can enable or disable their own EpicBans staff notifications. The preference is stored persistently and cached in memory. Simple Voice Chat integration Added optional native integration with Simple Voice Chat on Bukkit-family servers. Hook:
SimpleVoiceChat: true When enabled, these punishment types also prevent microphone transmission:

• MUTE
• TEMPMUTE
• IPMUTE
• TEMPIPMUTE

Removing or expiring the mute restores voice access without requiring the player to reconnect. Simple Voice Chat must be installed on the same Bukkit/Paper/Folia backend.

Database consistency controls

Added a database-backed consistency layer for multi-instance networks.

PreLoginFailurePolicy supports LAST_VALID_SNAPSHOT and DENY. EpicBans synchronizes revisioned punishment-cache changes through the shared database. Redis or another external messaging broker is not required. Staff UUID tracking Punishment and moderation records now support storing the staff UUID in addition to the staff name. This improves moderation-history attribution, staff history after username changes, warning displays, notification attribution, and rollback attribution. Existing schemas are migrated automatically.

Changed

Punishment engine rework

The internal punishment system has been substantially redesigned around a centralized service/repository model.

• Centralized PunishmentService
• Request/result objects for punishment and removal operations
• Immutable punishment/cache snapshots
• Cache deltas published after committed mutations
• Centralized player and punishment resolution
• Asynchronous database mutations with explicit completion results

The previous individual punishment implementations were consolidated behind the new service layer.

Multi-server punishment cache

Active punishments and registered-player identity data are now maintained in a revisioned cache. Local committed changes update the cache immediately, while other EpicBans instances discover newer revisions through the configured synchronization interval.

Database and migration layer

The database subsystem received one of the largest rewrites in EpicBans 2.4.0.

• Dedicated datastore implementations for H2, SQLite, MySQL, MariaDB, and PostgreSQL
• Centralized schema definitions
• Schema health validation
• Migration journaling
• Dedicated legacy, punishment, notification, Bedrock, staff-UUID, and consistency migrations
• Safer transaction/mutation coordination
• Database maintenance locking
• Improved recovery from older EpicBans schemas
• Updated SQLite JDBC driver

Migration work also addresses legacy UUID formats, duplicate/placeholder identities, missing columns, and schema differences between older database versions.

Database conversion

/epicbans convert <DATABASE> remains available, with a reworked conversion engine featuring target preflight checks, safer export/import handling, maintenance protection, improved error handling, and better target-connection cleanup. Supported targets remain H2, SQLite, MySQL, MariaDB, and PostgreSQL.

Player identity resolution

Player lookup and migration logic has been strengthened across names, UUIDs, IP addresses, legacy records, and Bedrock aliases. Dedicated verified/IP/legacy identity models reduce incorrect matches and improve old-data migration.

EpicBans API

The public API now follows the new punishment service lifecycle.

• EpicBansAPI.isAvailable()
• Asynchronous punishment operations returning CompletableFuture<PunishmentResult>
• Asynchronous removal operations returning CompletableFuture<RemovalResult>
• Asynchronous immunity updates
• Centralized player identity resolution

Examples include punishPlayerAsync(...), punishAsync(...), unPunishPlayerAsync(...), and setImmuneAsync(...). The older fire-and-forget punishment method remains for compatibility but is deprecated.

Discord integration

Discord handling was reorganized around a dedicated manager and received additional reliability fixes, including staff-channel delivery corrections.

Command permissions and tab completion

Command completion now takes the sender's permissions into account more consistently. The new notification subcommand, administrator-only subcommands, help output, and permissions output have all been aligned with the new behavior.

Fixed

• Database and SQL stability: SQL threading, callback execution, concurrent mutations, constraints, InnoDB handling, resource lifecycle, startup, migration ordering, and recovery
• UUID and legacy migrations: mismatched UUID formats, duplicate UUID records, placeholder identities, old rows missing newer fields, staff UUID migration, and repeated migration cases
• Rollback/history: additional legacy-data and identity edge cases, plus improved staff-name resolution through stored staff UUIDs
• Discord: staff-channel delivery issues
• Legacy Bukkit: message and color-code handling
• Tab completion: suggestions shown to users without the required permission
• Update checker: multiple update-checker edge cases and admin warnings
• /clearchat: silent-flag handling
• Paper/Bukkit detection: cases where Paper could be handled as unsupported
• Sponge: plugin-directory handling, player IP retrieval, database initialization, command completion, UUID handling, and startup errors

Upgrade notes

• Back up your EpicBans database
• Back up config.yml, templates.yml, message files and custom Discord configuration
• Replace the old EpicBans JAR with 2.4.0
• On a multi-server network, start one EpicBans instance first and allow migrations to complete before starting the remaining instances
• Review the new consistency, notification, Geyser/Floodgate, and Simple Voice Chat settings
• Verify the Bedrock username prefix before the first production startup if Geyser/Floodgate is used

Java requirement: Java 11+ Sponge compatibility: Sponge 8-11 / Minecraft 1.15.2-1.20.6 Short release notes Added

• Sponge 8-11 support
• Native Geyser/Floodgate Bedrock integration
• Bedrock alias and prefixless lookup handling
• Persistent staff notification digests
• /epicbans notify
• Simple Voice Chat mute enforcement on Bukkit/Paper/Folia
• Database-backed punishment-cache revision synchronization
• Configurable pre-login database failure policies
• Staff UUID tracking

Changed

• Rebuilt punishment engine around PunishmentService
• Reworked database/migration architecture across all five databases
• Reworked database conversion
• Improved UUID/name/IP identity resolution
• Improved multi-server consistency
• Updated the EpicBans API with asynchronous commit-aware operations
• Improved Discord and notification handling
• Improved permission-aware tab completion

Fixed

• SQL threading and callback issues
• UUID and legacy-schema migrations
• Database constraints and InnoDB handling
• Rollback/history edge cases
• Discord staff-channel delivery
• Legacy Bukkit message/color handling
• Tab completion permission issues
• Update-checker edge cases
• /clearchat silent handling
• Paper detection
• Multiple Sponge startup, command, IP, UUID, and database issues

EpicBans 2.3.0 is a major update bringing full moderation transparency, a powerful rollback system, IP history tracking, and a significantly improved database layer. Everything your staff team needs to moderate with confidence.

⚡ 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   
• 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

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 (e.g. server=Bedwars);
• 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

• 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.
  • Predefined punishment templates for faster and consistent moderation;
  • Configurable in templates.yml;
  • Full guide available here: Punishment Templates Wiki
  • Templates provide staff with quick access to predefined punishments (reason, duration, type).
• New Time Unit: Year
• 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.
• 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.

We are thrilled to announce the release of EpicBans 2.0.0! This is a major update, bringing new features, improved performance, and enhanced support across all platforms.

✨ What's New in 2.0.0

🌐 Cross-Platform & Compatibility

• Full support for Velocity, BungeeCord, Folia, and Paper/Spigot.
• Improved SQLite, H2, MariaDB, and PostgreSQL support with faster database access.
• Added UUID support for consistent player identification across servers.

🛡 Punishment System Improvements

• IPBan/IPMute offline players now fully supported.
• /check command shows detailed info: country, warns, and expiration dates.
• Improved warning expiration handling and punishment escalation.
• Automatic account/IP tracking when players join, including duplicate IP updates.

⚡ Performance & Reliability

• Database operations optimized for faster joins, chat events, and punishment logging.
• Tab-completion for commands fully fixed and updated.
• Plugin recoded to reduce memory footprint and improve speed.

🎛 Web & Discord Integration

• Fully integrated Discord notifications with customizable channels.
• Optional disabling of user punishment notifications while keeping staff notifications.
• Enhanced web panel support, now smoother and more user-friendly.

📝 Messages & UI

• Cleaned up all messages in console and chat, legacy & MiniMessage compatible.
• Default messages now include gradients and more readable formatting.
• All commands have improved tab-completion and case handling.

📖 Upgrade Notes

• Moving from 1.4.4 to 2.0.0 requires updating your config files. Default settings for drivers, databases, and Discord integration may need verification.

We highly recommend updating to EpicBans 2.0.0 to take advantage of all these improvements.

For full documentation, installation guides, and advanced configuration, visit the official EpicBans Wiki.

Thank you for using EpicBans — simple, reliable, and powerful punishment management!