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).
@weggaz
In a survival world, this behavior is to be expected.
@MCDerpTurtle
This option is available only in creative mode at the moment. Think of it this way: a player builds something without claiming it. A player comes along, claims it, and then abandons the claim. That person's build would now be totally gone with no trace of who did it.
@gamen11
That was changed in the newer versions of GriefPrevention. Are the worlds where you want creative rules applied in the creative section of the config? Have you configured the creative options in the config to match the behavior of what you what?
@Uberjovial5
Make sure the version of GriefPrevention you are using matches your Bukkit version!
@elirock12
I'm having this problem too!
In creative worlds, players can't build in the wilderness, because allowing them to do so would allow them to make a huge mess. So they must use the golden shovel to claim a limited area, and build within that. If they're stupid enough to actually build something ugly or offensive within their limited area, they'll be totally busted because it's impossible for them to delete or move the claim. :)
Nope they can unclaim and then the grief is still there.....
And why can users NOT drop items in creative? + why dont the buildings go away when u unclaim?
Hey, how does nature automatically restore? I don't mean by using the Golden Shovel. I mean, is there a way in this plugin for nature to AUTOMATICALLY RESTORE when a claim is unclaimed. Do you absolutely have to use the golden shovel and type /restorenature for nature to be restored????
Hi and thanks for a good plugin...
We have a BIG problem with the claim part. No errors or so, and the most works...
Problems are:
1. When a users unclaim a claim, the building is still left were the claim was? 2. When u do /abandonclaim the builds are not/ restored back to natuere?
We need help!! We use latest bukkit 1.5.1 and the latest version of GriefPrevention
The whole idea with using this plugin is for us to defend the wild from uggly grief
/Best regards
WZ
I find a issue that player can use bow to open open other player 's chest, it is a bug ? Or how can I fix this issue ?
@Simo389
Which plugin are you using for sponges? Please notify the author of the plugin as this isn't sonething we can prevent if they don't use the correct priority.
@Simo389
Wait, how could a user get trapped in their own claim? Couldn't they have just dug themselves out since they have permission to build/break blocks?
@elirock12
Paste it here: http://paste.yu8.me and send me the link.
@Tux2
Hey i posted a while ago about a problem with grief prevention, the gold shovel claim thing doesnt work i tried to post the config but it was all wierd i cant post it normal here but i can show u how it is if i have an email please reply and love this plugin :D
can you add permission for transferclaim?
Do you know if this is a bug or if I am doing something wrong here? It seems to work when using files to store claims but not when I try using a mysql db. http://pastebin.com/7bGb4bui
Oh forgot to mention, it says GriefPrevention.instance.dataStore is null!
Also forgot: on your latest build #19
@Tux2
Now, i'm using 5.5.1 for tekkit, and i just got my stuff together, and made a creative world, now i have been testing, and while mostly everything works, then i can't abandon claims again, i can only use /deleteclaim, which doesn't clear the claim, or give back the claim block, like /abandonclaim should. Is this a bug with the old version, or do you have any other idea, why this happens?
And no, i don't have any error log
@Fastidious
That's interesting... I'll have to take a look.
@Nentify
That might be a bug. Does it do async and sync tasks correctly in that mod?
@Absolutionmc
I saw and I fixed. Check your PMs. :)
@Mre30
I'll see what I can do. Look for a ticket with that feature request and upvote it. If it's not requested add a feature request.
@RustyDagger
Not yet.
@Tux2
Is there any way to Enable the Snow Golem's to actually place snow where they walk?
One small request, that I think is really neat,
Ability to add groups or special permmision node for trust.
Example
I made a Donators Club in spawn. I would like to /sc it and then /trust g:donators. Then I would add the perm griefprevention.trustgroup.donators or something like that.
Bad idea?
Edit: Thanks, also, I donated hehe thanks for helping me out with the lag
Check my pm tux2. Apparently there was a bug with player claims where the claims are lost and aren't working properly.
Players don't seem to be getting claim blocks over time, I've set it to give users 10 blocks per hour?
GP v7.6.2 MCPC+ L7 (MC 1.4.7)
Tux2 - Amazing plugin! I have one tiny query that's confusing the heck out of me. Initial allocation of blocks, I can see the option in the config.yml (InitialBlocks: 100) but when I alter it players always start with 124 block allocations - even though I've set it at 500+ and restarted the server. I've tried removing both playerdata and claimdata folders to see if that helped but no joy. Any suggestions?
Strange that is doesn't even start with 100 as it's the default but goes to 124
@steve0145
Just remove the playerdata and claimdata folders.
@slamsape
Because of the multitude of portal plugins this would have to be something either they develop, or a plugin can choose to do, as it has nothing to do with actually griefing a claim. Also, portal use isn't well defined as portal plugins just use the player teleport command, which is indistinguishable from other teleports without hooking into their api.
@UKZzHELLRAISER
Piston pushing could be used quite easily to grief, so unfortunately no.
anyway to make it so portals on claimed land cannot be used without the owner permission?
my server has divine rpg which has a lot of dimensions. and instead of making their own and doing the work there are a lot of people freeloading off easy to access portals. and the owners of those portals are refusing to enclose their portals rooms to only they can access them.
so i was hoping being able to set it to default that portals on claimed land must be given permission for use. (and for it to work with portals from mods as well)
ALSO. we need a way to prevent people from making claims on worldguard protected regions. right now they can place claims down in those regions, but thank god they cant build or destroy in those claims.
Is there anyway I can get all the old claims removed with a command. I turned off my server for about a month and now that its back online its been over a month of it running and the old claims are not being removed. If there is any way i can do this with out deleting the files that would be great.