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 Dec 23, 2014We just recently updated from 1.7.2 to 1.8 and everything works except that all worlds other than "world" the claims have been removed. We can confirm all of the worlds working in 1.7.2 however, upon multiple attempts to update to 1.8 all claims for alternate worlds seem to not exist. When launching the Spigot 1.8 server for the first time it start to convert playernames to UUID (Which I thought it had already done in 1.7.2). Could this possibly have something to do with all the claims being removed? We really would like to update to 1.8 however, we cannot do so until all claims are still available. Too many players rely on this plugin.
Is there something that can be done?
-
View User Profile
-
Send Message
Posted Dec 23, 2014@switorik
Alright, I'll work on that.
@PrimoHighDefinition
Yep, that's a client bug. I'm looking for a workaround, but there may not be one.
@MrHollick
You probably didn't give exactly the right permission. Permissions plugins are notoriously difficult to use correctly - please check the spelling of the permission you gave, and try using an in-game slash command to list all of the permissions that player has. Sorry for the trouble - an easy to use permissions plugin is sorely needed, but I've allocated all my free time already to my other projects. :\
@Pringui2
Confirmed armor stands are protected with the latest GP and latest Spigot. Please make sure you're on the latest for both, and that you're using the right output JAR from buildtools (there are many in there, and some are intermediate builds which don't work for all plugins).
-
View User Profile
-
Send Message
Posted Dec 23, 2014@bigscary
thanks :) i kind of had a feeling i should downgrade to the 1.7 build. works now!
-
View User Profile
-
Send Message
Posted Dec 23, 2014I added griefprevention.ignoreclaims to a players permissions but when they click in another players claim it just says they don't have the permissions to build in so and sos area. they don't get the you can override this with /ignoreClaims
Of course if i OP them it works just fine. Is it possible to just add the grief prevention.ignoreclaims permission to a normal player without Oping them so they can asset other people when they may need help?
-
View User Profile
-
Send Message
Posted Dec 23, 2014Got this when new chunks load with protection http://imgur.com/HeSlu3b no errors in console and fixed after reconnect, but annoy players
-
View User Profile
-
Send Message
Posted Dec 23, 2014AmorStands are not protected anymore with spigot builds #17 and #18 ! Thanks for updating so regularly :D !
-
View User Profile
-
Send Message
Posted Dec 23, 2014@bigscary
We use lava to destroy minecarts/boats for various reasons and mechanics. Now this seems to work in the nether, but in the normal world, they do not get destroyed. Boats/minecarts will fill up a lavapool and just sit there instead of burning.
In 7.8 it was an option called EnvironmentalVehicleDamage.
edit: Off-Topic: What happens to claims when the world they were in is removed? Do they get deleted or are they just stagnant? I know they don't count towards the players claimblocks, but I'm curious what happens to the file.
-
View User Profile
-
Send Message
Posted Dec 22, 2014@Perkulator_Time
The latest versions are for CraftBukkit or Spigot 1.8. You need to update your server, or use an older version of Grief Prevention. If you got your server bits from buildtools.jar, update your buildtools.jar and run it again - there used to be an issue with older versions of buildtools where users would often pick the wrong output JAR, and then many plugins wouldn't work. After updating and rerunning buildtools, be sure you're using a server jar from the top level folder (the one that has buildtools.jar itself). If you dig into the "target" folders, you may be grabbing the wrong server jar.
@flawlessbraz1
See setup/config page. You can set any world to "disabled" in the config file.
@MPigna
If your world is listed int he config under pvp worlds, then lava is allowed to be placed by other players. Check that list.
Similarly for player drops - those are not protected by default in pvp worlds. Either remove your world from the pvp worlds list, or enable drop protections for pvp worlds. Both are in the config.
@switorik
Sorry I don't understand what you mean by this? Please explain what you want to be different in more detail. :)
-
View User Profile
-
Send Message
Posted Dec 22, 2014@Perkulator_Time
ive got the same problem
-
View User Profile
-
Send Message
Posted Dec 20, 2014Players seem to be able to place lava on/near players. Can't find this in config. Read somthing on top here about other players not getting to pick up items from other players on death. How do i config this? Would be nice to add in survival.
Thanks! :)
-
View User Profile
-
Send Message
Posted Dec 20, 2014@Perkulator_Time
Same problem as you buddy..
-
View User Profile
-
Send Message
Posted Dec 19, 2014How do i disable claims per world?
-
View User Profile
-
Send Message
Posted Dec 19, 2014I dont get it, I put installed this plugin, the gold shovel doesnt do anything nor does "placing a chest"
-
View User Profile
-
Send Message
Posted Dec 19, 2014I would like to know if Environmental Vehicle damage can be brought back. We use this often on our server. If it isn't too hard I would really appreciate it.
I would like to thank you again on keeping this plugin up to date and being involved with us. I can't describe how much I appreciate a dev taking time to talk to the players.
-
View User Profile
-
Send Message
Posted Dec 19, 2014@ridddle
You make many very good points. I'll see what I can cook up to solve this very frustrating problem.
Claim limits are coming back.
@Cra2ytig3r
Thanks, I'll look at that as well. :)
-
View User Profile
-
Send Message
Posted Dec 19, 2014@bigscary
Oh and BTW, will you be re-adding claim limits or do you need more people complaining? Haha. :D
@Cra2ytig3r: Hey, neat stuff!
-
View User Profile
-
Send Message
Posted Dec 18, 2014@ridddle
For portals I use this a plugin called Direct Portals. Maybe an idea there to help.
-
View User Profile
-
Send Message
Posted Dec 18, 2014@bigscary
Putting a Netherrack block and air pocket would work I guess. Just make sure to go one block further in all directions (but down) and remove/replace lava. Lava pockets are rather common in Nether, if players get buried inside a mountain, there is a chance they will get rescued into an instant molten death trap. :)
Portals: Well, we decided to simply prevent Minecraft from doing a nice thing for players which is looking for open area to place the portal and we’re doing the most logical thing which is translating coordinates perfectly, 1:8. This also makes it so that players cannot get lost… vanilla can spawn a portal in a way that when you want to use it to return you can end up 1024 blocks away from your original portal.
This also means that we need to make an air pocket and remove that lava like I mentioned above. And I guess portal being placed inside of Nether’s mountain is much safer than out in the open… fewer Ghasts and lava streams forming. :)
Whenever player tries to open a portal that would end up in someone’s claim (that they don’t have permissions for), we place a sign into portal’s frame explaining what went wrong (sign has a colored name and we don’t drop a sign item when a sign like that is broken to prevent farming signs…). Investigation tool was rewired to provide info if portal can be opened in that spot or would it intersect someone’s claim to reduce guesswork.
What else… I guess we also allow people to manually build portals on the same x/z and different y to allow for fast vertical travel in their huge overworld tower.
One thing that threw a monkey wrench in our perfect math was 1.7 and its biggest portals. 23 by 23 in Nether is 168 Overworld blocks… which can fit many portals. To be honest I don’t have a perfect solution there. People who play with portal size and placement (multiple in 1 spot) were told to expect some erased portal frames here and there.
-
View User Profile
-
Send Message
Posted Dec 18, 2014@bigscary
Like a charm. TYVM :)
-
View User Profile
-
Send Message
Posted Dec 18, 2014@Duffa13
Nope, land claims are still protected even when surface explosions are allowed. If you don't have a plugin to repair the surface damage, though, your server will start to look like the surface of the moon (until you start repairing manually with GP's /RNF command, or something similar).
@TJW28
Nope, no perms. Did you remember to /reload after you updated?
@ridddle
About /trapped in the nether, what are your thoughts on this?
Maybe he's still "trapped", but less so than before, since he can build now?
About spammy messages... :)
Please do share your approach to portals. It's rising closer to the top of my todo list, and you could certainly save me some headache by sharing your experience there!
Sorry about all the breaks - I knew rolling back would bring out the pitchforks, but I just didn't think I could pull off forward fixes at the needed scale. The code had been refactored to the point of unrecognizability (to me anyway), the complaints were coming too fast to be answered effectively, and there were more than 700 open bug reports. When I sent a msg to Tux asking if they would welcome some help, I got a response same day along the lines of "oh thank god".