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 Jan 18, 2014NoSurvivalBuildingOutsideClaims doesn't exist in 7.8 and when added in the appropriate place in the config.yml the entry is subsequently removed upon next server start. It's easily replaced by BlockPlacement and BlockBreaking, however, the message players used to get that "you need to claim land before building http://howtoclaimurl" is gone.
-
View User Profile
-
Send Message
Posted Jan 17, 2014@stgram
Can confirm this, item frame drops their items.
-
View User Profile
-
Send Message
Posted Jan 17, 2014Ender pearls thrown at item frames cause the item to fall on teleport. Other actions with bow-arrow/whatever are properly protected and require Build permission.
-
View User Profile
-
Send Message
Posted Jan 17, 2014@BC_Programming
-
View User Profile
-
Send Message
Posted Jan 17, 2014@diannetea
My problem with doors not being locked by default is 1. iron doors are ugly, and 2. it should be left up to the server owner what can and cannot be locked. Since you're >changing everything to be more configurable, why is this not?
Options need to have reasonable defaults. The GriefPrevention.Rules.WoodenDoors, GriefPrevention.Rules.TrapDoors, and GriefPrevention.Rules.FenceGates van be adjusted in the world configuration, and they default to the values that correspond to the defaults in 7.7. It's already configurable. You're arguing that a default should be changed. A default that very few people have had a problem with so far, that has some sound logic behind it, and that has existed for nearly 4 years. "iron doors are ugly" isn't really that convincing, and the second one is already true. It is up to them.
@JustisR
If a player does not have the permission the message is not displayed. If it is, you are using an older build.
@iampyrex
Is there plans to release 7.8 for 1.5.2, or even 1.4.7(I know this is a stretch). The recent changes are absolutely outstanding.
Thanks, always means a lot when folks are happy with things. There is no set "plan" but there is a loose attempt to try to keep things compatible with previous versions, as well as some logic to determine the version of Minecraft the plugin is running under. eg right now it is used to make sure certain Materials are only ever used in 1.7 since they only exist there; and Horse-logic is wrapped so that the plugin doesn't try to access stuff that isn't available, so it <should> work in 1.5.2 as it is, and perhaps even 1.4.7. It's usually just a case of adding in a proper condition to check for a version before doing something version specific now, so the only issue is that I currently only test with 1.6.4 and 1.7 so things that won't work with 1.5 (or 1.4.7) may leak through.
-
View User Profile
-
Send Message
Posted Jan 16, 2014@BC_Programming
Im definately using one GP.jar and latest builds. From time to time using latest from your DEV page.
Thi smorning i used
Build #247 (Jan 16, 2014 2:06:05 PM)
and got this. Please tell me that claims are ok. With older i had infos about "cant read claims" but what this means?
http://pastebin.com/7Re6LfG8
thanks :)
EDIT: Yup all those claims are dissapeared. World i completely ruined, griefe, destroyed etc. Now i need to find a way how to get claim locations back. Do you, please, have any advice how to get back all those claims??
I have backup of map, so thats not a bih deal, but i need claims.
Cheers !
-
View User Profile
-
Send Message
Posted Jan 16, 2014Is there a way to restrict players from claiming blocks that contain the end portals?
It's basically a race to see who can find all three and claim them up.
-
View User Profile
-
Send Message
Posted Jan 16, 2014@MrStools
Yes. In each world config file there is something that looks like this...
http://pastebin.com/MqpVyY8Q
I've provided the answers as to what needs to be changed to do what you've asked.
-
View User Profile
-
Send Message
Posted Jan 16, 2014@BC_Programming
My problem with doors not being locked by default is
1. iron doors are ugly, and
2. it should be left up to the server owner what can and cannot be locked. Since you're changing everything to be more configurable, why is this not?
-
View User Profile
-
Send Message
Posted Jan 16, 2014Is there a way to have the Land Claim function apply to one world only?
-
View User Profile
-
Send Message
Posted Jan 16, 2014this plugin crashed my PEX it only started to work once i removed all nodes.... FIX YOUR PERMS!!!!!!!!!!!
-
View User Profile
-
Send Message
Posted Jan 16, 2014@BC_Programming
I had taken that node away. It only prevents the player from using the shovel, for claiming, restore nature, admin claims. etc. They will not be able to use the shovel for claiming. But the message still spams them when they hold it.
-
View User Profile
-
Send Message
Posted Jan 16, 2014@BC_Programming
I am sorry that I haven't read through the 600+ pages of comments and ask something that has been answered.
Is there plans to release 7.8 for 1.5.2, or even 1.4.7(I know this is a stretch). The recent changes are absolutely outstanding.
pyRex Feed The Bees Gaming http://www.ftbees.com
-
View User Profile
-
Send Message
Posted Jan 16, 2014@ha11oga11o
It sounds like you still have the GP 7.7 jar installed too. if GriefPreventionData is being created each time, than GP 7.7 or earlier is loading with the server.
I forget Ryan's original rationale for Wooden doors (that was all the game had at the time) not being locked by default, but it was quite reasonable. I believe it was along the lines of requiring players to do at least some work (to get a Iron door) to protect their stuff conveniently. Since trapdoors and fences are equally cheap it applied to them as well.
I didn't quite understand why it's not a good idea. What you said that it's not possible, other guy who bought that subclaim could use it as his own.
It's a bad idea because fundamentally it's GP-RealEstate fiddling with the innards of GP's claim objects. Subclaims are assumed to be owned by the same player as the claim on which they are a subdivision of. Looking at it now, the Owner of subclaims isn't ever used or retrieved from the database at all, and retrieving the owner name of a subclaim will retrieve the name of the owner of the top level claim to which it is attached.
7.8 enforces subclaim integrity- a subclaim is always owned by the same player that owns a top level claim. Attempting to circumvent this with plugins like GP-Real-estate won't work, because a subclaim will always inherit the owner from it's parent.
is there going to be any fix or something related to this problem?
The only "problem" is effectively that subclaims are still using the same system that every single claim used to use pre 7.7 or so. That is, every claim was in a giant list and checked and compared when it wanted to be determined which claim was being looked at. Tux revised this to use a more elegant Mapping, where the claims that intersected a given chunk were indexed based on that chunk, such that most 'searches' were a direct hash lookup.
This was not however extended to looking at subclaims within a claim. Subclaims are not top-level claims, so they are not stored using this optimized technique- the assumption being that you aren't going to have enough subclaims to justify the more complex data structures (and management).
A standard claim lookup for a given location is:
Get the chunk it's in->Grab the list of claims intersecting that chunk-> look through the list, and see which claim the location is within the bounds of->return that claim.
The result is that the actual "search" is almost always going to just have to look through at most two claims, and if there is no claim in that chunk, it knows immediately.
With a subclaim, however, what happens is it finds the top level claim that the subclaims are in via this method, but has to inspect and compare every single subclaims coordinates, sequentially, to try to find which one the location is within. With a lot of subclaims you effectively get the same massive performance problems that older versions of GP had with the same number of top-level claims. @JustisR
if you deny them griefprevention.claims.toolcreate permission, that should prevent the golden shovel from displaying any messages.
-
View User Profile
-
Send Message
Posted Jan 16, 2014@JustisR
Change the tool that's used to resize claims from golden shovel to something else in the config?
The other option is to tell them to not use a golden shovel.. As an actual shovel it is worthless cause it breaks really fast. I guess that's why the GP devs thought it's be alright to use it as the default tool for resizing claims.
- Leo
-
View User Profile
-
Send Message
Posted Jan 15, 2014Hey, Thanks For Spending The Time Reading Through, And Helping Us Server Owners...
I need your help.
Half the players on my server are not allowed to use any grief prevention abilities. I took away all permissions.
But whenever those same people take out a golden shovel, they go "WF*" complaining to me that it's spamming them with useless messages. I've, of course, looked through the config... And the only way I've found to do this, is to disable it completely. For everyone. Which is not an option. So, I was hoping I had missed something, and that i might find some help here.
-
View User Profile
-
Send Message
Posted Jan 15, 2014@iampyrex
Yes, it's possible.
Located in the per world configuration files, you'll find a line that goes like this...
WarnWhenBuildingOutsideClaims: true
Change true to false, and you will no longer receive the warning.
-
View User Profile
-
Send Message
Posted Jan 15, 2014First off, kudos! Best plugin ever!
Now, I have players wanting a way to disabled the "building outside your claim warning" Is this currently possible? If not, can this be added?
pyRex
Feed The Bees Gaming http://www.ftbees.com
-
View User Profile
-
Send Message
Posted Jan 15, 2014Using the latest GP whats the config option for letting flowing water break torches out of claims?
-
View User Profile
-
Send Message
Posted Jan 15, 2014@BC_Programming
I didn't quite understand why it's not a good idea. What you said that it's not possible, other guy who bought that subclaim could use it as his own.
So... I understand what you are saying about queries etc. but the main thing: is there going to be any fix or something related to this problem? I don't think that it should create lag and that's why I see it as a bug. If you think that it's "just a feature" then you should restrict doing that much subclaims (which would be quite a shame).
Ah, and sorry. I meant Grief Prevention 7.7 (I said 1.6 because I ment in Minecraft 1.6 version).