Grief Prevention
AUTOMATICALLY PREVENTS ALL FORMS OF GRIEF, including build/break, theft, spam, fire, spawn camping, lava dumping, chat trolling, advertising and more, so you don't have to undo any damage after the fact. It even teaches players how to use it so you don't have to! No configuration or database required. Stop responding to grief and prevent it instead. Grief Prevention will solve your grief problems without requiring you to manage a roster of trained administrators, juggle 10 different anti-grief plugins, take away cool standard game features, publish a training manual / tutorial for players, or add explanatory signs to your world. You can also choose to integrate PvP elements into build design to finally get a PvP experience befitting a sandbox game about creative building.
Grief Prevention stops grief before it starts automatically without any effort from administrators, and with very little (self service) effort from players. Solve all your grief problems with a single download, no database, and no configuration step.
Got a question or found some random bug? Check the documentation!
Got a problem or bug you can reliably reproduce? Or a feature request? Report it on the issue tracker!
Also, you might be able to catch me/others on the #GriefPrevention IRC channel for help (please state your question and exercise patience if you use this option).
Downloads for older Minecraft Versions
You may also view recent update notes on Github
The Manual
Feature List
Yes, everything is customizable.
- No database or world backups required.
- Extremely efficient CPU / RAM usage.
- Land claims are easy to manage.
- Players create and manage their own land claims, so you don't have to do it for them.
- New players get automatic claims around their first chests so they're protected even if they don't know how to create land claims yet.
- Players who ask for help in chat get an instant link to a demonstration video.
- Resizing claims and creating new claims is done with ONLY the mouse, no slash commands (slash commands are also available).
- When a player appears to be building something nice outside his claim, he's warned and shown his claim boundaries.
- Claim boundaries are easy to see, and don't require any client-side mod installation.
- Extremely easy-to-remember, single-parameter slash commands for giving other players permissions.
- Claim subdivision and granular permissions are available to organize towns and cities. Watch this video.
- It's IMPOSSIBLE to grief a land claim. Watch this video.
- No building or breaking.
- No stealing from ANY containers.
- No sleeping in beds.
- No button/lever usage.
- No adjusting redstone repeaters or other configurable blocks.
- No pushing blocks in with pistons.
- No pulling blocks out with pistons.
- No TNT damage (including cannons).
- No creeper damage.
- No explosive damage from other plugins, like Extra Hard Mode or Magic Spells.
- No enderman/silverfish block changes.
- All doors may be automatically locked (optional, see config file).
- No killing or luring animals away.
- No stealing water (e.g. buckets).
- No trampling crops by players, animals, or monsters.
- No building overtop, all claims reach to the max build height.
- No placing or breaking paintings / item frames / armor stands, etc.
- Fluids will not flow into a claim from outside.
- No placing blocks via TNT/Sand/Gravel cannon.
- Pets and death loot are protected.
- Players can't pick up what another player dropped on death without permission.
- All types of pets are protected everywhere, even outside of land claims (can be configured per-world).
- Excellent anti-spam protection
- Warns, then mutes, then may kick or ban spammers (configurable - you choose).
- Most spammers get only one message out before they're muted.
- Blocks server advertising (IP addresses).
- Blocks repeat message spam.
- Blocks ASCII art (ex. Nyan Cats) spam.
- Blocks similar message spam.
- Blocks unreadable (gibberish) message spam.
- Blocks CAPS.
- Blocks macro spam (very different messages in quick succession).
- Blocks login/logout spam, even when the spammer has multiple accounts.
- Blocks death spam.
- Blocks bot team spam.
- Blocks slash command spam, including /tell, /emote, and any more you add.
- Wilderness Protection and Rollback
- Fire doesn't spread or destroy blocks.
- Creepers and other explosions don't destroy blocks above sea level.
- TNT doesn't destroy blocks above sea level.
- No planting trees on platforms in the sky ("tree grief").
- Instant, point and click nature restoration for not-claimed areas. Watch this video.
- Insanely easy and fast fixes for penises, swastikas, and anything else unsightly.
- Point at what you don't like and click, and it's fixed. Even from far away.
- Never accidentally changes blocks inside land claims.
- No need to investigate who built it, who broke it, or when they did it.
- Doesn't matter if the griefer built with "natural" blocks, it will still be fixed.
- No database.
- No backups.
- No chunk regeneration (it's dangerous for technical reasons).
- Fixes bad chunk generations, like floating islands. It will be better than new.
- Fills holes, even next to water to correct big spills.
- Smooths noisy terrain.
- No griefer construction is safe. If it's unnatural enough to be noticeable by players, it will be removed or filled-in.
- Land claims can't be used as a griefing tool.
- It's impossible to get a player "stuck" inside a land claim.
- Land claims beyond the first require a golden shovel.
- Minimum claim size prevents sprinkling small claims to annoy other players.
- Max claim allowance grows with time played on the server, and can't be cheated by idling.
- A simple administrative slash command will instantly remove all of a griefer's claims, no matter where they are.
- Catches clever griefers.
- Enhances the /ban command to ban ALL a griefer's accounts (not just his IP address).
- Logs sign placements.
- /SoftMute command to shut down chat trolls without them knowing they're beaten.
- Abridged chat logs make reviewing what happened while you were away super-quick and easy.
- Automatically mutes new-to-server players who use racial or homophobic slurs.
- PvP Protections.
- When PvP is off, no setting fire or dumping lava near other players.
- Absolutely bullet-proof anti-spawn-camping protection including bed respawns, which requires no configuration.
- No logging out, stashing items, or using plugin teleportation to escape combat.
- Optional siege mode, to answer players who hide in their claimed houses to avoid combat.
- Supports your server growth.
- Permit players to exchange server currency for claim blocks (requires configuration and other plugins).
- Grant claim blocks automatically for votes, donations, etc (console command provided, other plugins required).
Please Vote for Grief Prevention
I've also posted Grief Prevention on the Spigot site, where plugins are ranked based on reviews. If you love GP, please take a couple of minutes to give GP your rating and leave a short review. Better rating and positive reviews will help server owners who look for plugins on the Spigot site make the safe choice (GP) instead of downloading something sketchy or incomplete. :) Thanks so much for all your support!
http://www.spigotmc.org/resources/griefprevention.1884/
Got a question or found some random bug? Check the documentation!
Got a problem or bug you can reliably reproduce? Or a feature request? Report it on the issue tracker!
Also, you might be able to catch me/others on the #GriefPrevention IRC chat channel for help (please state your question and exercise patience if you use this option).
Added anti-treetop code. By default, trees now come down whole, and saplings automatically appear when a tree is finished off.
Any players who are intentionally eliminating a forest (or trying to move it) can remove the automatic saplings, so no harm done there.
Yes, your tree houses are safe. In fact, chopping a tree very close to anything that even vaguely resembles a player structure may result in a tree top. I'm thinking, better safe than sorry. Besides if you chop a tree near your house, you're probably not going to leave the tree top on purpose to ugly up your build.
Two new config variables reflecting these features:
If you have a strong opinion about tweaking this feature, please post. :)
Ok, i will choose to disable that feature for now, anyway I plan on promoting my server quite a bit tomorrow if you happen to get on. And whats next on the list?
@TylerIsTooPro
Unfortunately, it's not possible to reduce the amount of damage done to trees. :( I just learned that. So yeah, axes become less valuable, and I guess a determined griefer could remove your forest rather quickly with a stone or iron axe.
I don't see any way to balance this out, aside from what I just learned won't work. If anyone has any ideas, pleast post!
So are the trees just as hard to beat down as normally? Just wondering if it will negate the need for axes.
Documentation fully updated. :) Thanks all for your patience.
Based on the recent research in Bukkit docs and discussions in the Bukkit forum, I'm revising the tree top design a little. Because it's not possible to detect when a dropped sapling despawns or to reliably generate the correct seedling when a leaf block is programmatically destroyed, the new tree top solution will be very similar to other tree top plugins. Specifically:
Not a problem, I was just updating my server info page along with our permissions groups and wanted to be sure I had all the permissions and commands laid out properly for my users/admins
@Dracolix
What doesn't count the bonus blocks? When you equip your golden shovel, it tells you how many total blocks you have available for claiming land, and that number includes the bonus blocks.
Yes, an admin can give himself 100,000 bonus blocks if he wants. If you don't want to give that power to a particular administrator you don't trust with that feature, then just take away his permission for it. By default, only ops can use that command.
@mrcheesete0
The current features already have a true/false toggle. You can disable claims, spam protection, and newbie PvP immunity. I'll eventually add a config option to disable to fire protection.
As you mentioned, it's no longer necessary to edit the file to add claim blocks for a player, because we have /adjustbonusclaimblocks. The new file format has two lines for claim blocks - the first is how many have been accrued through online time, the second is the number of bonus blocks.
About the Multicraft thing, maybe. But it'll be low priority if at all.
Yes, I'm fully-updating that documentation tonight. Sorry for the delay, but my time has been short and I chose new features over updated docs the last few days.
Sorry for the DP but this is a separate subject.
it looks liek you’ve already started at http://dev.bukkit.org/server-mods/grief-prevention/pages/Administrative-Details/ but a nice commands and permissions list would be nice. when yo f inish with that page maybe at the end of it just listing the names of all the commands and the permissions, so I can see everything easily would be helpful.
Me again, Just curious if you could add in a true/false toggle for every feature? Such as the spam protection and all. I am mainly using this just to stop griefing by destroying other peoples’ houses, as we already have chest lock plugins (multiple because everybody on our server is used to a different plugin and won’t shut up unless I give them their plugin), but I don’t really have problems with spaming, and even if we do, I have a chat-logging plugin that I monitor daily (yes we are small enough I am able to do so XD) so I can warn them without using this plugin to do so.
SO maybe just make every feature toggle-able, so I can disable the spam but keep the grief prevention?
Another thing completely unnecessary but just curious and figured I should ask, is there any way to make all the configurable options in a file that shows up in my Config Files section of the Multicraft Panel? I know its possible because other plugins, (such as dynmap and deadbolt) place configurable files there, so that those admins I have who don’t have FTP access can still configure this as needed?
Just a side-note for anyone else by the way who in earlier pages were asking if there is a way to change the number of blocks a person can claim, there has been since the first version.
In your FTP files go GriefPreventionData>Users>(Username) and find the configuration file for that user, and on the first line it has a number, that is how many blocks you can claim, I have edited about half of my servers’ user files to bigger numbers, before the addbonusblocks was implemented.
EDIT: Just remembered he said something about there being a new way the files are stored, if it has changed this, I apologize, but I haven’t checked yet.
@bigscary
I figured as much.. just thought of it as a possible issue. Didn't really think it all the way through, but at least it was a possible issue. Also how are bonus claim blocks actually used? I doubt you even as an admin, could give yourself 5k or more bonus right? As I've tested it just as a trial, and it doesn't count the bonus blocks. Is there going to be a counter on the notification, to tell you the user how many extra blocks?
@Dracolix
As for seeing claims without checking blocks, I've been thinking on it. I just need to experiment a little and see what's possible and what isn't. I definitely want to do some kind of claims visualization if it's at all possible.
As for limits on claiming, I don't think it's necessary. The problem you describe, where a player takes a break and comes back to find nearby land is now claimed, is just a general minecraft multiplayer experience which can't be avoided, because when you're not playing, others may be building around you. Players can avoid this by building farther away from others, or by waiting until they have enough claim blocks for the build they have in mind, and claiming it all at once.
Using claims to grief intentionally is difficult because it takes a long time to get enough blocks to do any damage, and then your damage is very temporary and limited. Because each claim must be at least 10 blocks wide and at least 10 blocks long, circling another player's claim requires MANY more blocks than that player's claim itself. That means it will only work when you have vastly more claim blocks available than your victim, and griefers are all about doing max damage - they want to grief giant castles, not newbie houses. Further, suppose you manage to grief someone this way - now you're out of claim blocks, so you can't grief anyone else without un-griefing this victim, and you might not even have the blocks to protect your own build. In short, it's an extremely long way to go to grief someone using claims.
@TylerIsTooPro
It's already in. Use /adjustbonusclaimblocks <player> <amount>.
1.0 Updates! Please note... just because it's 1.0 doesn't mean it's out of beta. I just incremented the version number from 0.9.
Added PvP limits. Freshly joined and freshly respawned players can't participate in PvP until they pick up an item (should reduce camping).
Can disable PvP altogether. World-based PvP toggle will come later.
Note that poison splash potion still works (even versus "pvp immune" players), but isn't fatal. I'm looking for ways to fix that. Other spash potions are correctly blocked.
Also fixed a bug you may have noticed in your logs about blocks spreading.
Tree top code is next.
Noticed my own mistake.. it tells you the claim block amount. *feels stupid* >>
Suggestion not that it is very important but the ability to grant players more blocks as in the amount they are currently allowed to claim.
I've looked through all of the detailing you listed, and really find this to be an interesting protection plugin. Is there a way to find out details on say, how many blocks you can claim still? Along with listing possible bonus claim blocks you've gotten. Not to mention if there's a possible way, to see claims in the future aside from checking blocks?
Just seeing that as something useful, because people will eventually build quite expansively. Want to also keep limits on how fast someone claims. As a possibility of course, because someone could be building a huge area. Suddenly go afk / offline and come back, to find areas around them were claimed. Just as a possible griefing of course, because that can be a possibility.
Spent a bit of time thinking this over with others. Mostly for the sake of keeping our server content, because it would just be chaos otherwise.
@bigscary
I like the pvp free time for new players idea. Also what about admin protected areas such as spawn. In residence for example you can set a pvp flag on or off for claims. Less grief would occur if spawn cities etc have no pvp.
Added spam protection. Note new config variables. Details coming soon (probably tonight).
You'll need to delete your GriefPreventionData folder before starting this update, because I updated the file format for player data.
Hi scary I will probably be opening tonight or tomorrow. Thanks for your continued development :D
@burtthaman
Yeah I've already done some homework on that problem and I'll do some more before I release any code in that area. In some cases, the source is available so I can see what others tried and where they might have gone wrong.
I think you misunderstand about PvP limits. PvP will be either on or off for a world. When it's off, no PvP damage. When it's on, it's on everywhere. However if you want to be safe even before siege is implemented, all you have to do is build an iron door with a button. Because others can't use your button (because it's on your claim), no one will be able to get into your house to kill you (unless you leave other entrances open).
I'll consider a new player PvP-free time. I saw that on another server and liked it.