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 Sep 23, 2014@fafler
GriefPreventionFlags:
http://dev.bukkit.org/bukkit-plugins/gpflags/
Use the flag called AllowEntry.
-
View User Profile
-
Send Message
Posted Sep 23, 2014Hi, I'm wondering if there's a way to only allow players to use (Essentials) /sethome inside their own claims, or at least not inside other players claims? This has caused me and my players problems for years, but I've never found a solution.
-
View User Profile
-
Send Message
Posted Sep 23, 2014Everything looks really cool, but i'm missing one feature, to set teleport location for your claim. I now we can use /sethome, but creating public shops its really not cool :/
-
View User Profile
-
Send Message
Posted Sep 23, 2014@gnaxi
Thank you. I will not be updating just yet then! Where is the main issues list for griefprevention? Like a github issues page.
-
View User Profile
-
Send Message
Posted Sep 23, 2014After upgrading from dev 292 to 8.0.3 I am getting these errors in the console. I am using mySQL to store the player information.
Column count doesn't match value count at row 1
When making new claims, or re-sizing. After restarting the server de information from playerdata is removed, but the claim-data is preserved. Which essentially resets your total claim-blocks to the default value.
-
View User Profile
-
Send Message
Posted Sep 23, 2014@gnaxi
Same issue.
-
View User Profile
-
Send Message
Posted Sep 23, 2014This shows up for almost all claims:
"[INFO]: GriefPrevention: Failed to look up UUID for player [player name]"
So I guess almost all claims are now owned by administrator (me) and I have to manually go out and give them their claims back? Talk about automating something....
EDIT:
Every time I restart my server now, Griefprevention is acting weird.
First it gives me this:
[09:10:03 INFO]: GriefPrevention: Grief Prevention enabled.
[09:10:03 INFO]: GriefPrevention: Unable to retrieve schema version from database. Details:
[09:10:03 INFO]: GriefPrevention: Column Index out of range, 0 < 1.
Then it starts going through a list of usernames like this:
[09:12:46 INFO]: GriefPrevention: gnaxi --> GnaXi
This process halts the server and makes it impossible to join the server before it's done (5+ minutes)
EDIT2:
On a third note, all claims are now gone. The updated version apparently deleted everything in my claimdata and nextclaimid tables. Thanks...
EDIT3:
When using /buyclaim or /sellclaim, players are told their total amount of available claimblocks (which is high for some, since all claims was just removed as explained above), but the Golden Shovel seems to think that the player only have the starters 100 blocks, even though the database and the buyclaim and sellclaim commands tell differently.
https://images.seedbox.it/images/2014/09/23/mc629lf.png
EDIT4:
Console keeps spamming the following:
[09:28:52 INFO]: GriefPrevention: Unable to save data for player [UUID]. Details:
[09:28:52 INFO]: GriefPrevention: Column count doesn't match value count at row 1
and this:
[09:28:50 INFO]: GriefPrevention: Unable to save data for claim at [world;cords]. Details:
[09:28:50 INFO]: GriefPrevention: Column count doesn't match value count at row 1
-
View User Profile
-
Send Message
Posted Sep 22, 20148.1 Updates
There are some (uncommon) scenarios where some players may lose access to their land claims, for example if they last played before you deleted your world. In that case, their land claims will revert to "administrative" which ensures they're still protected and won't be automatically cleaned-up by any processes. If the long-lost player returns, you can return his land claims to him using /transferclaim. This has to do with GriefPrevention not knowing the proper casing for the player's name, and not being able to get it from your Minecraft server data due to the world delete.
@LeeTheENTP
Thanks, but I think I got enough. :)
-
View User Profile
-
Send Message
Posted Sep 22, 2014@bigscary
If you want more claim data, I can provide mine.
-
View User Profile
-
Send Message
Posted Sep 22, 2014@bigscary
I think the documentation is fine. It's comprehensive and well-written. The video you link to is also very good.
-
View User Profile
-
Send Message
Posted Sep 22, 2014Hey all, erik1988 was kind enough to supply me with his claim/player data, so I'm going to hold onto my UUID changes until this afternoon when I can test them using his data. :)
@Bobcat00
I think I need to do a better job with docs... I've rearranged and rewritten them so many times over the years, but I'm never satisfied. I may ultimately have to back them with a series of demo videos.
-
View User Profile
-
Send Message
Posted Sep 22, 2014@unquieterpig
From the documentation: "For example, you might use WorldGuard to create a PvP-free zone in your PvP world. To make sure no one can create a GriefPrevention claim in an area, do the following. First, use /adminclaims (detailed below) to create a claim overlapping the area already protected by your other plugin. Then, stand in the area and use /trust public. This essentially disables GriefPrevention's protections in that area, while preventing other players from creating any claims there because it's already claimed."
-
View User Profile
-
Send Message
Posted Sep 22, 2014@unquieterpig
yes. Make an administrative claim on top of WG claim and make it public/passthrough.
-
View User Profile
-
Send Message
Posted Sep 21, 2014Hey is there any way to stop people from claiming claims in world guard regions?
-
View User Profile
-
Send Message
Posted Sep 21, 2014@AdultCraft
Yes for now, maybe on later updates we'll see them back :)
-
View User Profile
-
Send Message
Posted Sep 21, 2014Do i get this right? No more per world configs?
-
View User Profile
-
Send Message
Posted Sep 19, 2014Hey all, just a quick update. I think I'm still on track to get the UUID conversion done this weekend. I've finished the initial coding, but I have a LOT of testing ahead of me.
If any of you are running in flat file mode (non-SQL mode, the default) and have lots of data for many players and claims, it would help me greatly to get those data from you (a zip file posted somewhere I can grab it?). Otherwise, thorough testing will be really tough for me because I'll have to imagine all the interesting situations and somehow produce them using only the two accounts I own.
EDIT:
Oh wow look at that! My files got approved! =D
Also, UUID testing looks good. Just going to run my test server overnight and check the logs before I release.
-
View User Profile
-
Send Message
Posted Sep 19, 2014@kvgeorge1
Yep these are definitely the wrong config files, those are the old files created by the 7.8.* versions. Ensure you're on at least GP 8.0.3 (if you're uncertain, just download the latest file from the link dev builds link above), and look for a config.yml in a folder called "griefpreventiondata". If you're still not sure you have the right file, try deleting all of the yml files related to grief prevention and restarting your server. That will generate exactly ONE file which will be the right one.
-
View User Profile
-
Send Message
Posted Sep 19, 2014@bigscary
Thanks for the response. When I looked, I am set for NORMAL (Survival) for all worlds. For sake of argument, I am posting the config.yml AND the_end.yml files here (I know they are really long....sorry for excessive reading). Also, in order to get everything to work, I had to essentially turn-off protection for "the_end" by setting Enabled: false.
As I mentioned earlier, when I first arrived at "The End" there were Endermen there, along with the EnderDragon. For some reason, all the endermen de-spawned and never respawned and the dragon did NOT drop any XP when killed.
config.yml
the_end.yml
-
View User Profile
-
Send Message
Posted Sep 19, 2014@CKGAR
There's no wrong way to update - you're not supposed to have to do anything other than set up your config.yml. If you're using SQL, make sure you're using the correct SQL url in your config file. It's not the same format as the 7.8.* versions of GP. Follow the "setup" link in the description above to see an example of the right SQL url format.
Aside from that, I'd have to look at your data. If you're running using files, maybe zip up your GP folders and post them somewhere I can look at them?
@kvgeorge1
Check to see if your THE END world is listed under creative rules worlds. That would be the only reason for not spawning monsters in a world.
@Onionbro
That's right, I removed the links to the beta docs because they don't apply to the latest builds.
@cap10zeus
I fixed the link. It needed http://
@Cra2ytig3r
Don't know - I wouldn't use anything from that line. I've removed the links from this page.
@kvgeorge1
If you're on the latest version, there is only one config file for all worlds called config.yml in a folder called griefpreventiondata. Any other config files in other folders can be deleted.
Similar to above - items don't drop when the world is marked as a creative rules world. Check that in your config file (if your server.properties says game mode is creative, GP will assume all worlds are creative when you leave the creative list in the config blank. put a fake world in there to fix this).
When items are droppable and mobs are spawnable in a creative world, griefers spam both to lag the server and make a mess. Since creative mode players don't need to pick up items and are invincible (fighting is silly), both spawning monsters and dropping of items are disabled. From the sound of it, you intend your players to play survival mode in that world, so just fix up your config.yml and everything should be great.