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 13, 2014We have a server that is whitelisted. The issue we have is whenever anyone joins, GP creates a file for them - even if they are not whitelisted. I looked in the config and did not see a setting to cause GP to wait till someone is actually in the game before making a file.
Suggestions?
-
View User Profile
-
Send Message
Posted Nov 12, 2014About the "someone" problem, I am in online mode, running the latest GP version 8.7.3 I didn't migrate to UUID, I made a fresh GriefPreventionData folder. The file that is affected can be seen at https://m.ly/0 or downloaded at https://m.ly/0.zip (files will be deleted in 72 hours)
P/S: I let players rent plots by giving them permissions in admin's subdivided claims (whenever they type /rent). It usually happens when they type /rent, the permissions become "someone"
-
View User Profile
-
Send Message
Posted Nov 12, 2014@bigscary
"Since the new tree types were added by Mojang a couple of versions back, the treetop code hasn't been working on those new tree types, and no one noticed (or cared enough to complain, anyway)."
I noticed, figured it had to do with the new tree types, but wasn't bothered by it enough to complain.
-
View User Profile
-
Send Message
Posted Nov 12, 20148.7.3 Updates
More details on reasons for these changes follow. :)
On fire:
After doing analysis on the biggest cause of GP's CPU time (players left-clicking on blocks), I determined that cutting fire protection would cut that time in half. So I dropped it, and gave you all an option to re-enable it.
Yes, I do know that players sometimes create fireplaces in their homes or epic braziers atop their castle towers, and I still think this change is a VERY good trade-off. Most flames are temporary anyway, and in many (but not all) cases, it's not inconvenient to add some glass or other blocker to prevent players from putting out a permanent flame.
I worked for several hours, monitoring CPU expensive for several alternatives to this change, but nothing I came up with protected flames while saving CPU time.
On treetops:
@Cereealh
Yep, for survival worlds, disabled in the nether and end by default. Use your config file to enable it for those worlds if you want, but it may not be worth having GP monitor those worlds, as there will be few player claims there on most servers. See the setup/config page linked above if you'd like more details. :)
@LordDWT
Yep sorry, had a lot to write! See above. :)
-
View User Profile
-
Send Message
Posted Nov 12, 20148.7.3 does not have a change log.
-
View User Profile
-
Send Message
Posted Nov 12, 2014disabled in a world?
-
View User Profile
-
Send Message
Posted Nov 11, 2014@Kahenraz
Yep, I also recently learned that even in Vanilla, that event can be incredibly spammy. When a new chunk is generated, water isn't right immediately, and a flurry of water flow events fire until everything settles out. So as players push the boundaries of the world, a LOT of very substantial but short-lived lag can happen. If fluid flow continues to be a problem despite my recent changes to how it's handled by GP, I will look into possibly ignoring those events for recently-generated chunks for a small window of time after the chunk generates. Right now, it's not even on the radar, but that may be because no one has successfully captured timings in the narrow window in which it was happening.
Sure thing, I'll have a look at those pull requests. Didn't notice them. :\
-
View User Profile
-
Send Message
Posted Nov 11, 2014@bigscary
I an confirm that fluid tracking has been a major source of "mystery lag" on my server. When trying to diagnose major TPS issues, we've often found the result to be a large amount of droppers pushing/pulling water in large dark-room spawners.
Also, please consider my pull requests on the GitHub.
-
View User Profile
-
Send Message
Posted Nov 11, 2014@LeeTheENTP
Nope, I removed it entirely for survival worlds. It still applies to creative worlds. Give it a chance - I think if you run your server for a while without it, you'll agree it's overall better this way. Over the years, this area of the plugin has been controversial for both admins and players, and I recently eliminated the main reason for having it in the first place (greatly reduced the cost of tracking fluid spread).
I turned it off for my public test server a couple of weeks ago. The players like it better this way, I haven't logged any lag spikes, and I can easily remove dumped fluids with /restorenature, just like other unwanted wilderness builds.
-
View User Profile
-
Send Message
Posted Nov 11, 2014@bigscary
Can we still enable the bucket dumping ban and fluid cleanup in the config?
-
View User Profile
-
Send Message
Posted Nov 11, 2014@starg09
I think this will disappoint you, but my thinking is that if a plugin author creates a griefing opportunity, it's up to him to also provide a solution. If extending pistons with slime blocks in front can be an issue, then the developer of that plugin should give admins an option to disable that.
Or, he can use the correct Bukkit API's to send an event with world change information to other plugins, then check whether or not any of them cancelled the event.
If it does appear as a standard feature on CraftBukkit servers, then I'll address it in GP for CraftBukkit.
-
View User Profile
-
Send Message
Posted Nov 10, 2014Feature suggestion: Could you add protection against slime block extension in 1.8? In spigot/bukkit in the far future, but currently with the Carbon plugin for spigot. It would be really appreciated.
You see, with slime blocks comes the possibility of stuff like missiles, which can move by themselves without interaction of a player (at least without interaction of the player in a protected area). This can lead to some serious griefing on servers, wether it's just moving some blocks, or shooting tnt to a "protected" spawn.
So... could you maybe add protection from this to this plugin in some way (maybe deny piston extension when a slimeblock is in front, altough that may work better as a separate protection plugin...)
-
View User Profile
-
Send Message
Posted Nov 10, 20148.7.2 Updates
-
View User Profile
-
Send Message
Posted Nov 10, 2014@sparts
Yep, that's right. Blame Bukkit - they made a decision that searching for offline players by name would now make an internet call every time to ask Mojang for UUID. The alternative of searching your local offline player data one player at a time is equally bad. I tried both ways, and both ways generated an unacceptable level of server-wide lag.
About your water problem, set your config file correctly - there's a sea level override setting for when your sea level isn't what Bukkit guesses it is. Now that worlds are more diverse, I'm trying to come up with a better way of doing this.
-
View User Profile
-
Send Message
Posted Nov 10, 2014It appears players can no longer trust people that are offline. This is quite annoying when you make a new claim and your friend is offline at the time of creation. Also players can grief entire bodies of water by claiming/unclaiming them.
-
View User Profile
-
Send Message
Posted Nov 10, 2014@dutchrastacraft
It just means your local server data doesn't have a player name to go with the UUID. If the player logs in later, it will fix itself.
@broluigi
What Basurci said.
-
View User Profile
-
Send Message
Posted Nov 10, 2014@broluigi
There is no 1.8 yet. And it does work with latest Spigot and final Bukkit release
-
View User Profile
-
Send Message
Posted Nov 10, 2014does this work for 1.8
-
View User Profile
-
Send Message
Posted Nov 9, 2014@bigscary
No problem :) By the way, I also have that problem with the player "someone", but that occurred after convertion to UUID's. Since we are a cracked server we just banned the player "someone", just to be sure.
-
View User Profile
-
Send Message
Posted Nov 8, 2014@Mipastu
Default protects players from pvp in land claims. Update your config file:
@mcly
It's in the config file - set the worlds you don't want claims in to "disabled":
About the "someone" problem, are you in offline mode, online mode, or bungee? What version of GP are you running? Please send me the logs for the boot where you migrated to UUID, and also the data for that land claim.
@dutchrastacraft
Nice, thanks! Was hoping you'd pop in with an update after my changes to player login/logout. :) Already planning more optimizations.