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.
Dose this work on 1.8 ?
MCBans notifies me of a ban by user "[honeypot]" (Date Notified : 7/29/14)
MCBans logs the ban by user "[honeypot]" on server "survival.mineyc.com" (Date Ban Occured : 2011-07-31 3:57:19 pm)
No idea what this server is, but honeypot banned me from it.
Possible Bug?
I think honeypot should add a feature where people can add messages to the last part of the ban. Ex, mcbans global bans, adding a " - dispute @ mcbans.com" would be nice. :)
@OldScurvyDog
Thats because honeypot has not updated to use the new mcbans api :#
Actually it has, try updating mcbans and honeypot.
Honey pots just kicks players now, doesn't ban them since the update. This is the log message...
[02:52:12] [Server thread/INFO]: [Honeypot] Player Buddhist09 was caught breaking a honeypot block. [02:52:12] [Thread-34/WARN]: Exception in thread "Thread-34" [02:52:12] [Thread-34/WARN]: java.lang.NullPointerException [02:52:12] [Thread-34/WARN]: at com.mcbans.firestar.mcbans.request.Ban.run(Ban.java:114) [02:52:12] [Thread-34/WARN]: at java.lang.Thread.run(Unknown Source)
@andune The issue is that it does not seem to save any honeypot changes. Even if I use the hp tool on a block several times it will not mark it but instead tell over and over again that it just created it. This can be temporarily fixed by reloading the plugin manually (PlugMan). After that it works perfectly fine.
@Tallcraft
What are you reloading by hand on every restart? The whole plugin? Or setting up your Honeypot blocks? Make sure you are using /hp save after you've setup your Honeypot blocks.
If the plugin isn't loading, all I can say is it's running fine on at least two 1.7.4 servers I know of, plus the report below that it works fine on 1.7.4. So if it's not working for you, please open a ticket and include details about your environment: exactly what version of Bukkit you're using, what other plugins you're using and exactly what behavior you're seeing, including any relevant log files.
@hutt132
Same issue here, but I don't want to reload it by hand on every restart.
@OSTechGA
Thanks. If somebody find an issue, please feel free to open ticket http://dev.bukkit.org/bukkit-plugins/honeypot/tickets/
@hutt132
It is maybe Bukkit issue, open ticket w/ them :).
@hutt132
I have zero issues with this on 1.7.2. Working Great.
Plugin broke with 1.7.2. It doesn't create the honey blocks correctly and people don't get banned for breaking them. Was working fine in 1.6.4.
EDIT: Just realized I had to reload the plugin with PlugMan. Bukkit doesn't load some plugins properly with 1.7.2.
Worst plugin ever. I just tried to see if I could build and was autobanned.
Would you consider adding some logging to this plugin? I would love that if the player has done the offense once run X command. Then if the player does it again after coming off a kick or tempban run another command.
Basically I want to easily give them a second or third chance before I just straight up ban them. Thanks.
@Builder874
regarding global rollback on ban, yes, use the new custom ban type. It accepts multiple commands, so you could do something like:
Obviously replace the second line with whatever causes your logging system to issue rollbacks.
BTW, I'm not advocating this as a solution, I'd never do this myself. If you are setting up some new honeypots and you or a player accidentally trigger one while you're setting it up, it's obviously a much bigger deal to fix a mass-"oops"-rollback than it is to just unban someone, as in the default autoban case. But assuming you've thought through all that and think it's a good idea, that's how you'd do it.
@niels1189
auto reset when banned? This already exists. If you use the "original" Honeypot mode (1 block is instaban), then the block is never destroyed and there's nothing to reset.
If you use the point-blocks mode, where they are allowed to destroy blocks but if they go over a certain point threshold, they get banned, then immediately after the ban the blocks are rolled back. This is tracked internal to Honeypot and has no external dependencies (such as LogBlock or Prism or such) and last I checked it was still working fine.
If you're finding otherwise, feel free to setup a test scenario that I can reproduce that shows it not working and write it up as a ticket, upload your configuration and version information and I will take a look at it.
@BeastsMC
After creating Honeypots, you must issue an '/hp save' command to have them persisted. I have no idea why it was designed this way, it was part of the original design and I never bothered to change it. I suppose for marking up dozens or hundreds of blocks, it could have been more efficient than writing it out after every single update, but the file is really small and people don't edit Honeypot blocks all that often...
Anyway, if '/hp save' isn't working for you, you should be getting some sort of error in the server.log. If that is the case and the error seems to be Honeypot's fault (ie. your disk isn't full or it's not some other plugin causing an issue), feel free to open a ticket with all the information and logs you can provide to help troubleshoot the issue.
@SuperPyroManiac
There is no easy in-game way to remove a region. The regions are written out to the lists.ncsv file just like the original Honeypot blocks are. You can edit the file by hand to delete the regions you no longer want and then just issue an '/hp reload' in-game to reload the file.
Because this works well enough for me, I have no intention of adding an in-game way to manage regions beyond what's there today for their creation. If anyone is really inspired and motivated to have an in-game way to list and delete Honeypot regions, they are welcome to pull the source and write it up and send me a pull request.
Stored honeypots keep getting wiped and the plugin basically crashed/resets. No errors in console.
Is this still working on 1.6?