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 27, 2015Is there a way to disable "pets" completely? It messes with my mobs (villagers) in claims and other stuff. I would love to disable this feature as I don't like it and it is not in the config.
Thanks!
-
View User Profile
-
Send Message
Posted Apr 27, 2015Is there a permission node for the being able to see signs and such? So that I don't have to op those who are staff but still allow them to able to see signs that players place?
-
View User Profile
-
Send Message
Posted Apr 27, 2015@Hirushika
Just update to 1.8. Bam problem solved.
-
View User Profile
-
Send Message
Posted Apr 27, 2015Hi! There is about 180 versions of this plugin, but i couldn't find any for 1.6.4. It's strange. Can you answer, is there is 1.6.4 support, on what plugin version or will it be sometime?
-
View User Profile
-
Send Message
Posted Apr 26, 201511.5 Updates
@EpicATrain
My wild guess is that your sudden power outage resulted in data corruption, which then lead to your later crashing problems and the odd data files. If you have any backup data, I think that's your best option. Otherwise, you might experimentally move those two larger claim files out of the claim data folder to see if it solves your protections and crashing issues.
I'd like more information about the bug you describe. Please share the logs or any other information you have that lead you to believe that GP was the reason for your crash.
@GodsDead
I'll definitely look into this - please link me that complete report. That image alone isn't actionable for me, gotta have more specifics and some overall server state context.
-
View User Profile
-
Send Message
Posted Apr 24, 2015Another strange one, GP running tasks at 27,000%.
-
View User Profile
-
Send Message
Posted Apr 24, 2015Hey, we have the weirdest thing happen... we had players be able to grief and other stuff in other player's claimed plots so we had to shut the server down. Earlier in the day we lost power to the server room and we didn't have an UPS to save it in time so we lost a lot of data. Upon coming back up, everything worked fine, and all was well. The server soft-crashed due to a grief-prevention bug (we were using an old version) so we decided we were going to use a new version. After that crash is when we discovered that players could grief others. So we shut down the server and call it a night and fight it in the morning.
I went through the server files and found 2 claimdata files that were not like the rest... this one listed below is 320 KB and the other one is 4 KB, while all the other ones are 1 KB. I'm wondering why these 2 files are not like the rest.
http://pastebin.com/fVzQ2WR0
-
View User Profile
-
Send Message
Posted Apr 22, 201511.4 Updates
If you love GriefPrevention, please help out by leaving a positive review on GP's Spigot page. :) Thanks!
@Jikoo_K
Thanks! I'll investigate today.
@Emalton
Glad you figured it out. :) Thank you for the compliments!
-
View User Profile
-
Send Message
Posted Apr 21, 2015This is a very good plugin, it's really awesome. I do however get an error on boot. It's probably something on my end. Anyone ever see: Plugin GriefPrevention v11.3.2 has failed to register events for class me.ryanhamshire.GriefPrevention.EntityEventHandler because org/bukkit/event/block/BlockExplodeEvent does not exist.
EDIT: I updated the jar file. (Re-Compiling BuildTools)
-
View User Profile
-
Send Message
Posted Apr 21, 2015Minor complaint - when a player with permissiontrust untrusts another player, they receive a message "Only <owner> can revoke permissions here" but /trustlist shows that the trust is removed as expected.
-
View User Profile
-
Send Message
Posted Apr 21, 2015@jackv1999
Please use pastebin to share your config file with me. By default, all players have that permission - unless of course your permissions plugin is doing something odd.
@GodsDead
I'll work on that /sellclaims change.
I'm not sure about that "crazy resizing" problem. I've never been able to reproduce it, so I'm not sure I understand where it's coming from. When players experience this, are they perhaps trying to resize onto the surface of a body of water? How long has it been since you updated your server jar? It could also be a spigot bug I recall from months ago.
I hope to get the explosions config investigation done this evening.
I'll think some more on the siege thing. Maybe a limit on # of sieges per hour like you suggested can work.
There's no recurring task to check claim blocks. However when a player gets out his shovel or runs /claimslist for the first time after logging in, I do check to see if he has at least enough total blocks for all his land claims, and if he doesn't, I adjust his blocks so that he doesn't have a negative total anymore.
@dutcholdskool
Sure, I've added that to my todo list. :)
-
View User Profile
-
Send Message
Posted Apr 20, 2015Hi Bigscary,
Any change you can modify the /acb command to allow UUID?
-
View User Profile
-
Send Message
Posted Apr 18, 2015Hello, I just installed this plugin on 1.8.3 but I have problems with my claims. It looks like the the claim is created since a player can't destroy/place blocks and chests are protected, but TNT destroys blocks and player can kill animals inside the claims (with any weapon). I also tried to reinstall the plugin .... but nothing. Any suggestion to fix? Thanks!
-
View User Profile
-
Send Message
Posted Apr 18, 2015@bigscary
/sellclaims Yeah you fixed the initial issues previously, There's just one tiny modification needed; Allow Earned block to be sold, In the right way! People can sell their Acquired Blocks over time, BUT they should never be deducted from the aquiredblocks column from the data storage, They should be deducted from bonusclaimblocks and a calculation made, So bonusblocks should be able to go into negative numbers! Let me give you an example, I have 300 Acquired blocks, 0 Bonus Blocks and I have spent 200 of these blocks on claiming land; I decide to sell the 100 free blocks I have, this is de-decuted from bonusblocks. So the database would show aquiredblocks: 300 bonusblocks: -100, This is how the old GriefPreventon worked. Since all free claim blocks are calculated, you just change it to something similar to this $freeclaims = $aquiredblocks - $used_on_claims + $bonusblocks, When you add the bonusblocks as a minus it will deduct them! I hope this makes sense, Aquiredblocks data should never be adjusted, All adjustments are handed in bonusblocks.
Subclaims getting deleted when master claim resized: Would this also fix the issue with Resizing issues just going absolutely nuts when you try to resize? This keeps happening, where a player goes to resize their claim, and it just randomly reduces the claim size, resizing it instantly, as if the player has clicked twice, its infuriating.
TNT not working in the wild: Yeah, whatever happened in the update to fix other explosions destroying claims, Now made TNT/Other explosions not work at all in the wild, its either destroy everything, or destroy nothing, theres no middle ground where claims are protected.
For the players getting repeat sieged by multiple players This is a hard one to fix, how about there is variables in the config to set the amount of times you can be sieged in a time limit from different players? Theres got to be a way to stop players getting sieged over and over for hours on end by a group of players making them quit the server, ive had this happen over 20 times now.
Claim block vanishing I deleted this as I did the calculation, and the players claims worked out about right, But it did show them different results over 2 days, a few thousand block difference, I have no idea why the plugin could do this, All I can assume is that you have a recurring function that goes through all players and checks their claim blocks?
-
View User Profile
-
Send Message
Posted Apr 18, 2015Hello.
I downloaded this plugin and when I right click with a golden shovel this comes up. http://prntscr.com/6v6sg7 I can't find the default permission nodes to add them am I doing something wrong? Please help :) Note: They don't have access to things like /trust either.
-
View User Profile
-
Send Message
Posted Apr 17, 2015@alyurbeis
That's a spigot/craftbukkit bug. You have to update your server to the latest (rerun buildtools.jar).
@CrypticCabub
When other players who have that permission node log in,they will find that they also have the bonus blocks you assigned.
@GodsDead
I thought you told me you didn't want them selling accrued blocks? Or did I misunderstand, and you meant that it's fine for players to sell them accrued blocks as long as they don't accrue them back?
You cannot delete trust for a player that hasn't been on in a while, maybe to update their UUID from the conversion. This one I can't fix. The cost of looking through all players who've ever been on the server before is so high that it will crash some servers. :( I logged a bug against the spigot team for this when they first released 1.8, and they still haven't done anything about it.
Sometimes Subclaims get deleted when the master claim is resized. I believe this is due to a fixed bug which caused SOME claims to get corrupted while it was still alive. The bug has been fixed, but the claims are not automatically repaired. If you delete and replace them (yes I know this is a pain in the ass), I expect they'll be permanently fixed.
TNT is disabled everywhere, it does not do any damage in the wild, and if I turn on "BlockLandClaimExplosions" this makes them work again, but also destroys claims! We need an option to turn on TNT in the wild. I thought I thoroughly tested different combinations of the explosion settings, but I'll check again that this configuration works.
A player can be sieged over and over again by different players, You mentioned a friend sieging them to add a cooldown; at least make it togglable, so we can deal with troublesome players, this would only be a select few. In what way do you want it toggleable? Do you mean a config option, or a per-player permission? Please go into a little more detail here so that I don't code up something and find out I misunderstood the ask.
EDIT: If a player doesn't want to be besieged, why is he even playing on a server with siege mode enabled? He should be excited for the opportunity - there are so many ways to win even against overwhelming odds, because he has the home advantage. Hidden pitfalls and lava dispensers to kill his enemies. Build an escape tunnel to sneak out. Throw an ender pearl over their heads to get a head start so they can't catch you. Go out and fight them. Add arrow slits so you can shoot at them from relative safety. It's a solvable problem that the player should be working on, not you - don't you think?
Random players have their claim blocks vanish without claiming or doing anything to change their claim blocks, One of my staff members claim blocks has gone from 6000 to 250 from last night to today. I have zero idea what could be causing this, or where to start looking. Adding to the puzzle, no one else has complained (noticed?). I will keep thinking about this and try to come up with something. In the meantime, I'm already working on more detailed logging that may provide some hints.
-
View User Profile
-
Send Message
Posted Apr 16, 2015@bigscary
Yes im in Database mode, I figured out the /sellclaim issue, Its actually something ive already covered a few times, so I feel a little rude repeating (sorry).
We have also found some more bugs to add on top of the ones I already reported, so Ill update the list here:
-
View User Profile
-
Send Message
Posted Apr 16, 2015@CrypticCabub
If you are in linux you could change the appropriate line in each GP player file via batch script, like:
for all files in GriefpreventionData/PlayerData do
// get the 2nd line (bonus claim blocks)
bonusblocks=`head -2 <file> | tail -1`
// add x to it (the number you want to give each player...here e.g. 10)
bonusblocks=$(($bonusblocks + 10))
// replace the old bonus claim line (line 2) with the new one
sed '2 c\ > $bonusblocks' <filename>
Needs a bit trial&error to get this running as it should I guess as I am always not sure about the correct syntax. But should be the easiest to do something like this when server is down (e.g. in a restart).
-
View User Profile
-
Send Message
Posted Apr 15, 2015Hey, it's me again :)
Turns out /acb [permissions.everybody.has] {amount} is only assigning claim blocks to people who are currently online. Is there any way I can assign claimblocks to everybody (online and off) at a set time without having to maintain a list of all students on our servers? Hoping to be able to schedule the command to assign claimblocks every weekend.
Great plugin, thanks for all the hard work. God bless, CrypticCabub (VicePrincipal_Cryptic, MinecraftHomeschool)
-
View User Profile
-
Send Message
Posted Apr 15, 2015@bigscary
Haha, yeah I already updated and it works successfully. I told the same to @Shayd713.
Thanks! ;D