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 29, 2014@bigscary
I use GP and worldguard (I like worldguard in many cases over admin claims). If you stopped pistons outside of claims that would be a major headache for me. I have several Redstone circuits utilizing pistons in world guard regions not in any claims.
Once I have some time I will be happy to test timing. I'll follow up later on this.
-
View User Profile
-
Send Message
Posted Sep 29, 2014@dutchrastacraft
Man, that is a beating. I'm glad this UUID conversion stuff is just a one time thing.
-
View User Profile
-
Send Message
Posted Sep 29, 2014@bigscary
I am still converting my data. I had to run a query today to remove 77k rows because the convertion was going to last for a full week! Now it'll take approximately 2-3 days. When it's done I'll make sure to help you out with the timings!
-
View User Profile
-
Send Message
Posted Sep 29, 2014Please read! I need your input/help.
I'm concerned about a potential server performance hit related to limiting where pistons and push and pull blocks. Basically, the issue is that a piston can push a lot of blocks, and for each one, I have to check whether it's in a land claim or not. Further, pistons can be hooked up to redstone clocks, multiplying the cost and creating a loop such that one player can do a LOT of block moving.
I could completely solve this problem by not allowing pistons placed outside of land claims to move blocks, which would carry the additional benefit that pistons could never be stolen due to sloppy placement. I'd like to know what you all think of this before I do it, since the downside is that players may sometimes use pistons outside of land claims (I think very rarely?), and this would agitate those individuals.
I've decided it's time to make another pass at improving GP's overall performance. To do that, I need your help. If you'd like to help out, please install 8.1.5 (I will release it later today) and turn on timing measurements (the steps are different for craftbukkit versus spigot versus others, so check your docs/wikis to learn how to do that). After you've collected measurements for at least a full day, share them with me either in comments here, or via private message if you prefer.
I will be allowing tree growth to place blocks inside claims when the tree is rooted outside. A recent look at some perf measurements showed that it's a large part of GP's overall execution time to prevent a "grief" that only the most detail-obsessed players care about, and which can be remedied by extending your claim out a little or (harder) pulling your build in away from the claim border.
-
View User Profile
-
Send Message
Posted Sep 29, 2014@Bobcat00
From that log output, GP's claim loading is taking less than a second. Please update to the new version (8.1.5) when it's available and share your output from that. I'm adding more detailed boot logs, which may help explain what's going on there.
@theDarkFate
What do you mean by "plugin message format"? It's just strings in a YML file. Have you successfully edited other YML files and put Korean into them?
@Feeriix
Glad it's fixed, I'll make a note to myself to automatically delete claims for deleted worlds so that messages like that won't appear.
@tomaste
Seems bizarre to me. I'll think on it and see if I can figure out why that would happen for you.
@GodsDead
I've had a look at your logs there. GP isn't crashing - Spigot is killing GP because GP is waiting too long for your database to accomplish a simple task. Look into either improving the performance of your database (preferred solution), or configuring Spigot to allow GP (or all plugins) to take longer before killing them - some lag is better than no land claim protection.
-
View User Profile
-
Send Message
Posted Sep 29, 2014In my case, I figured out which claims were converted to administrative. Any claim that was created by an admin, then transferred to a player, was converted back to administrative on upgrade to 8.1.4.
Now that I know this, I think it can be managed. I'm not sure if any player->player transfers happened, and what happened to those claims though. I haven't found that situation yet.
-
View User Profile
-
Send Message
Posted Sep 29, 2014There is a major bug with how griefprevention handles the mysql connection. If the mysql server crashes, overloads or looses connection it will crash the minecraft server with it, this has been the constant cause of grief in my life for the past 6 months with GP being the main cause crashing my server because its lost connection with the mysql server.
Sometimes the minecraft server will stay up, but all claims will be open and vulnerable. Please, please can we have a try/catch so if griefprevention looses connection to mysql there is a backup or cache used for the claims, this could also trigger an event to cache any claim edits while the mysql server is down and then update it when it establishes a connection again.
Here are some examples of a crash caused by this issue. http://pastebin.com/vBi6QwmT
http://pastebin.com/EFi2cUzY
-
View User Profile
-
Send Message
Posted Sep 29, 2014@bigscary
With 8.1.4: http://pastebin.com/QGnaVHpp. Removing the claims from that world solved it. Thanks for the help.
-
View User Profile
-
Send Message
Posted Sep 28, 2014@bigscary
It is recognized korean as special characters but your plugin message format does not allow special characters
-
View User Profile
-
Send Message
Posted Sep 28, 2014Regarding startup speed, my flatfile GP takes 7 seconds to start with 104 claims made by 31 players. This is the non-UUID version, of course.
-
View User Profile
-
Send Message
Posted Sep 28, 2014@bigscary
Yes, this is how bungee works. All previous versions of gp, work without issue. Its with the recent UUID the admin claims issue arose.
For me, personally, when username changes ever do come into play, Id happily just transfer the claim from one name to the new one.
But, from what you saying, for me, and other bungee users, were out on a limb now with GP.
Im not a coder, nor can I offer much advice, but maybe some other bungee Gurus can comment on possible solutions.
-
View User Profile
-
Send Message
Posted Sep 28, 2014@bigscary
Yes, I'm running in flat file mode. The log won't tell me how many claims I have, but in ClaimData/_nextClaimID I have 9156.
Intel(R) Xeon(R) CPU E5-1650 v2, 64GB Ram, SSD
-
View User Profile
-
Send Message
Posted Sep 28, 2014@McLive0
That's an insanely long boot time. How many land claims do you have? It would be in the boot logs. I assume you're running in flat file mode? Is your server professionally hosted, or are you running it on a laptop you found in the garage?
-
View User Profile
-
Send Message
Posted Sep 28, 2014@bigscary
I wonder why the startup takes so long. My server needs 627 seconds with GP installed.
-
View User Profile
-
Send Message
Posted Sep 28, 2014@McLive0
No, there's no change to boot speed or migration speed. I plan to address the boot speed eventually but right now I need to stabilize all this UUID conversion stuff before I start changing up the file format and adding all new bugs.
-
View User Profile
-
Send Message
Posted Sep 28, 2014@erik1988
No there isn't any option to allow creepers to explode blocks in land claims.
@theDarkFate
I don't understand - what doesn't allow unicode, the YML file format?
@cap10zeus
Which version are you on? This code is not mine - I think you must be on one of the broken beta builds created by BC_Programming. Please update when you can.
@unquieterpig
Not sure it's GP - can you get closer to the blocks so I can make them out? They're too far away in the picture.
@TJW28
Do I understand correctly that your servers are in offline mode, but your players are authenticated and connecting in online mode? If so, I have no idea how I can account for that - certainly the UUIDs generated for offline mode will not match the real UUIDs given by Mojang. Share your logs anyway, just in case I see something you don't?
EDIT: Just went and tried to figure out what Bungee is. The outlook is grim - seems Bukkit can't handle this situation and explicitly does not support Bungee, which means Bukkit plugins (like mine) probably can't do anything to help. If I'm wrong and you can point me to some specific information on how to work around this problem, please do. :)
@tomaste
Please confirm you're on 8.1.4. I also need more details - online/offline mode? DB or flat file? Bungee? Also logs from the first boot after update to 8.1+. Sorry to ask for so much, but it's all critical information.
-
View User Profile
-
Send Message
Posted Sep 28, 2014@TJW28
Mine is also updating all claims to admin.
-
View User Profile
-
Send Message
Posted Sep 28, 2014My setup is Bungee, with the proxy in Online mode, and Servers in offline mode as per the norm. I currently use Flatfile.
I have a Mirrored image server as test platform, and updated it to the latest build, and during boot, it changed all player claims to Admin Claims. I have tried a few times, setting server to be On, and Offline mode with same results.
Nothing unusual in logs other than the message saying "Failed to look up UUID for player", and then converting it to an Admin claim.
I'm hesitant to update as is, so, any advice?
-
View User Profile
-
Send Message
Posted Sep 28, 2014Im getting these weird claim border blocks after each chunk.
http://imgur.com/IE0QvQk
-
View User Profile
-
Send Message
Posted Sep 28, 2014Is the slow startup fixed in the newer builds?