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).
I can't turn off the pvp protection for my arena world, i tried multiple times removing the world from the config but it keeps popping back.
Why does the config autoload worlds inside the config?
And how do i fully disable GP from enabling pvp protection.
I used this config and uploaded it to the server after a /stop
http://pastebin.com/deGb9HUN
When i started the server the config did this:
http://pastebin.com/Ri58iERk
@fungreenfox
Try sending the messages.yml via dropbox or some other service to me, and i'll try looking it over
@JacksonJacksonJackson
just use /ac then claim the area
if im hosting a server and i want to protect my spawn and stuff how can i increase my blocks that i can protect really fast????
@Tux2
Hey sorry i didn't get it the first time in case u forgot ever since the update I wasn't able to claim so plz help here's a link to my config for griefprevention http://paste.yu8.me/?4c595ed4f71fff84#edJJB5ycWJ5BcCFxC6qcOua3Fefz4jimTmJZ4vtj2s4=
@zlepper
I am using notepad. When i saw the file the first time, it was detected as encoded utf-8 with bom. But i still get english after a full replacement.
This has been working before, and i think its a line i have to add to the config, can you please confirm this.
Big problem here:
Using MCPC 1.4.7 Legacy 8 build and I cannot stop items such as quarries from going through protections. I'm using the 7.6.2 version of Griefprevention.
What builds are safe to use on 1.4.7 (waiting for FTB update) and What setting will stop quarries from digging in protected zones? this is a pretty big oversight for a comprehensive protection plugin... ([BuildCraft] is NOT opped.)
PLEASE help...grief is getting pretty bad now
I have an issue that no matter how often I change the settings like how many blocks acquire per hour or banning for spam or anything that's not the default setting it changes back to the settings of when I first installed the plugin :/ help!!
http://dev.bukkit.org/profiles/fungreenfox/
what are you using to edit the messages.yml notepad++ works fine, and it uses ANCI coding, so it can understand anything
Thanks! Maybe bind it to successful claim resize? Default chest claim may not mean complete claim knowledge.
Does this plugin block capital letters? If so is there a way to disable it?
@CrossfireLR99
/acb username -100 would remove 100 claim blocks.
How can I delete claim blocks from someone? So actually the opposite of /acb.
@zlepper
yes, it has to be regarding the version, or i have missed out something to type in config to make it use another messages.yml
Regarding the API, specificaly this bit:
testing permissions all these return null when a player DOES have permission they return an explanation message when a player DOES NOT have permission
What does that refer to? The allowX(player) methods? If so, it's a little confusing having them as returning a String, it would make more sense to add a canX(player) and return a boolean.
@fungreenfox
For the console yes, but vanilla minecraft contains the danish letters.
Og jeg har lige testet på min egen server, godt nok med en ældre version af GP, men der virker det fint, hvis jeg bare går ind og oversætter.
I have found forgotten spaces after text: and corrected it. But GP has just inserted the english version afterwards and using this. Did not delete the danish part this time, but its still in english ingame.
@zlepper
in order to use the danish letters , i need to convert to utf-8. But GP will tell in console if there is any error. its just that i got rid of those and its just converting anyway.
@fungreenfox
You most likely made an YML-error, most commom one is using TAB instead of 4 spaces
is there a way to disable PvP in protected areas except for when sieges are happening? Right now, even during siege people are unable to PvP
E.G. All players are protected inside their claims unless someone sieges them.
ok, do i have something set wrong? Default users, and vips, and ops do not generate more blocks to expand claim area? Do i need to set a perm? Seems to always stay at -189. Thanks
Using 7.6.3 for 1.4.7
Oh and weird but, now replaced dirt blocks never grow back to a grass block, but grass blades will grow on them, with top of it still dirt? Otherwise, seems to be working well! Thanks again for any help.