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 Dec 8, 2013Is there a way to give someone a horse you own? I had bred and tamed some horses for my daughter, and now she can't ride them anymore.
-
View User Profile
-
Send Message
Posted Dec 8, 2013@Awsmpossum1313
Untamed Horses Are treated like Normal creatures. Since they are tameable they also should be controllable through the Breeding, Feeding, and Taming rules.
Owned horses:
-Can be attacked by their owner in any circumstance. You should be able to do whatever with a horse you own, after all.
-In the wilderness can only be attacked by their owner. This will probably be changed.
-in claims, can only be attacked if being ridden by their owner, and if the owner does not have any trust on that claim. (Will probably be revised to not require that they are being ridden to be attacked).
-Can only be mounted by their owner (Everywhere)
@danisblack9
Maybe after killing a player you get granted access to his chests, doors etc. for configurable amount of time (5min).
That's called a Seige. It's already implemented. It's configured to allow only X chests to be accessed. Doors and buttons and levers are unlocked for a duration I think is configurable.
@RustyDagger
Allgedly earlier spigot and CB builds had issues raising some events. More recent reports are saying that Item Frames are impossible to break at all by any player with any permission in 1.7.2.
-
View User Profile
-
Send Message
Posted Dec 8, 2013running one of the latest Spigot 1.7.2 Builds items in item frames are not protected inside claims Any player can walk in and remove the item from the item frame.
-
View User Profile
-
Send Message
Posted Dec 8, 2013@freakyy85
-1 is the default level for the world, if you leave it like that it will be 64 for normal worlds.
@BC_Programming
I suggest implementing a check to not create claims inside regions. While your plugin is superb for its simplicity, I still do my admin protections with WG because of all the flags, and it would be nice those two to coexist. (I know I can create public claims on top of my regions, but I propose an automatic solution. :)).
-
View User Profile
-
Send Message
Posted Dec 8, 2013what should i use as safe default sealevel? creepers still do damage on the surface if the surface is below sealevel ... so whats the lowest surface blocks below normal -1 sealevel? maybe -5 or smth? oO
-
View User Profile
-
Send Message
Posted Dec 7, 2013How about the raiding feature? Factions are all about griefing which makes surroundings look horific. Maybe after killing a player you get granted acces to his chests, doors etc. for configurable amount of time (5min). In the config could you add option to disable auto chest claim please instead add a command to claim area the chest would claim and a command to expand land by 10 blocks.
Thank you!
-
View User Profile
-
Send Message
Posted Dec 7, 2013Just a note for you to look at. When using GP-200 with Spigot #1168 we have the following issues with horses:
1. No player can get on them regardless of claim permissions other than the owner. I am assuming a flag for /trust permission ranks will ultimately be added.
2. OP's cant kill, mount, or /butcher the horses. So they are very protected.
Rolling back resolved the issue but I figure you would like to know.
-
View User Profile
-
Send Message
Posted Dec 7, 2013@danisblack9
This goes far beyond the scope of the features we are aiming for. Siege lasts until one of the players dies or the attacker leaves. Special PVP internal scoreboarding (tracking kill ratios) is far beyond the intent of the plugin- it is not designed to replace popular PVP Plugins, just provide a basic alternative for servers that want to prevent grief but want to have PVP. The other stuff has already been requested and rejected- being able to set a home claim is no different than simply sleeping in a bed, and teleport features are provided by other plugins. Naming a claim has no particular purpose, since the name won't be visible anywhere.
@MRLUCKYSHOT11
This is a bug in the current beta release. It should be fixed in the latest build. Expect a new beta to drop within the next week or so.
-
View User Profile
-
Send Message
Posted Dec 7, 2013It would be very appreciated if you could add more commands.
/land claim (claims land 10 more blocks in each direction)
Siege mode should last only 10min no longer
-
View User Profile
-
Send Message
Posted Dec 7, 2013I'm impressed by the plugin. But it misses some PVP options. I want to change faction plugin on my server to grief prevention, but there is no way to raid claims. I dislike all those TNT cannons and lava griefing but at least raiding should be supported in some way. If you plan on making 1.7.2 version of this plugin, you could add features to support PVP and raiding inside claimed lands. Possible feature that should be supported are, PVP in claimed land between both (attacker and land owner), player death ratio (If the player dies 10 times or so you get the option to open their chests and doors etc., each death could be taken back each 10 minutes), player ability to set claimed land teleport (/set landhome) and every time player dies he gets teleported to his land home point, invite players to your land that can use command "/land home", name your claimed land, make all the features I listed configurable in the config incase other people don't want PVP.
Thanks for your time :D
-
View User Profile
-
Send Message
Posted Dec 7, 2013How do I enable worlds to have claims enabled?
-
View User Profile
-
Send Message
Posted Dec 6, 2013I have an error and I'm sure its with grief prevention because eveeytime I remove griefpeevention the erro leaves. The error is that everytime a player dies it says: you are protected from pvp as long as your inventory is empty. Everytime a player touches him it says: you can't injure defenceless players. How can I fix this. Please help. I've tried everything but nothing works. Please please help
-
View User Profile
-
Send Message
Posted Dec 6, 2013@MinecraftLegends_us
There is a way to remove/change ownership, it's built into the Bukkit API. Bukkit handles horses the same way it handles cats and dogs, even though Minecraft itself allows you to ride another players horse, when that happens the original tamer is still considered the owner. Grief Prevention merely prevents you from riding the horse if you aren't the owner.
However, the owner is not part of GP, it's Bukkit. What you need is a plugin that allows you to sell or trade tamed animals. This is a better method for your horse seller anyway because her "product" can't be stolen.
-
View User Profile
-
Send Message
Posted Dec 6, 2013The protect fresh spawns setting keeps getting enabled, even when changing it while the server is not running.
-
View User Profile
-
Send Message
Posted Dec 6, 2013I am confused as to what permission node I need to give a moderator (someone who does not have OP) so that they can view another players claimslist. Using the 7.8 reference I try to provide GriefPrevention.Commands.<CommandName> where CommandName is claimslist, but this adds nothing to the player already being able to use /claimslist by default for their own claims.
-
View User Profile
-
Send Message
Posted Dec 6, 2013I have a player that collects and sells horses. They can no longer do that because all of her horses now belong to her and there doesnt seem to be a way to remove ownership. Can you put an option to disable this in the config?
-
View User Profile
-
Send Message
Posted Dec 6, 2013@LordEcchi
@spblat
Yep, it was discussed a few pages back. It's not GP, it's Bukkit events not being called. The JIRA issue is here:
https://bukkit.atlassian.net/browse/BUKKIT-5020?jql=status%20in%20%28Open%2C%20%22In%20Progress%22%2C%20Reopened%29%20AND%20text%20~%20%22ItemFrame%22
@BC_Programming
Actually I had looked into something similar. The original author probably didn't do it because there is no way in the API to tell where a block's power source is coming from. You can tell if a block IS powered, but not what is powering it, so trying to prevent redstone from outside the claim would effectively block any redstone in the claim.
-
View User Profile
-
Send Message
Posted Dec 6, 2013@LordEcchi
Seconded. Running build 200. Otherwise the plugin seems to be working quite well. Thanks BC for your continued support of this great plugin.
-
View User Profile
-
Send Message
Posted Dec 5, 2013I don't know if this has already been addressed, but I'm running version 7.7 on my 1.7.2 server and players are able to remove items from item frames inside of protected zones by punching them.
-
View User Profile
-
Send Message
Posted Dec 5, 2013@Sargewood
The original developer didn't add that feature because the redstone events fired nearly constantly and destroyed server performance, if I recall correctly.