BanManager v5.6.0

Details

  • Filename
    BanManager.jar
  • Uploaded by
  • Uploaded
    Jul 4, 2015
  • Size
    2.46 MB
  • Downloads
    2,565
  • MD5
    478e3e9e280c3eb1bd228b68f89c91b7

Supported Bukkit Versions

  • CB 1.7.9-R0.2
  • 1.8.3

Changelog

IF UPDATING FROM V4 READ THESE UPDATE INSTRUCTIONS FIRST

For v5 major changes, please read the v5.0.0 change log.

  • Added optional geo ip lookup within /bminfo
    • Uses max mind geo lookup database, hence increase in jar size
    • Requires enabling in geoip.yml and permission bm.command.bminfo.geoip
  • Added ability to whitelist or blacklist countries, see geoip.yml for more info
    • Players with bm.exempt.country may bypass the restriction
  • Added [actor] to dwarn.notify
  • Ensure all syncing tasks close their underlying resources, fixes too many connections open issue
  • Removed online actor memory cache, fixes actor_id is null error
  • Fixed exemptions not being reloaded correctly on /bmreload
  • Fixed missing -t argument throwing an exception
  • Fixed new players not being added to offline autocomplete
  • Added post punishment created events for other plugins
  • Use new post events for broadcasting, ensures the broadcasts are only ran if the punishment is created
  • Fixed enabled not being checked for warning actions
  • Added pre and post hook event commands, see hooks in config.yml for more information
  • Added /addnoteall <player> <message> NOTE this creates a new table, therefore if you need a non-default table name, ensure you disable the external database before starting the server with this update to allow for the new config nodes to be created for you to modify
    • Requires bm.command.addnoteall permission
  • Added new warningActions syntax to allow for delays in seconds
    • E.g.
'1':
    - cmd: kick [player]
      delay: 10
    - cmd: ban [player] [reason]
  • Fixed warning exemption check
  • Added /tempwarn
    • Requires permission bm.command.tempwarn
    • NOTE For advanced MySQL users, expires column added on startup, ensure your mysql user has permission to alter the warnings table