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).
-
View User Profile
-
Send Message
Posted Jul 12, 2013@BC_Programming
I removed the commands from the config but they were readded on /gpreload. Also /gpreload doesn't give any feedback in chat but I can see it reloaded in console.
Would you consider adding transferclaims as it's own permission? I'd like one of my groups to claim random found unclaimed houses for their owners but not create admin claims.
-
View User Profile
-
Send Message
Posted Jul 12, 2013@BC_Programming
Thanks BC your input helps out a lot answering questions for the players I have on my server. I think what some players what to be able to sell their tamed horses that's why they are looking for add ownership. I really like the last idea of "additional riders" if that could be added.
-
View User Profile
-
Send Message
Posted Jul 12, 2013hey, can I somehow disable the commands for (default: everybody) because I want only to use some commands administrative purpuses (for example: /rnf, /rna )
-
View User Profile
-
Send Message
Posted Jul 12, 2013@deleted_9935739
The reason I'm not looking into that is because I cannot reproduce any of the reported behaviours, so "looking into a way to fix it" would pretty much just be me flailing around and changing random things until it is reported that one of the Random changes is a good thing.
As a side note, if you don't want players banned you could also remove the /ban from the bancommand config setting.
the /transferclaims command requires both griefprevention.adminclaims as well as griefprevention.transferclaims permissions.
-
View User Profile
-
Send Message
Posted Jul 12, 2013Could you please look into a way to stop spam protection from banning and kicking instead of using large numbers which doesn't seem to work? I had to turn off the spam feature completely and am now looking for other antispam plugins.
What is the permission node to use /transferclaims?
-
View User Profile
-
Send Message
Posted Jul 12, 2013@DQone
you can use /setclaimblocks
current and maximum values cannot be set with group permissions.
-
View User Profile
-
Send Message
Posted Jul 12, 2013BC_Programming, I think you missed my question..
Hi,
Using the adjust bonus claim blocks command seems to add blocks on to existing blocks that the player has. Is it possible to set the total for a user?
Or even better, is it possible to set the total (or maximum) via group permissions? i.e, Players will have 8000 blocks, VIPs will have 16000 blocks etc.
Thanks
-
View User Profile
-
Send Message
Posted Jul 12, 2013@2coolforu22
Change the settings in GriefPrevention.Rules.WoodenDoors
-
View User Profile
-
Send Message
Posted Jul 12, 2013GriefPrevention-126 how do you lock wood doors on claims ?
-
View User Profile
-
Send Message
Posted Jul 11, 2013I want this...
Claims.LockAllDoors: true
Where do I put it?
-
View User Profile
-
Send Message
Posted Jul 11, 2013@CaddoMan I didn't get involved with the project until after the 7.7 release. I Can however say that on Tux2's Server- which is perhaps ironically running GP 7.7, Ender Pearls require Access Trust at both the origin and target On the server.
I think this may have been a change made since the 7.7 release. It might be using Dev build #2:
http://build.yu8.me:8080/job/GriefPrevention/2/
Browsing the commit history that one seems to protect both the origin and destination.
Of course, my changes include a more powerful ability to configure on each side- also, if an enderpearl teleport is cancelled it doesn't use up the pearl, which I found annoying.
@gameofblocks
Well GP doesn't add a "ownership" framework, it's actually changes to bukkit that actually expose that, so I guess maybe previous versions of CraftBukkit weren't saving an Owner.
This actually might explain some of the exceptions and errors being reported which point to Tamed Horses that manage to not have an owner, which might be related to horses tamed in previous builds of Bukkit.
As for adding additional riders, I really don't see that happening because that would be a lot of work; lists of extra riders would have to be tracked per-entity, saved somewhere, etc. And that would undoubtedly cause all sorts of bugs that will need to be fixed.
This means that once a horse is tamed, it "belongs" to that other player. With appropriate trust on a claim you could tame a horse for yourself, too.
Another idea might be to make the "additional riders" not actually be a "per horse" setting but actually per player; that is, Players could have lists of players they trust, and then those players will be able to ride their horses.
-
View User Profile
-
Send Message
Posted Jul 11, 2013@fungreenfox
GriefPrevention only keeps claims for loaded worlds in memory. If nobody is in a world than only claims at spawn will be visible. Dynmap-GP probably expects GP to have all claims loaded at the start, since that is how 7.7 and earlier worked.
-
View User Profile
-
Send Message
Posted Jul 11, 2013@imaycon
A dev build for 1.6.2 can be found here.
-
View User Profile
-
Send Message
Posted Jul 11, 2013Update to version 1.6.2 please? Thanks.
-
View User Profile
-
Send Message
Posted Jul 11, 2013What is the permission to use /transferclaim?
-
View User Profile
-
Send Message
Posted Jul 11, 2013By latest update, users claims are still there, but not shown at dynmap. Dynmap 070 latest also. Still nothing. Its really wierd, i only see one single tiny claim at main world and nothing else, even a single one in the other 5 worlds. I will ticket error.
-
View User Profile
-
Send Message
Posted Jul 11, 2013Thanks for the update we can now mount horses anywhere!!! Two questions for you. First Can we add ownership of horses that were tamed before the update? If we dismount one now it will say onwer 0 when we try to mount in the admin claim. Also is there a command to add other riders to your horse? Thanks again for your help.
-
View User Profile
-
Send Message
Posted Jul 11, 2013Is it possible to prevent any PvP while in a owned plot? I've looked but I can't see an answer. I'd be neat to have people safe at home but while getting resources they're vulnerable. To go a step further, If someone starts PvP with a player & runs back into their plot, they're still able to be attacked for the 15 second cooldown that's used to the logoff protection.
-
View User Profile
-
Send Message
Posted Jul 11, 2013@BC_Programming
Thanks for the update BC can't wait for the new dev build.
-
View User Profile
-
Send Message
Posted Jul 11, 2013@BC_Programming
Thanks for your response. I am talking specifically about version 7.7 using bukkit 1.5.2 I have had multiple players on my server test it. They can 'teleport' into a players claim using an ender pearl when the config is set to EnderPearlIsRequireAccessTrust : true I assume you will defer this to the next release anyway.