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 Nov 5, 2014@GodsDead
Per world configs are gone for now. They'll come back eventually, in an easier to use format.
Just set LimitSurfaceWaterBuckets = false in your GriefPreventionData\config.yml. :)
There's also a sealeveloverride config option, if you want to tweak the Y value where the rule applies.
If you have worlds where claims are disabled, the water bucket rule will not apply there even if you have that rule enabled in the config file.
@xxooss
I have no current plans to do anything with Rainbow. I'm waiting to see which new platform becomes popular, and my bet is on Sponge.
-
View User Profile
-
Send Message
Posted Nov 5, 2014@GodsDead
Nope, it's all preset and we just have to live with it, for now. Makes the config super easy for new users, but of course it leaves us more advanced users in the dark.
-
View User Profile
-
Send Message
Posted Nov 5, 2014re all, I am sorry if this is a redundant question but Is GP going to be fixed to work with the Rainbow project jar? I have been using 1.7.10 and it is perfect so I backed up and "upgraded" to the rainbow version of 1.8. All went fine except for some plugins not working but that was expected. I noticed that GP was not loaded and I had zero protection so i stopped server and set it to owner only. lol any way I went back to 1.7.10 and everything was fine except the signs were messed up but no big deal i could revert to back up.
Tl;Dr I know sorry. I guess I really want to go to 1.8 but if GP won't work I have to redo "claims" with some other plug in like world protect. sigh. So is there a current plan to make GP work in the Rainbow versions?
Thank you so much for such an awesome product.
-
View User Profile
-
Send Message
Posted Nov 5, 2014@Bobcat00
Wait, so we are limited to the way the developer has set the rules?! What happens if he decides that water can only be placed in claims? Where as I think thats a stupid idea and want to set it globally? as an example. Could we still not have the option to set our own rules like before?
-
View User Profile
-
Send Message
Posted Nov 5, 2014@GodsDead
The GriefPrevention folder (including per-world configs) is ignored. All config is done via GriefPreventionData. There are no longer unique config files per world. You'll probably need to reconfigure using GriefPreventionData.
-
View User Profile
-
Send Message
Posted Nov 4, 2014bigscary could you possibly take a look at my ticket please? I did not paste it here because it had playernames and UUIDs in it. Thanks in advance.
-
View User Profile
-
Send Message
Posted Nov 4, 2014Ive been using 7.8 since it released and decided to test out the conversion process on my development server, It looks like you have made a new plugins config folder called GriefPreventionData? But there are no world configs in there, so are the world configs still being pulled from the GriefPrevention\WorldConfigs folder? I have well over 11,000 players all on mysql, Thought I would try and understand what has happened to the new version of GriefPrevention while I wait.
-
View User Profile
-
Send Message
Posted Nov 4, 20148.6.5 Updates
@mrretrus
No permissions changes needed, only config file.
chest claim radius = -1 (disables chest claims for everyone)
creation requires permission = true (disables creating with golden shovel unless the player has griefprevention.createclaims permission)
@Turbotailz
Will you please look into your log files and get one of the messages sent to a player because he had a login cooldown? I want to see the exact text sent - it should look like this:
You must wait X seconds before logging-in again.
If it says minutes, your server is in a weird state - please try a /reload, and if that doesn't work, a reboot.
-
View User Profile
-
Send Message
Posted Nov 4, 2014How do I completely block players from using this plugin? This also includes placing their first chest- The reason why is because im using it to protect Spawn builds only on a factions server for FTB. Ive tried setting claim size to 0, tried setting "requires permissions" to TRUE, tried negating the node griefprevention.claims.chestcreate and even the whole set with griefprevention.* (Using groupmanager) - But still players are able to get a claim by placing their first chest! How can I block the plugin to everyone but my staff?
-
View User Profile
-
Send Message
Posted Nov 3, 2014I believe it is only player made claims in which this problem occurs with.
-
View User Profile
-
Send Message
Posted Nov 3, 2014@ThisUsernameIsMine
Always use the latest. :) In the extremely rare case where a new build is overall worse than an older build, I retract the build so that no one can get it. Newer is always better.
@confuser
Yep, I will.
@Bobcat00
You misunderstand. It still gets rid of many claims, it's just sticking to only considering how long the player has been gone, and not also scanning the content (blocks) inside a land claim. Chest claims will still be removed by default, and you still have the option to auto-remove land claims for all inactive players based on days absent.
The "scoring" land claims based on what types of blocks were in them was expensive and didn't remove many land claims, and that is the only part I changed. I was tempted to remove it entirely, but left it in for creative mode claims because it also effectively auto-removes lava towers and other ridiculous messes which only really happen in creative mode worlds.
@Johndonne
I've seen this for land claism which have subdivisions (and so they require a confirmation, where you /abandonclaim again). Are you saying you have this problem for all types of land claims, all of the time?
@Turbotailz
I'm not sure how that could happen, but I will look into it.
@Johndonne
I made a note of your problem, but deleted your message because it was so long. Please use pastebin next time. I will look into that for you. :)
@sparts
No, there's no option to remove that. I do understand the problem, though - sorry I haven't come up with a better solution to preventing griefers from dumping water all over the world.
-
View User Profile
-
Send Message
Posted Nov 3, 2014I'm wondering if you can disable the feature that removes water/lava from claims when you delete or abandon them. You can use that to remove water effortlessly and also its a hassle when you have to delete claims. I have to go back and fix all the water that it deletes.
-
View User Profile
-
Send Message
Posted Nov 2, 2014Thanks to a couple of people who joined my server yesterday, I was made aware that the wait for re-logging (anti-spam) in was set to 30 minutes instead of 30 seconds (as it is set in my config). I have since then disabled anti-spam altogether, not a huge deal but thought I'd let you know this happened.
Not sure what version I currently have - jar file just says GriefPrevention.jar, installed it on 25 Oct so it's probably 8.6.
-
View User Profile
-
Send Message
Posted Nov 2, 2014When deleting claims using any method (/deleteclaims, /abandonclaims, /abandonallclaims), claim is deleted from server (no entry in ClaimData folder), however claim remains in world until restarted.
-
View User Profile
-
Send Message
Posted Nov 2, 2014I agree with Bobcat00. Removing of unused claims is a MUST. You could do removal once every 12 or 24 hours and still get performance increases. I think I'll stay on my current version for now.
-
View User Profile
-
Send Message
Posted Nov 2, 2014@bigscary
"No more scanning survival mode claims to remove unused claims" - What? One of the best things about GP was that it got rid of old claims. I can't imagine it was a big impact. You only needed to do it once every 12 hours or so.
-
View User Profile
-
Send Message
Posted Nov 2, 2014GP perms do not working for NONE OP staff/players... tried old version perms and newer version. Cannot get any Perms to work running version: v7.8 Any ideas?
Until all bugs get worked out of newer version I'll stick with this version
I'm changing op status on must staff, this is how I found out perms not working for none OP players
Edited: I put wrong version in by accident sorry, edited the correct version
-
View User Profile
-
Send Message
Posted Nov 2, 2014Can you please re-add the custom events for other plugins to listen/cancel please, e.g. ClaimBeforeCreateEvent etc
-
View User Profile
-
Send Message
Posted Nov 2, 2014@bigscary
I'm a long term user of your great plugin, but stopped using GP at some point.
Now i want to get back into the game but i'm uncertain which build to use (cause: frequent updates :+) ).
Is it wise to wait a bit longer for a big update to come or should i simply use 8.6.4 or 8.6.2 (since 8.6.3 is confirmed to be broken)?
Thank You in advance for the contineous efforts to improve your plugin(s).
-
View User Profile
-
Send Message
Posted Nov 1, 20148.6.4 Updates
About /SoftMute
It's a great ban alternative - unfortunately, banning an immature player often motivates that player to escalate - coming back on another account on the offensive, recruiting other malcontents to make trouble, or sometimes a DDOS attack. /SoftMute limits a player's chat messages to only other players under /SoftMute, effectively putting them on "ignore" for all the mature players. Unlike a ban, because the troublemaker doesn't get any indication he's on mute, he doesn't escalate.
Every time I use this on the test server, I picture Mr. Burns behind his desk, tenting his fingers. ;) It has proven very useful in turning chat trolls into quiet, well-behaved players who just think they're making trouble.