DecoyBlocks
DecoyBlocks ALPHA is a plugin designed to catch and appropriately deal with griefers automatically.
Originally conceived of by FlamingArmour in a request thread; this plugin allows you to specify certain blocks called "decoys" that, when broken, trigger a logging system for automatically catching and dealing with griefers.
Code was written from scratch by me, with some help from the community on file serialization.
Features!
Quote:
- Persistant storage of specified decoy blocks.
- Full logging of who broke which decoy, and when.
- Fully configureable automatic detention and / or punishment of people who have broken decoys.
- 3 Punishment thresholds, completely configureable.
- Punishments currently comprise of:
- Kill - Instantly deals the offender 9001 damage.
- Jail - Teleports the offender to the specified location. (Set via coordinates in config.)
- Kick - Instantly kicks the offender from the server.
- Ban - Instantly bans the offender from the server.
- IPBan - Instantly bans the offender and associated IP-Address.
- CraftBukkitUpToDate compatibility.
- Anonymous statistic reporting to mcstats.org!
Commands & Permissions
Decoys are set and removed by right-clicking the block with a stick.
- /db decoys - Gives you a list of all the decoys on this server.
- decoyblocks.decoy - Required to use /db decoys and to set or remove decoys.
- /db log - Enables you to see a block's log by placing a log block. Use again to disable.
- /db log all - Displays all log entries, in chronological order.
- decoyblocks.log - Required to use /db log.
- /db teleport <player> - Teleports you to the nearest open space by the last broken decoy (by the player, if specified).
- decoyblocks.teleport - Required to use /db teleport.
- /db <search / lookup> <player> - Gives you a list of all decoys broken by the specified player.
- decoyblocks.search - Required to use /db search or /db lookup.
- /db restore - Restores all decoys to their original state.
- decoyblocks.restore - Required to use /db restore.
- /db clear <log / decoys> - Completely clears out either the log or the decoys.
- decoyblocks.clear - Required to use /db clear. This is a dangerous command, and should be highly restricted.
- decoyblocks.clear.log - only allows access to /db clear log.
- /db save - Saves the decoys and log to their respective .dat files.
- decoyblocks.save - Required to use /db save.
- /db reload - Saves everything and reloads the config.
- decoyblocks.reload - Required to use /db reload.
Upcoming Features
- Ability to search an area for broken decoys.
- Ability to freeze players.
This plugin is now more or less inactive.
So, while I still would like to make a release version with that added, DecoyBlocks has been pushed to the back of all the stuff I'm doing. :/
mcstats shows only 3 active servers, which makes me sad. :(
@MRCartm0n
Thank you for being the first person in months to request anything.
I'll add that.
Is there a way to set a limit? I wanna give my players the ability to create such blocks but only a certain amount.
@Master_Zangetsu
Nope. You can do all group managements (& anything else) from the "Command=" punishment.
Also nope. For chests use LWC. (Why aren't you?!) For anything else, use BB / WorldGuard / LogBlock / HawkEye, or something.
any chance of adding a group migration punishment, so anyone that breaks the block gets moved to a pre configured group
also is it possible to add detection of other griefing such as TNT, lighting fires, and stealing from chests?
I am leaving for a week. Any needed updates will be made once I am back. (1st of April)
@bobbysmithyy
Umm... Pardon?
Okay
With any luck, v0.7 will be a BETA version! :D
@Fishrock123
Ah, thanks so much for the fix! I did suspect that it was DecoyBlocks, but I didn't have time to test anything, so I didn't file a bug report.
....You guys need to learn to report bugs.
@bobbysmithyy
Negative. If you want temp bans or time jailing you will have to use separate plugins and execute their commands from DecoyBlocks.
I will, however, improve the jail. Currently you can TP out of DB jail.
Temp bans?
@Fishrock123
Thanks and sweet!
@Kane_Hart
Yup! See the config page: http://dev.bukkit.org/server-mods/decoyblocks/pages/main/configuration/
You could set a punishment to, say;
- 2,command=ban %player% blah blah blah message
So long as it does not contain another '=' it should play nice. :)
Looks like a fun honeypot. Can I make it work with any ban program I want? Be nice if I could do something like /ban <name> flag flag flag message. Or whatever my ban plugin uses or has hehe.
@bigscary
Because there's already worldguard / hawkeye / guardian / etc?
Decoys are the things you put on likely points of grief to automatically ban/punish/etc people. You don't put this stuff on random blocks, you put it on high-target blocks that player's shouldn't mess with anyways.
The advantage is that this gives the server a chance of not just logging, but punishing the griefer without needing an op / admin / owner to manually do so.
It's mean to complement the other systems, not replace them.
Someone asked me for region support already, but I haven't gotten around to it yet.
Hi, I hope you won't be offended by my comments. I'm looking around at the different options for anti grief, and I don't quite understand the strategy here. It seems like a lot of work to do all the config to place these decoy blocks, and then isn't there a good chance that griefers will sort of randomly bypass them? And what about players who are just new to the game and don't realize the damage they're doing? Why not just block griefing by allowing players to draw boundaries around their builds with Residence or GriefPrevention, or have administrators do it with something like WorldGuard?
Is there a big advantage to this angle that I'm just not seeing? And could I potentially use this along with other popular anti grief tools?
Uploaded v0.4.1 - Fixes the command variables and some other related issues.