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 Oct 14, 2013is there a way to disable griefprevention completely in a world, like in my skyblock world i want to be able to place lava while close to my friend. im using gp 7.7
-
View User Profile
-
Send Message
Posted Oct 14, 2013@DonGrif There is no ETA on an actual "release" or "beta" of [GriefPrevention for] 1.6.4. Providing an ETA gives the illusion of a schedule which simply does not exist; Thus the development builds. At this stage the main issue is simply having to rewrite practically every page of documentation for the project since many critical parts of the plugin have been touched and changed.
-
View User Profile
-
Send Message
Posted Oct 14, 2013ETA on 1.6.4 version of the plugin?
-
View User Profile
-
Send Message
Posted Oct 13, 2013@MistPhizzle
Check that you don't have your starter claim size set for bigger than the amount of initial blocks. I did that on my server by accident and the result was that everyone was able to claim more than their initial block allowance when they placed the starter chest but they got negative claim block amounts.
Idk if that's what's happening for you or not, but I thought I'd offer it to rule it out.
-
View User Profile
-
Send Message
Posted Oct 13, 2013@Gunner857
You have a folder named worldconfig and a worlds file there. Look 700 lines down for Expiration:
-
View User Profile
-
Send Message
Posted Oct 12, 2013On my server the claims delete them selfs after a day or so please help
-
View User Profile
-
Send Message
Posted Oct 12, 2013I have the MaxAccrued blocks set to 250,000, blocks per hour at 300, and initial blocks at 1500. Players are starting with negative blocks, help?
-
View User Profile
-
Send Message
Posted Oct 10, 2013When enabling and disabling GP (Grief Prevention) on a world I know you can do it in the GP config.yml file but is there a way, command or such that will allow you to enable/disable GP on a world in game? I am creating personal worlds for players and would like to enable GP for a world with a single command, rather than having to modify the config.yml manually.
-
View User Profile
-
Send Message
Posted Oct 9, 2013Hi BC,
I'm currently running #179 and have run into another issue and I need help on where to start trouble shooting. I don't know if this was a 1 off type of problem or if it will re-occur. On my last server restart several players lost part of the builds in their claim.(Right along the chunk boundary)
There was a save right before the restart and it was restarted properly. Any idea what may have caused this? The most recent thing changed was an update to the latest McMMO dev build.
Thanks, EmberC
-
View User Profile
-
Send Message
Posted Oct 9, 2013@fungreenfox
Thats your opinion. Have you asked anyone what they like about this discision? An admins job to resize a claim, should not contain paying out of his own amount.
Both of the things I said are not "opinions" they are facts, and they are how the plugin has worked since LOOOONG before I ever got involved with the project, practically since it was started, presumably. I'm not sure why I would have to ask people about somebody elses decision that was made years ago. Additionally, admins resizing a claim do not pay out of their own amount. There might be something you aren't understanding, specifically my second paragraph. Claim block values are NEVER decremented. when you make a claim you do not "lose" claim blocks; your current number of claim blocks is calculated when needed by taking your current total accrued and bonus claim blocks and subtracting all the claims you own. If an admin resizes somebody elses claim, that player- Not the admin- the player owning the claim- will need the have enough claim blocks. Any admin with permission to resize somebody elses claim should have permission to give claim blocks to a player so this shouldn't be a problem.
I have no idea what part 2 is referring to, but it certainly wasn't in these comments.
-
View User Profile
-
Send Message
Posted Oct 9, 2013@BC_Programming
Thats your opinion. Have you asked anyone what they like about this discision? An admins job to resize a claim, should not contain paying out of his own amount.
2) GP holds onto that the user doesnt exist at all, but a check for the file or typing /seen <name> shows obviously a profile. User has even set the existing claim by himself, and claims are set to expire in a year.
-
View User Profile
-
Send Message
Posted Oct 8, 2013@fungreenfox
adminclaims is for creating administrator claims and has no effect on resizing existing claims of other users.
The way claim blocks work is the accrued amount plus the bonus amount minus the size of all claims made by that player. Therefore there is no way for a claim to be resized without giving that player more blocks.
-
View User Profile
-
Send Message
Posted Oct 8, 2013@Snoopyfighter
This plugin is designed around multi-world compatibility. Just remember that the configuration and permission nodes have changed between the release and the development versions, so please reference the correct page.
-
View User Profile
-
Send Message
Posted Oct 8, 2013I am wondering if this plugin has multi world support. I would love to use it on one of my worlds but not the rest. If there is anyway to do this please let me know. It will not work for me if players can use the protection (golden shovel) anywhere on any world, just one.
-
View User Profile
-
Send Message
Posted Oct 8, 2013the option expiration is not working will be neat? or how to use
-
View User Profile
-
Send Message
Posted Oct 8, 2013I want to resize a users claim as admin. I switch to adminclaims and get message, i can claim for free. But when i try to resize, i get told, i have used all my blocks in this world (there are 500000 for users), though i have just bought 100.000 blocks. What am i missing?
Fixed resizing was already fixed in 171? i had 172, (updated to 179 this minute, and i am still getting the msg, that i need more blocks. I should, by all means, have all permissions for this. If i have to change the settings for the world, those settings will be to high amount for a user. As far as i can see, GP doesn't see me as admin.
-
View User Profile
-
Send Message
Posted Oct 7, 2013is there any way to deactivate the sign log? Thanks
-
View User Profile
-
Send Message
Posted Oct 7, 2013@BC_Programming
Thank you for your replies. I did find the problem and it was indeed Dynmap. Specifically the griefprevention 0.60 add-on for dynmap. Updating to 0.7.0 fixed the problem.
-
View User Profile
-
Send Message
Posted Oct 7, 2013@MinecraftLegends_us
You would need to run the server longer than 25 seconds to get a usable timing log. Based on that one it looks like some other plugin is causing signs to change frequently, Though I wouldn't have any idea which one it would be.
-
View User Profile
-
Send Message
Posted Oct 7, 2013@MinecraftLegends_us
I have been using GP for almost 1½ year or more, and its not GP making lag. To answere your question more precisely, i suggest you to goto bukkit help forum and provide the pc specs like cpu Ghz, ram amount, disk usage and amount of plugins. My guess is dynmap if you have that.