HoneyPot
Honeypot - Honeypots (griefer traps)
Authors: Argomirr, andune, dog.big, BeastsMC
Supports 1.6.X and 1.7.X
A plugin that allows Op's to create so called "honeypots," traps to identify and take care of dishonest players. Using the /honeypot or /hp commands you can turn any block into a honeypot: if a griefer tries to break it, everyone online will be alerted and the violation will be logged so an admin can take action, and optionally, Honeypot can kick or ban said player automatically. The block will be replaced, the trap reset - ready to catch the next griefer before he knows it.
For example, you can place a little shrine with valuable blocks such as gold near your spawn, and turn them into honeypots. When a griefer logs in, sees nobody around and decides the shiny blocks on that shrine would look so much better in his house, he's already given himself away.
A few videos that demo Honeypot in action: Video 1 | Video 2
Can you add support for XYZ ban plugin?
No, I won't. Please read the author's note at the bottom of this page. However, I've made it really easy for you to do it yourself and contribute. Read about it here.
Features:
- Plug 'n play - just drop Honeypot.jar in your plugins directory, and you're good to go
- Identify and take care of dishonest players (almost) entirely automatically
- Very easy to use
- Full logging of honeypot violations
- Configurable via a .properties file
- Changeable ban and kick/info reason
- Supports MCBans, EasyBan, UltraBan, KiwiAdmin, vanilla bans and Permissions
- Supports points feature for advanced needs, read the link for more info
- PHP script for showing Honeypot ban logs online: link (courtesy of @jellehen)
How to install and configure
- To install Honeypot, drop Honeypot.jar into your plugins directory, and run the server once. The plugin will generate a new directory, plugins/Honeypot, where you can find the honeypot violation log (honeypot.log), the properties file (honeypot.properties) and a file used to store honeypot data (list.ncsv).
- Open honeypot.properties with your favorite text editor and make any changes you want, then run your server again.
- A little note: if you wish to enable the ban feature, set the kick feature to false. Note that you need to have MCBans installed in order for banning to work.
- Permission nodes for the Permissions plugin (2.7 and also PEX with compatibility core):
honeypot.break # Can the user destroy honeypots? honeypot.create # Can the user place honeypots using /honeypot?
- Congratulations, you've set up your honeypot! You can set up as many honeypots as you like, but keep in mind that this system was not designed to be used as an area protection plugin, so don't apply /hp to every block on your house. See How to use bellow.
How to use
You can now log in and use /honeypot or /hp (Op's only, at this time) to start the process of making a honeypot. You will now be prompted to right click a block with the tool you specified (default: wooden axe) to create a honeypot. You can select any block, but it's recommended you choose a shiny block - something a griefer would want to break - and make sure it doesn't look like an obvious trap. (A single diamond block in the middle of nowhere looks somewhat suspicious, don't you agree?) You can keep selecting blocks until you exit the honeypot creation process by entering the /honeypot or /hp command again. To destroy the honeypot, simply have any Op break it and the block will be dropped as normal.
One more thing: honeypot data will automatically be saved once the server stops, but you can also apply a manual save by using /honeypot save or /hp s to prevent data loss in case of a server crash.
Author's note (andune)
This plugin was originally written by Argomirr. Though his last post related to Honeypot was April 18, 2011, I found value in this plugin and so have kept it updated through newer Bukkit versions and have released it here for others to continue to enjoy as well. Some features have been added at my whim (such as banPoints and WorldEdit region support), but I am not accepting feature requests. If you want a new feature or some new ban plugin supported, please pull the source and write it yourself. Here's a brief guide showing how to add a ban plugin to Honeypot. I WILL NOT help you with coding issues. If you can't figure it out, keep trying/learning until you can, or just use the custom ban type.
Changelog
Source Code
And thanks to godsyn for the idea.
Hi, does Honeypot support subtracting points (via the point system), over a set period of time?
For example, if I had a point system, and I had a 5 point limit, and at some point someone (accidentally) broke a 3 point block. . . is there a way to set it so that they will have a point subtracted for every hour of online playing where they haven't broke a Honeypot block? Thanks in advance.
One more thing, if a person places back a Honeypot block (that they didn't mean to break), will that give their points back to them?
I mean that this does local bans, and I need global bans.
@don4of4
what do you mean?
Can you add global banning now?
@Andune Yes I have the most recent version and none of my users have that permission, so I'm not sure what is going on :/ But players do get banned for breaking them, but it seems overtime the honeypot seems to wear off?
@don4of4 No, but it would be pretty easy to add now that I've been in there monkeying with the mcbans code to add mcbans3 support (was originally written by someone else). I'll add it next version for mcbans3 for sure, mcbans2 I'll have to look at some more.
@CourtneyOnFire Are you using Honeypot 1.0+? (ie. most recent version) I have not seen this behavior myself. Looking at the code right now, a Honeypot is recorded by Location and saved that way, ie. the Location is Honeypotted, not the block itself, meaning no matter what happens with that block, the Location should always remain a Honeypot. The only exception is if you've mistakenly granted your users the "honeypot.break" permission, in which case they are allowed to break Honeypots and the act of "honeypot.break" person breaking a Honeypot block results in it being removed as well. Sounds like that might be your problem.
Oh, also on the region question, yes, that was part of my motivation for adding the recent point system is to eventually allow for a Honeypot region and have finer control over what kind of blocks inside that region result in Honeypot bans. Haven't look into this much yet, but most likely it would use WorldEdit regions if I implement this in the future.
I'm not sure why this is happening but on my server the Honeypots keep resetting and people don't get banned for griefing them... some of them stay but others don't, any idea why?
We're running CB #1060
Also I have a suggestion, could you make it so you could select a whole area like you do with worldedit and be able to set all the bocks within the region to honeypots?
Has global ban support been added?
To those using MCBans3: support was added in 1.0.0 and it turns out it was working fine. However, Honeypot was NOT properly reporting that it was using MCbans3 on startup, it mistakenly said "Using vanilla". v1.0.1 fixes this issue.
@ivals Alright the points feature is now documented, read http://dev.bukkit.org/server-mods/honeypot/pages/points/ for more info.
@jgeboski the URL is listed under 'repository' tab, which should be consistent for all Bukkit projects you find.
@ivals well, truth is I didn't feel like writing up documentation for a feature I didn't know if anyone but me would use. Now that someone's called me on it, I guess I better go write the documentation. :) I'll post a page on it here soon and link it in the description.
Where can the source for this be found? I see in the facts section it's under the "Apache License version 2.0".
"added support for "ban points", an advanced form of the offenseCount algorithm. Read documentation for more details."
What documentation? I can't find it.
@godgodgodgo Issue tracker has been enabled, thanks for asking. Please post a ticket there. Regarding MCBans3, I haven't updated myself so I didn't get a chance to test it, it's possible there's a bug in the detection code. I'll look at it more later when I can install MCBans3 on my test server and try it out (possibly tonight).
@TTSDA This feature already exists, I added it a few days ago, unfortunately the web-site documentation here needs some work, we'll get it updated soon. Add "offenseCount=3" to your honeypot.properties and it will now require they break 3 blocks before they are Honeypot banned. Additionally, it will rollback the Honeypot damage they did automatically. This was added in v0.8, read the Changelog notes here: http://dev.bukkit.org/server-mods/honeypot/pages/changelog/
There is also more advanced functionality I added just last night where you can ban based on "offensePoints", which by default works the same as offenseCount (since every block is by default worth 1 point), but it allows you to assign weighting. So for example, those diamond and gold blocks might be worth 3 points (and if offensePoints is 3, that's instaban) whereas the wood blocks in your honeypot structure are only worth the default 1 point, meaning they have to break 3 of them to get the boot. I really did this as a step along the way to allowing you to Honeypot a cuboid/region (ala WorldGuard), so that you can weight the honeypot blocks appropriately (maybe dirt is worth 0 points, etc).
Hi ! Great Plugin, but I think it is too harsh on the players, it doesn't give a second chance, so I think it would be good if we could protect, for example, a house using honeypot, and the player can remove 3 blocks, once he removes the 4th he gets global banned.
If the player only removes 3 he gets kicked after a pre-set time (2 minutes after stopping to destroy the honeypot) and the items are restored.
This request might be too hard to accomplish, but it would make the plugin much better, IMO.
I can't post issues? Add an issues page please. HoneyPot isn't finding the stable version of McBans 3
New file posted, it'll be available as soon as dev.bukkit admins approve it. Includes initial (untested) McBans3 support, please let me know if you have issues with it. Full Changelog here:
http://dev.bukkit.org/server-mods/honeypot/pages/changelog/
@andune
Ok... Is it open source?
@don4of4
Wasn't planning to any time soon, but I did take a look at it and I have it half-coded already. Busy day ahead, won't promise anything.
@andune
Can you quickly patch it? Hooking ban and kick really shouldn't be too painful.