MaxBans 1.8


  • Filename
  • Uploaded by
  • Uploaded
    Jun 23, 2013
  • Size
    205.88 KB
  • Downloads
  • MD5

Supported Bukkit Versions

  • CB 1.5.2-R1.0
  • CB 1.5.1-R0.2
  • CB 1.4.7-R1.0



  • Tidied up kick messages
  • Added /unwarn command to undo the last warning to a player
  • Added language translation ability (Messages will be changed a lot!)
  • Removed some color code config (The options in old configs won't work due to the new message system, above. Just edit messages.yml to fix it)
  • Fixed a bug where using /ban on an IP address would cause other sync'ed servers to ban the username instead of the IP.
  • Added /immune command, allowing a player to be immune to ALL maxbans punishments. (You are a fool if you use this feature, not my fault if you screw yourself with it)


  • Fixed warnings with expirey of 0 being deleted
  • Added missing history expirey config option
  • Fix a NPE if there are no users from the given IP
  • Removed "Could not validate core", people think it's an error: it isn't.
  • Call actions in the main thread using the Syncer
  • Possible fix for concurrency issue with Syncer connections
  • A GeoIP link in /checkip to lookup the location of the IP easily
  • Throw away dead connections when broadcasting through SyncServer
  • Kick command now accepts IP addresses


  • Explicitly close connections more often
  • Sync: false by default
  • Probable fix for MySQL timeouts
  • Revamped database API
  • Split /checkban and /checkip commands. Checkip is now no longer useless, checkban no longer prints someones IP.
  • DynamicBan importer
  • Fixes for some importing and the autocompletion
  • Reasons now accept \n as a newline character
  • Fixed an issue where /dupeip'ing someone would delete IP info for the target
  • Auto-dupeip option in the config
  • Revamped warnings system - You will have to reconfigure these if you use them!
  • Warnings with expirey of 0 will never expire
  • Improved update checking


  • Improved error handling
  • Fixed issue with /checkban and rangebans
  • Code tidyup
  • Improved debugging
  • Use Synchronized for database writes instead (Safer)
  • Moved some writes to async
  • Stop Syncers before stopping the SyncServer
  • Additional debug info in /mbdebug
  • Support for silent /warn
  • Notify on boot if there is an update available (Configurable to be turned off)


  • Added alias for /mb (/maxbans)
  • Fixed unban NullPointerException when syncer disabled
  • Added rangebans. Usage: /rangeban, /unrangeban, /temprangeban
  • Added MaxBans whitelist... This allows whitelisting certian usernames so that IP bans will NOT affect them (Includes rangebans) Usage: /mbwhitelist
  • Fixed a bug with history loading backwards
  • /Checkban is now sexy
  • Massive amounts of extra useful data in /mbdebug. Also defaults to file output now.


WARNING THIS BUILD WILL REQUIRE A FEW MINUTES TO CONVERT YOUR OLD DATABASE'S FORMAT! It may be longer or shorter, depending on the size of your database!

  • Fixed mute history colours
  • Added /mbdebug
  • Tidied up commands
  • Tell lockdown bypassers the reason for the lockdown
  • Fixed /checkban reporting time in milliseconds for mutes
  • Reworked some inheritance areas of the API
  • Added tab autocompleter to most commands (Eg like vanilla commands have)
  • Added Syncer and SyncServer, this is for advanced users who want to use commands from webpages or have two servers or more.
  • Sync tutorial available here:
  • Added time to history command
  • History now accepts a name. E.g. /history NewGuy 10 reports the last 10 things to happen to NewGuy
  • Does anyone even read this, to be honest?
  • API method to convert lowercase usernames back to normal case usernames


  • Tidied up lockdown code
  • Possible fix for MySQL connection timeouts
  • Added appeal-message to config (You may need to regenerate your config to see it!)
  • Color code support for:
  • Lockdown messages
  • Appeal messages
  • All reason messages
  • Fixed a Permissions issue with lockdowns
  • Fixed a typo in plugin.yml's permissions (One of the seesilent nodes was meant to be seebroadcast)
  • Possible fix for SQLITE_BUSY on reload


  • Tweaked /checkban message to be clearer
  • Added configurable colours for kick messages
  • Fixed a blank space being added to some kick messages
  • Fixed escape sequence characters doubling up (Eg, one ' becomes '' after a reboot)
  • Added /checkban for players. Permission is maxbans.checkban.self
  • Added /mbexport mysql|sqlite commands. This lets you export your database to MySQL or SQLite. (No import yet.)
  • Added /history command
  • Added an alias for each command as /mb<command>. Example: /mbkick and /mbban are the same as /kick and /ban, just in case another plugin overrides these commands.
  • Fixed proxy IPs bypassing lockdown when kicking proxy IPs is enabled
  • Added missing permission check for /mbexport and /mbimport (Kiinda important)
  • Added permission nodes to plugin.yml
  • Gave OPs all maxbans permissions by default
  • Fixed a bug where failed unbans were announced as successful
  • Added maxbans.seesilent permission node, to see any silent commands given out.
  • Reworked unban command
  • Added maxbans.seebroadcast permission node (given to players by default!) to see normal ban messages (Not silent ones)
  • Fixed a possible issue were lockdown permission checks would come before a player was given permissions at all
  • Metrics tracking


  • Trim trailing spaces in reasons
  • Fix reason when none given and command was silent
  • Fix error when silently kicking with no reason
  • Added importer/exporter (Exporter untested) - Command is /mbimport and /mbexport.. Only works for "vanilla" at the moment.
  • Added DNS blacklisting (Looks up IPs on to see if the IP is a known proxy/spammer)
  • Fixed /ban command not printing the reason to the console
  • Added default reason config option in config


  • Fixed /mbreload command
  • MySQL support added
  • Ban command now accepts IP addresses
  • Improved duplicate IP performance
  • Highlight username or IP in notification message, depending on which one is banned


  • Initial Release