Inactive [ADMN] BanHammer v2.0.2 Bans, kicks and records [1.3.1-R2.0]

Discussion in 'Inactive/Unsupported Plugins' started by grandwazir, Jun 26, 2011.

  1. Offline

    grandwazir

    [​IMG]

    BanHammer is a plugin that allows adminstrators and other trusted users to ban and kick players. The basic idea is to have a lightweight banning solution that includes all the features you help manage your server. Additionally the plugin stores all bans using the Bukkit persistance system, using permissions for all commands and is simple to configure.

    Features
    • Simple and easy to configure.
    • Supports permenant as well as temporary bans.
    • Custom configurable limits to prevent moderators banning for too long.
    • Ban offline and online players.
    • Player name matching when kicking or banning players (no need to type every letter)
    • Can broadcast notifications to other players.
    • Review previous bans of a player, even after they have expired.
    • Review recent bans to see what has been happening while you have been away.
    • Banned names are cached for quick logins.
    • Reload the banned name cache on command (useful if you alter the database outside the plugin)
    • Uses Bukkit persistence for data storage; you choose what is best for you.
    • Supports built in Bukkit permissions, operators have all commands by default.
    • Command help system, simply type /bh.
    Requirements
    • Bukkit Persistence needs to be configured in bukkit.yml
    • If using MySQL for Persistence, you need a MySQL database
    Installation

    Ensure you are using the latest recommended build.

    Before installing, you need to make sure you are running at least the latest recommended build for Bukkit. Support is only given for problems when using a recommended build. This does not mean that the plugin will not work on other versions of Bukkit, the likelihood is it will, but it is not supported.

    Getting BanHammer

    The best way to install BanHammer is to use the symbolic link to the latest version. This link always points to the latest version of BanHammer, so is safe to use in scripts or update plugins. Additionally you can to use the RSS feed provided by BukkitDev as this also includes a version changelog.

    Alternatively older versions are available as well, however they are not supported. If you are forced to use an older version for whatever reason, please let me know why by opening a issue on GitHub.

    Configuration
    1. Configure permissions if necessary.
    2. Optionally configure your ban limits (config.yml) and assign them to moderators.
    All documentation for BanHammer is available on the GitHub wiki, including example usage.

    Reporting issues

    If you encounter any problems using BanHammer, and you believe it is due to a bug in BanHammer, report the issue on the issue tracker. Please do not report issues in this thread as I will not see them as quickly as if you place them on the tracker.
     
    klarnet, PatrickFreed and fromgate like this.
  2. Offline

    C0R7

    Vary Nice plugin. Im going to use this for my server.
     
  3. Offline

    grandwazir

    Thanks! Let me know if you have any problems or feedback for the next version.
     
  4. Offline

    C0R7

    OK will do.

    I found on thing that you can change in the plugin. when you do /banhistory -a 123. i banned that name permanently for a test and what the history say the ban time is zero. i was wonder if it can be changed to permanently or something.

    EDIT by Moderator: merged posts, please use the edit button instead of double posting.
     
    Last edited by a moderator: May 17, 2016
  5. Offline

    grandwazir

    Should already say permanently. Let me check what is up.

    Just fixed it in the latest version. Download it again to solve the issue.
     
  6. Offline

    C0R7

    ok thanks. i can copy the log if you want.
     
  7. Offline

    grandwazir

    It is ok; I know where it went a bit wrong. Thanks for the feedback!
     
  8. Offline

    C0R7

    So you will add the fix to the next update that you make? Thanks for the reply so fast to.
     
  9. Offline

    grandwazir

    It is already updated. Just download it again.
     
  10. Offline

    C0R7

    oh ok thanks.
     
  11. Offline

    Jellp

    Could you add a option when an admin tries the give command, they will be banned for a amount of time? (The time banned could be changed?)
    Thanks!
     
  12. Offline

    OMGtehEPICNESSS

    @ Jellp Why would you want to ban an admin :D? And if you don't want Admins to have give commands, don't give them the permissions for it.

    b2t: nice plugin! This should actually get implemented into the vanilla :]
     
  13. Offline

    grandwazir

    Thanks OMG! I am going to update this hopefully this weekend to fix a few bugs and to update the command alias to make them easier to use.
     
  14. Offline

    Plague

    Update the plugin to latest recommended build and change the title accordingly.
    Failure to do so will result in this moving to INACTIVE section.
     
  15. Offline

    grandwazir

    There you go. The title just needed updating.
     
  16. Offline

    mikedjose

    What an excellent plugin. I prefer to keep my server from being weighed down by plugins which feature useless junk on the side. This is exactly what is called for. I have a question, though. Do you maybe plan on using permissions to check for access level hierarchy? I believe the latest version of Permissions 3.1.x supports custom variables.

    Failing all else, you could require a rank variable be set for a user or group. Banhammer could then check that the person calling the ban had a 'higher' rank (lower rank variable value) than the person being banned/kicked/pardoned. If the user calling the command has no rank (who must have permissions to use ban/kick/pardon), the person being banned/kicked/pardoned would also be required to have no rank AND not have the same command permission as what was being used on them.
     
  17. Offline

    grandwazir

    Thanks for the feedback! I aim to make all my plugins do one thing, but do it well. I am planning on adding weighted permissions so for example a mod can not kick an admin. I have not had a chance yet to look at the permissions API yet; I've been adding isolated chat to DimensionDoor instead.

    My basic plan is to have it so you would only be able to kick/ban people who are a lower rank than you.
     
  18. Offline

    Lynxdragon

    Yes! This would be EPIC! (The co-owner keeps kicking me for the lol's, im the owner. -_-)

    Any chance for separate permission nodes for Ban and Temp Ban?

    And a permission to define the max tempban time the person can give? eg. "banhammer.tempban.24" = Max temp ban of 24 hours that this person can dish out? Or a Max Temp Ban Option for certain groups, eg. "MaxTempBan=Mod:1d,Admin:3d,Owner:-1" would mean max ban for group mod is 1 day, admin is 3 days, and owner is unlimited.

    This is the one feature im really really searching for, and i know alot of other server owners care crying out for this feature too!

    Thanks for your time.
     
  19. Offline

    Brekkjern

    I support what Lynxdragon suggests. Would be a fantastic plugin if so.

    A warning system would be nice as well. Where you could warn a person with a reason and after a configurable amount of warnings, you get banned automatically. Would also like a setting to make the warnings fade, but not disappear. I want to be able to look up a players record to see what they have been warned for.

    I know this is probably more than what you aimed for, but that would be rather useful. This would become the definite ban plugin really.
     
  20. This is an amazing plugin... Better than the stock one that comes with essentials!
     
  21. Offline

    grandwazir

    This is already in the latest bit of code on GitHub and will be in the next version.

    Doing it by time would be handy but not practical that way I think due to how permissions works. I can't easily get a list of all the permissions someone has on a certain node (at least I don't think I can from looking looking at the API).

    If that isn't possible my plan instead would be to have tempban.long, tempban.medium, etc with long being 2 weeks for example and medium being one week. The lengths may be configurable if people need to tweak it.
     
  22. Offline

    kahlilnc

    So this plugin is very similar to mcbans? like the lookups and what not.
     
  23. Offline

    Stodo

    So I can't give other groups on my server ability to ban? This is only for admins? If no so... Where are the permissions nodes?
     
  24. Offline

    Lynxdragon

    Please read the post properly before posting idiot comments.
    Honestly you don't even bother to read the post in full, and you expect support?
     
  25. Offline

    grandwazir

    It is unnecessary to be rude like this. A polite referral to the first post is much better.

    The plugin has just been updated including a wealth of bug fixes. Updating is highly recommended.

    Although this release is mainly a bug fixing release I am aiming to release one next week which will include the features discussed in the posts above.


    EDIT by Moderator: merged posts, please use the edit button instead of double posting.
     
    Last edited by a moderator: May 17, 2016
    garrett2smart87 and datwerd like this.
  26. Offline

    The Wizard

    The plugin didn't made a config file, how can I use mysql instead of sqlite?
     
  27. Offline

    grandwazir

    You need to configure your bukkit.yml to use MySQL instead of Sqlite.
     
  28. Offline

    The Wizard

    Can you make it so you can write the database, table name, user, pass in a config file like most of the plugins?
     
  29. Offline

    MasterMeNL

    When I tempban a player for lets say 10 minutes and unban him after 3 minutes.
    I can not ban him again, I get the message "player is already banned" and there is nothing to pardon.
    I'm using the recommended build 953.
     
  30. Offline

    grandwazir

    No. The bukkit developers have given us a new system to store data with and it is currently the recommended way to do things.

    Think about when you need to change database details for whatever reason. Rather than change plugin configs for every plugin you have you do it in one place instead - much easier.

    I am aware of this bug and it will be fixed in the next version.

    EDIT by Moderator: merged posts, please use the edit button instead of double posting.
     
    Last edited by a moderator: May 17, 2016

Share This Page