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).
I have been having issues with having people destorying under claims. I changed the setting in the config to not allow it but it keeps working and being destroyed. Is there something I am not doing right?
Happy Halloween! Update 13.0 is here! :)
@CloakedAlien
Yep, I found and fixed a bug. EDIT: More accurately, GodsDead found it, and then I fixed it.
@TysonMan101
Use your server's commands.yml file to force the server to map /tr to the command you want to run, like pluginName:trCommandYouWant.
@GodsDead
Odd, let me look into that for you. :)
@TysonMan101
You can remove the /tr alias by editing the GriefPrevention.jar file (with something like WinRAR). Change the plugin.yml file to remove the aliases line for the trust command. You can also change it to aliases: []
./ac no longer works for admin claims, can you please fix this.
I had a quick question. SO i have read the page on how to disable grief prevention in a world. But How do i disable all of it's commands in general. I have tnt run on my server and /tr is tnt run's main commands it grief prevention always messes up and things players want to trust people to their claims. This leads to players complaining that they can't leave the map until they actually relog on the server. Does anyone know how to fix this or is it un-fixable. Or do i need to bungee cord the worlds into server for it to work?
Did you change anything to the database code? The disappearing claim blocks issue seems to have gone away.
Only thing I could possibly have done is to use separate db users for logblock and grief prevention.
@boopidoop
Nope, sorry not supported. :\ You'll have to struggle through another plugin for that, like WorldGuard or Residence.
Hello! First off, love this mod. We use it on my friend's server, and it works really well for it. There is one slight issue though; One thing we want to have at spawn is a multi-storey mall. I'm not sure if a comment about this has already been posted, but is there any way to make separate protections on the same y coordinates? If not, then people will have to share :P
@AriKira
I would like to see table prefixes added too, Its the only reason I haven't gone to mysql for GP yet.
Update 12.9 is here! :)
EDIT: Re-released as 12.9.1 because I stupidly left in some debugging code. Sorry! :\
@GodsDead
There's no cheap solution to the nether portal problem. Because nether portals often connect to existing portals offset from the easily-calculated mathematical destination, the only way to find out for sure where a portal is going is to ask Minecraft, which is very expensive. If you want to do that anyway, there's a config option to require build permission before creating generating a new nether portal by walking through an existing one.
Anyway, it's a smallish problem - maximum damage is either creating a portal that's easily moved by a land owner with a diamond pickaxe, or gifting a convenient portal to someone who doesn't yet have the diamonds to create one for himself.
@jahangir13
Yes, but at the time of teleportation, we don't know whether that teleport was initiated by the player through some command like /tpa, or by the server for a different reason. This protection would have to be somehow scoped to specific commands available to players, since there are other reasons a player will teleport which shouldn't necessarily require any permission, like using /spawn to teleport back to the server's spawn point for example. In that case, the player may not have /accesstrust, but that shouldn't stop him from going back to the spawn. GP already has a list of commands requiring access trust to use, but those of course use the player's current location, not the destination because we don't know in the command preprocess event handler.
@bigscary
Ah yes, it appears I was using 12.6 and the 2 'near player' options were missing from the PVP section of the config.yml. (I am pretty sure I have seen these options in the past)
I have now updated. to 12.8
Thank you bigscary
@bigscary
If I understand the problem (Request 1) correctly there should be an EntityTeleportEvent sufficiant which checks for a player and checks if the teleport_to location is within a claim he is allowed to tp to (then allow the event) or not (cancel the event). So no need to check locations in other plugins files I guess.
@GodsDead
I don't understand why these examples are problems. So what if someone gets into someone else's base. They can't grief it anyway.
@bigscary
Superb, An Essentails fork is as active as ever, its under a new name EssentialsX has been for a while: https://github.com/drtshock/Essentials/ Essentails is still one of the most popular plugins across most servers, I wasn't aware of any other way the last position was saved apart from this place, maybe its in the players data? Im not sure i've never looked!
Request 2 Nether portal position checking, People are calculating where to put nether portals in the nether, to Grief and break into Claimed bases, A quick calculation to where the new nether portal would be placed on the overworld could check to see if the player has build permission in claimed land.
@Goldentoenail
I'm confused - is this problem resolved, or are you saying that when you looked for the config option after seeing my message, you didn't have it? Be sure you're on the latest version - that config option was added very recently.
@GodsDead
Will try to think of a good way to do that. Digging into another plugin's data is a mess, and when I'm done the feature will only work for that one plugin (one which is officially discontinued, which will drastically reduce how many use it in the future).
Request Do a lookup in essentials data for the "lastlocation" position when checking for /back, to see if that person is trying to teleport into another players claim, if they don't have trust there then they should be denied the teleport.
@bigscary
Thank you for replying.
The option AllowLavaDumpingNearOtherPlayers was missing from my config.
@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?
The 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?
Update 12.8 is here!