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 16, 2015@Goldentoenail
In the latest version, you can have pvp rules turned on but still disallow placing lava next to other players. Just update to the latest, then adjust using the new settings in your config file.
As for what you're doing wrong - when lava isn't allowed to be placed very close to other players according to the config, admins (permission: griefprevention.lava) can still place lava anywhere, including on other players. Maybe you've been testing as /op?
-
View User Profile
-
Send Message
Posted Oct 15, 2015The old Lava PVP grief problem.
I have a Survival world. In order to have a PVP Zone in one location. The server is set to PVP true.
However the global region is set to PVP: deny.(using WorldGuard). And just the one PVP Zone region is set to PVP: true (using WorldGuard). The result of which enables PVP in the PVP Zone region only.
It does not matter whether Griefprevention is set to PVP: RulesEnabledInWorld: world: false or true.
Players can place lava near other players in the world and kill them.
I do want players to be able to use Lava inside there claims, but not to use Lava buckets to PVP players.
Am I doing something wrong?
-
View User Profile
-
Send Message
Posted Oct 13, 2015Update 12.8 is here!
-
View User Profile
-
Send Message
Posted Oct 12, 2015@Ehrensalut
The file will reset if you make a syntax mistake. I recommend using a YAML editor (like notepadplusplus) which will help you by highlighting mistakes, and also always making a backup copy before trying to boot your server with your changes. Sadly, this is just a problem with yaml - easy to read, tricky to edit. The most common mistake is putting tabs instead of spaces at the front of a line.
@mrcheesete0
Yep I got a msg via email.
-
View User Profile
-
Send Message
Posted Oct 12, 2015bigscary, Blood over at SP is trying to get in contact with you in regards to a port of GP for Sponge the dev team whipped together. Might wanna hop on and talk to him about it
-
View User Profile
-
Send Message
Posted Oct 9, 2015Hello bigscary, I downloaded your plugin and need to say, that it is pretty useful. But I need to ask something: Is it possible to translate it by myself? I tried so, but it resetted the config after a restart. Does it need to be changed via the .jar or isn't it possible at all?
Greetings, Ehrensalut
-
View User Profile
-
Send Message
Posted Oct 8, 2015@GodsDead
Yep, there's already a ticket tracking custom ban command lines.
Is there some exploit involved in a player sieging himself? If not, I'll leave it as-is... handy for testing, plus every time I change something something else breaks.
-
View User Profile
-
Send Message
Posted Oct 8, 2015Players can Siege themselves...
-
View User Profile
-
Send Message
Posted Oct 6, 2015@bigscary
Amazing! Its funny how quickly we fall into routines, I've been trying to change myself to a ticket system but I stil rely on my forum support tickets!
Alright, then Ill just keep throwing things into here! They may stack up. On top of the things i've already mentioned:
-
View User Profile
-
Send Message
Posted Oct 5, 2015@GodsDead
I'm doing fine tracking comments here - I've had years of practice, plus lately I don't get so many comments because I've updated the plugin to solve most problems without asking a question (for example, if an admin doesn't have enough claim blocks to claim an area, the error message tells him about the /acb command). Anyway there's a ticket tracker here on bukkitdev - just click the blue tickets link above. Ironically, I always remember to read comments, but often forget to check on tickets. You might get a faster response from comments.
-
View User Profile
-
Send Message
Posted Oct 4, 2015@bigscary
Its too late for me to turn back now, we are just re-creating the sub-claims, but there was an issue converting, what I will do is send you a copy of our GriefPrevention database, so that you have some real-world data to play with at some point. I have a few other issues to report, but I will wait until you are caught up. Where do you keep track of all your open tickets? Using the comments here must be impossible. Most people tend to have a github and use the issue tracker there?
-
View User Profile
-
Send Message
Posted Oct 4, 2015Update 12.7.2 is here!
@AriKira
You can't use the same database for two different servers, or share claim blocks across servers. If you really want to do either, my source is on github - you can make those customizations yourself or ask/pay someone to do it for you.
-
View User Profile
-
Send Message
Posted Oct 4, 2015And could U add an option in config to custom the mysql tables name or prefix? I want to make different servers's tables in the same database.
-
View User Profile
-
Send Message
Posted Oct 4, 2015@bigscary
That mean...I cannot make players have the same claim point in different servers? Maybe i need use mysql trigger to synchronize 'griefprevention_playerdata''s date?
-
View User Profile
-
Send Message
Posted Oct 3, 2015Update 12.7.1 is here!
@G0ularte
Yep there's a claim mode for that - see setup/config page.
@AriKira
Different servers should use different databases (but the databases can all live on the same database server).
@MotheMan
Rather than blanking the list, reduce it to only a fake word no one will type like asdfasdfasdfasdfasdf22232. Due to a mistake on my part, leaving the list entirely blank results in all words being treated as profane. :( I'm working on the fix.
@deathly809
I dunno which files are missing? Maybe the JUnit stuff. Try deleting the file with tests in it.
@marubal21
I'm gonna have to work on making the docs on that more obvious. Unused only applies to creative mode worlds - it means a claimed area where few player-type blocks have been placed, making the claim "unused" in the sense that it doesn't protect a build, just reserves a wilderness area. Because players can by default create any number of land claims and in creative mode start with the golden shovel, griefers could potentially sprinkle small claims around just to be annoying. This would clean those up automatically.
@ExDomino
Put a subdivision around the container, then /containertrust public in that subdivision.
@Asile
Nope, sorry. Most of GP's rules (like no creeper damage above sea level for example) apply onto to worlds where land claims are enabled. I hope that helps?
@GodsDead
I'll work on the first two issues right away. Please give me more information about your conversion - maybe you have some logs? My guess is the reason it doesn't go well for you is because your server is atypical - huge amounts of data from existing a long time, heavy load due to many players simultaneously, and running in database mode. That's not an excuse for my making mistakes of course - but it's almost impossible to test for your situation when I can't manufacture it on my test server (mine is a year old and in database mode, but I'll bet I see nowhere near your traffic levels).
-
View User Profile
-
Send Message
Posted Oct 2, 2015I am running GriefPrevention alongside MultiVerse. Is it possible to have a completely different GriefPrevention configuration on different worlds? For example, if I want FireSpreads to be false for one world, but true for another, is that possible?
Thanks!
--
Asile
www.twitch.tv/kingbohica
-
View User Profile
-
Send Message
Posted Sep 30, 2015@jahangir13
Alright, I have set my database to have a very high number of open connections, mines set to something like 250, and I can see 25 open connections at present, either way the plugin is converting all claims to turn into negative which in turn resets them to 0 when /claimslist is ran! So there is a major issue there.
For the second issue of the badly converting sub-claims; I finally bit the bullet and updated my main server, the sub-claim conversion did NOT go well, an entire city of sub-claims was removed. Why can a conversion never work properly!
-
View User Profile
-
Send Message
Posted Sep 30, 2015@GodsDead
Hi GodsDead: have a look here: http://stackoverflow.com/questions/2839321/connect-java-to-a-mysql-database/2840358#2840358 Somewhere in the middle there are some points for the Communication Link Exception.Could be something like 6.)...too many open connections or other parameters. I did not have a look into the code if connections are closed properly. But you could check in my.cnf how may_connections are allowed. It' s just a guess...but as this happens sporadically as it sounds it's maybe an db issue like this (and not caused by the plugin itself).
-
View User Profile
-
Send Message
Posted Sep 29, 2015Finally got around to testing out this new conversion you do after 12.3 as the beta tag was dropped in 12.7 as I expected the data to not convert properly, It did give me an error, when i next ran the server it also showed only 7986 claims too.
-
View User Profile
-
Send Message
Posted Sep 29, 2015Is there a way to disable the protection for just one container, for example the trade booth top from trade booth mod?