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 Feb 29, 2016Please do not update your production server and then come running to me with your hair on fire, because I do not have access to a fire extinguisher at this time. Check things out on a test server first, then update only if you're feeling confident. I will be able to code on GriefPrevention again when I can get my development computer out of storage and also find space to set it up and code.
I have heard anecdotally that there are no major issues with GriefPrevention in 1.9, based on testing done in SpigotCraft.
Hi all, this always happens to me - when a major update finally releases, I'm unable to code! The last two times I was out of town on vacation, this time I'm between houses and my development gear is in storage for the next couple of weeks. This means if there are any new griefing issues related to 1.9 changes, I'll be unable to react to them immediately. PLEASE poke around on a test server before updating your production server to check for any serious issues, since I won't be able to code up a fix as quick as I'd like (and please do report to me any issues you discover, so I can get them all fixed as soon as possible after I get access to a computer I can dev and test on). For example, 1.8 added leads which were a new way to steal animals, and hoppers which could (situationally) steal from another player's chests. There may also be changes to the Spigot/Bukkit API which cause features which work correctly on a 1.8 server but which don't on a 1.9 server, like for example the time a Spigot update broke all protections for armor stands, allowing any griefer to destroy any armor stand until I made a code change.
@unclemark
Nope, I'm not turning off flying for anyone in any case.
@Strika92
You have to reboot your server after changing messages.yml. Please back up your file first in case you made a syntax mistake, which would cause it to revert back to defaults.
@The_PC_Tech_Guy
Please tell me about those minor issues. :)
@DeGariless
Mod items won't work - it has to be an item Bukkit knows about. Sorry! I'm considering changing it.
@bremdecoolste
I think you want something like GriefPrevention.instance.getClaimAt(location). Returns null if there is no claim there. There are other parameters, see code comments on github.
-
View User Profile
-
Send Message
Posted Feb 27, 2016What is the hook called to check if land is claimed, if I were to call it from another plugin (tp plugin)? Something like ==== if AreaIsClaimed == notpblabla else blabla ====. In this case, what is the correct hook for AreaIsClaimed?
-
View User Profile
-
Send Message
Posted Feb 26, 2016from console in our main world the command is fly <name> on
but when they go to grief prevention world they can no longer fly.
-
View User Profile
-
Send Message
Posted Feb 25, 2016I am trying to use a mod item in place of the golden shovel, however, whenever I save the config file and do /gpreload, it automatically changes the config file back to GOLD_SPADE. I have tried BiomesOPlenty:ancientstaff:3, BiomesOPlenty:ancientstaff, 4741:3, 4741, ancientstaff, and ANCIENT_STAFF. How do I use the config file to change the modification tool?
-
View User Profile
-
Send Message
Posted Feb 25, 2016@CloakedAlien
You can test it right now on SpigotCraft, there's only a couple of minor issues but will work as-is in 1.9
-
View User Profile
-
Send Message
Posted Feb 25, 2016w00p. Seems like 1.9 is slated for release monday 29th of February and a Spigot update the day after. Fingers crossed we'll see Grief Prevention updated as soon as possible as well. Very well timed with me wanted to get back into MC to help our server players out =)
-
View User Profile
-
Send Message
Posted Feb 24, 2016@unclemark
What command are you using to grant the temporary permission? Also, seems GP does nothing regarding fly status: https://github.com/ryanhamshire/GriefPrevention/search?utf8=%E2%9C%93&q=fly&type=Code
@Strika92
Use commands.yml to map your custom german commands to GP's commands. As for changing the message that appears - other than handling it yourself (in a plugin that uses PlayerCommandPreprocess), you'll have to open the plugin jar file and edit the plugin.yml to change the "usage" and permission error messages.
-
View User Profile
-
Send Message
Posted Feb 24, 2016Hey guys, i want to use GP on my server in german so i translated the messages.yml to german but ingame all commands are still in english. how i can activate that gp load the messages.yml and show me the commands in german?
thx for your help :)
-
View User Profile
-
Send Message
Posted Feb 24, 2016Thanks for your wonderful support in the past. It has helped. However, I have one more issue. Using Spigot and Multiverse, I can set it up so people don't lose /fly when they go to other worlds, but when they get to our 'Claim World' they lose fly ability and have to ask staff to turn it back on for them. (temporary permission). Is it grief prevention that turns off fly automatically? How do I fix it going from one world into a /gp survival world and have people keep their fly status? Thanks again for you previous help.
-
View User Profile
-
Send Message
Posted Feb 23, 2016Hi big_scary, unaware if you've checked your Spigot page... More like pages... :S But other than that hope you're doing well!
-
View User Profile
-
Send Message
Posted Feb 23, 2016@AquaXV
Hmm... if you can "catch" this problem in the act, send me your claim data file and the coordinates of the claim where you're having a problem with subdivisions. All I can promise is to do your steps and reboot, then try to see the problem. :\
@unclemark
Essentials allows this (other plugins overriding its commands) by default, but you can disable that in the Essentials config file.
If you don't want to do that, you can also use your commands.yml (see Bukkit wiki) file to redirect /pt to /essentials:pt.
@DNDev
I don't think this is about GriefPrevention - it doesn't do anything to set/unset/change permission nodes. I'm betting you just need to fiddle with your group manager settings some more. What do you mean by promote builders - do you mean that you've used /trust with a permission node, and now you want players to add other players to that permission node?
You didn't answer my question about whether or not players get a message from GriefPrevention when they press a button to activate a command block and it doesn't work.
@foxi69
Yep, what Bobcat said. Just set all of those to false and PvP will be on everywhere. If you also want to allow spawn camping, that's a separate PvP rule you can also turn off in the config file.
-
View User Profile
-
Send Message
Posted Feb 22, 2016@foxi69
I believe you want the following:
Alternatively, you could disable PVP rules entirely in your world.
-
View User Profile
-
Send Message
Posted Feb 22, 2016how can I enable the pvp anywhere ?
so on the unprotected block same dmg as protected
-
View User Profile
-
Send Message
Posted Feb 21, 2016Hello. It's me again, and this time with a possible conflict. I just configured ranks with GroupManager, and prefixes with SimplyPrefixes. I tried to add permissions to each rank, so that admins and mods could promote builders and such, however after giving them the permissions they couldn't use them. Could this be a conflict with griefprevention? Better Put: Do you know if I should I be altering YML files in greifprevention or groupmanager?
Sorry if it seems I am asking a lot. As for the command blocks, the buttons still don't work, but I am using pressure plates so its fine. Players can still use buttons themselves to open doors and such, just nothing with command blocks.
Thanks again.
-
View User Profile
-
Send Message
Posted Feb 21, 2016/pt alias (permissionstrust) overrides /pt (powertools) from essentials !! Can you fix it so the aliases can be changed ?
-
View User Profile
-
Send Message
Posted Feb 18, 2016I am having a slight issue; For some reasons the subclaims sometimes dont save correctly and subclaims of an adminclaim sometimes kick their trustees off taking away their access.
I am not using a database, have 16.5k playerData files, and 3k claimData files. Only changes made to the config are in numbers of total claimblocks, height of claim, expire duration and claimblock gain speed.
No errors are shown in console on neither startup nor shutdown. We do not use /reload, ever. We currently run version 13.9.1. We have WorldGuard and Vault installed.
If you need additional data let me know :) It is just very annoying this keeps happening.
-
View User Profile
-
Send Message
Posted Feb 17, 2016Sorry to keep you all waiting, two sick kids + trying to move this week.
@crane0002
The default setting protects players from pvp in all types of land claims, BUT if a player starts fighting outside a protected area and then runs in, he will still be vulnerable for at least a few seconds, and will continue to be vulnerable until he hasn't been in combat for a while. Check your config file to make sure you have pvp rules turned on for that world.
@bikkit_User6372
Increase the IP addresses per player limit in the config file.
@DNDev
Hmm... this has me stumped, I'll have to try it myself. You're attaching a button directly to the command block, and the command block executes an administrative command when activated? You're pressing left click or right click to hit the button?
Your expectation is correct - you should need only /accesstrust in that subdivision.
EDIT: Did you try without any claim at all? I wonder if it's a nuance of command blocks. Also when another player can't press the button, do you get an error message from grief prevention, or nothing at all? If GP is interfering, you'd definitely get a message.
@jhmaster2000
In your config file, there's a worlds list. Make sure it's set to something other than "disabled" for that world. This is covered in the setup/config page.
Votes aren't valuable anymore, I'm thinking about just dropping that ask. But thanks for your consideration. :)
-
View User Profile
-
Send Message
Posted Feb 14, 2016@jhmaster2000
Calm down. Bigscary, the Developer comes on about once a week to answer questions here. I don't doubt that Bigscary is a busy person. Being impatient will not improve the chances of you getting an answer, you'll just have to wait. Also I am sure there would be someone to vote in your place, as this is a great plugin.
I am waiting too, as I have before. Like everyone else I will have to wait to get my questioned answered.
-
View User Profile
-
Send Message
Posted Feb 13, 2016Incompatible With Multiverse?
I Try To Create Claims On My Server But It Says: Land Claims Are Disabled In This World
Please Tell Me How To Enable Claims On a Multiverse World
Thanks
-
View User Profile
-
Send Message
Posted Feb 13, 2016Hi! Thank you for this wonderful plugin. I see why you have pages upon pages of 5-star reviews. However I have found one problem that I can not find the answer to. Command Blocks. I am trying to make an area where newbies have to answer a question (By pressing the yes/no button). Depending on what answer they choose and what button they push, a different thing happens. Either they get TPed back to the rule area or they get TPed to the next question area. This filters out the noobs who skip the rules and have to ask how to play. However I put this area in a claim, and now only I can press the buttons and have the TP work, even after I do /accesstrust public and /containertrust public. I even tried /trust public in general but the command blocks only work for me.
I should also mention that the area is a subdivision. That may be the problem as I dont want to allow accesstrust in the main division.
Also if this doesn't work for buttons might it work for pressure plates? EDIT: Pressure plates work, but still not buttons.
Thanks for taking the time to read, and I look forward to your answer. ~ Isiah, Manager of DNMC