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 Apr 17, 2014Does anyone know how to make the Claims.LockAllDoors: false to Claims.LockAllDoors: true under the "Configuring Security". The link for it is: http://dev.bukkit.org/bukkit-plugins/grief-prevention/pages/administrative-topics/ I tried putting the command into the world.yml in the plugin folder but it deletes the command. I don't know how to turn it on for true, by default it is set at false. I have downloaded all the .yml's associated with the Grief Prevention and I can't find it in any of them. My server is running 1.6.4 for pixelmon. If someone can help out i'd really appreciate it. thanks
-
View User Profile
-
Send Message
Posted Apr 17, 2014Hey Devs,
My server is running the latest build for Minecraft 1.6.4 I can't seem to remember which one though. I'm the server owner and all of he players, including myself, have been randomly losing claims, even Admin claims for our central spawn, Which isn't too much of a problem, except there have been a few griefers taking advantage of this. We are using a mod pack as I know this is unintended, but ever since I've installed Griefprevention, except within the past 3 days it has been working flawlessly. Players are becoming uneasy with this since we've had slight influx of griefers attacking, and it's almost pushing us to having to pass a whitelisting to prevent that. I really like keeping an open server for everyone to come and play, but without some form of grief prevention, it's making an open server less appealing. Thanks in advanced for any help.
-
View User Profile
-
Send Message
Posted Apr 16, 2014Latest build is almost good, clean claims is finally working awsome job on that, but it need some improvement on performance, it's impossible to run on a real server. It's kicks everyone of the server while performing the cleaning tasks (80 kicked players, 18 minutes running the task, nobody could join while the task was running), first time I thought that was ok, too much things to clean up... but after that, instead of kicking everybody while running the clean up task it just freeze the server for 512 seconds again and again.
And why it's taking so much time to startup with alot of players? 13.000 players on db and it takes 4 minutes to load on startup, making the MySQL server crazy (99% cpu usage), same thing happens with flat file, of course in this case the server proccess goes to 100% cpu, not the MySQL...
Server specs: E3 3.4gz, Raid 1 SSD + 32GB RAM
-
View User Profile
-
Send Message
Posted Apr 16, 2014@xbenas
This is never going to happen. It's against BukkitDev policy to steal someone's project that way.
There is nothing wrong with the 7.8 design, I'm keeping tabs on BC's Github for obvious reasons and bugs are being squashed every day.
-
View User Profile
-
Send Message
Posted Apr 16, 2014Can someone make GriefPrevention Reloaded which is based on 7.7? The only bug fixes it needs is the Item Frame. Also, UUID support would be needed.
-
View User Profile
-
Send Message
Posted Apr 15, 2014Most of my player's accounts have negative claim blocks! From looking at the GriefPrevention/PlayerData/ player files all the accounts have been reset to 100 claim blocks with a date stamp of 1970.01.01.01.00.00. I do have a backup of the user files but it is after the conversion. So my question is what should be the format of the player files in griefprevention? Here is what I see now:
1970.01.01.01.00.00 100 0 falseand sometimes this
1970.01.01.01.00.00 100 0 <blank space here> falseThe old file format is
I am thinking I can strip out the claim locations as it looks like that has been converted and just replace with "false" Anyone else had this problem?
-
View User Profile
-
Send Message
Posted Apr 15, 2014@sphbecker
Alright, I'll let him know. Thanks!
-
View User Profile
-
Send Message
Posted Apr 15, 2014What access rights are requires to enable users to place minecarts?
Accesstrust was enough in older versions, but the latest one listed here does not allow it anymore
-
View User Profile
-
Send Message
Posted Apr 15, 2014@taylormarek, My guess is that he claimed a large area by mistake and does not know where it is. Suggest that he use the /AbandonAllClaims command followed by reclaiming the areas he wants.
If the problem persists, then as an OP I would use the /DeleteAllClaims command to remove all of his claims from the system, then stop your server, delete his user file found in ./plugins/GriefPrevention/PlayerData and restart the server. At that point, GP should treat him as a brand new player.
You could try the /AdjustBonusClaimBlocks command to give him more blocks, but that is more of a workaround than a solution.
-
View User Profile
-
Send Message
Posted Apr 15, 2014Hi, is there any way to only enable this plugin in 1 world. Thanks!
-
View User Profile
-
Send Message
Posted Apr 14, 2014Have a problem that I hope is a quick fix. Plugin runs fine, but I have one player who says that his claim is stuck at 23 blocks. He can't claim more and no matter how long he plays his claim doesn't increase. Let me know what the bug might be regarding this. Thanks!
-
View User Profile
-
Send Message
Posted Apr 14, 2014Thank you for answering, sphbecker. I have time to play with different ideas as I am waiting until 1.8 is squared away. :) I will try to adapt my ideas to this plug in to reduce the number of plugins I need. My aim is to keep it as simple as possible. Thanks again for answering. :)
-
View User Profile
-
Send Message
Posted Apr 14, 2014@DaisyDigs I am no expert, but do like to tinker, so I can probably answer most of your questions. In the world config file you can set BlocksAcccruedPerHour to 0 to prevent gaining claim blocks with time.
As far as I know there is no direct way to define someone’s initial claim value based on groups, but you can easily use the /acb command to give everyone in a group extra claim blocks (according to the documentation this is a persistent command and will grant blocks to new players added to the group later).
You can set the AutomaticNewPlayerClaimsRadius in the world config file smaller if you want (I am not sure if a value of 0 for single block is allowed), keep in mind that it may take new players a while to get a Golden Spade to expand it, you might want to provide that as part of a free kit or change the trigger item (I use flint on my server). It sounds like what you might want is a simple chest locking plug-in and disable the automatic new player claim all together.
GP can’t do the kind of chest protection you are talking about, I consider adding a check locking plug-in in addition to GP. Players can grant sub-division within their claim to allow someone else to place a chest, but the main claim owner would also have access to the chest and would have to setup the sub-division before the other player could place the chest.
-
View User Profile
-
Send Message
Posted Apr 14, 2014Would it be possible to fix the claim expiry?
Its not worked for months, nearly a year in fact.
It would be really useful for cleaning up the map.
I have it all setup perfectly it just doesn't work.
It expires chest claims, but thats all.
Thanks!
-
View User Profile
-
Send Message
Posted Apr 13, 2014@Tydron123
I mentioned that in my previous comment too. Seems like it's broken.
-
View User Profile
-
Send Message
Posted Apr 13, 2014Hi! So in my Permissions i used these commands -griefprevention.admineavesdrop - griefprevention.eavesdrop - griefprevention.ignoreclaims - griefprevention.lava - griefprevention.loginspam - griefprevention.spam
But For some reason only the OP'd people on the server can use /ignore claims etc. Help me please!
-
View User Profile
-
Send Message
Posted Apr 13, 2014Hi there - I am planning a server and I love this plugin. I need to know if, instead of allowing a player to accrue blocks based on time, a set number of blocks may be allotted based on a player's group? Also, if I set it that a NewPlayer claim (with the chest) claims only the chest, I need to know if the player can protect a chest placed on another person's claim? In other words, if a new player is given permission to live in another player's claim, can his chest still be protected if he places it there, or can the other player automatically access it? Thanks for any help you can give me. :)
-
View User Profile
-
Send Message
Posted Apr 13, 2014Thank you for an awesome plug-in. I run a tiny privet server and GP makes keeping people honest as easy as downloading a file.
My only real complaint is that claim boundary marker blocks become a nuance and seem to be displayed far more than needed. It would be nice if when the player is not holding a Golden Spade or Stick, those fake blocks had a maximum display time of 5 seconds. A slash command allowing players to toggle the automatic displaying of those blocks (like when they build out of their claim area) would be nice too. Last suggestion, deselecting a Golden Spade or Stick should remove all fake blocks.
Otherwise, it is an amazing plug-in. Does exactly what it needs to.
-
View User Profile
-
Send Message
Posted Apr 13, 2014UUID's are here, any timeplan for adding 1.7.8 support?
-
View User Profile
-
Send Message
Posted Apr 9, 2014Hi. I am helping one of my friends on a server getting ready for 1.8 and he wanted a way to contact you about the plugin. if possible, email me at albiehoheb94@gmail.com.