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 Sep 25, 2013@brian163b
Per below, any suggestions appreciated.
-
View User Profile
-
Send Message
Posted Sep 25, 2013Maybe you guys can save me some time. I'm trying to set it up on a survival server so that nobody can build anything until they place a chest(to setup their autoclaim) or they use their shovel to make a new claim.
How can I do this? If I disable block placement they can't place the chest. Is there a way around this?
EDIT: I am using your latest Dev Build :)
-
View User Profile
-
Send Message
Posted Sep 25, 2013@xDizasterCYx
If you want compatibility with 1.6 and later, use the dev builds.
If you want a Beta/Release version sooner, start paying me like my IRL job :P
-
View User Profile
-
Send Message
Posted Sep 25, 2013update this to 1.6.4, this version is causing some errors,
-
View User Profile
-
Send Message
Posted Sep 25, 2013@GodsDead
No. If the dev build saved in both folders, 7.7 wouldn't be able to read it anyway. If you go back claims, player data, and configuration will be what it was when you last used 7.7.
-
View User Profile
-
Send Message
Posted Sep 25, 2013I could not run a server without this amazing plugin, so thanks developers. Im itching to try out the development version on my small server, is it not wise to test the latest developments on a live server? Also is there a changelog I can look over to see what has changed?
edit: Reading through http://dev.bukkit.org/bukkit-plugins/grief-prevention/pages/7-8-and-later-grief-prevention-configuration/
Edit edit: My actual question is: If I test out griefprevention development versions on a live server, can I go back to stable versions? Even if new claims are created/altered? Do the current dev versions save claim information in both folders?
-
View User Profile
-
Send Message
Posted Sep 24, 2013@BC_Programming
I have confirmed the config file for the world in question has "GriefPrevention.Claims.CreationRequiresPermission: true" and the user's group ("Regulars" in Essentials Group Permissions terms) has no "griefprevention.claims.create" or any other GP permissions at all.
However, the users can still use the golden spade to create new claims. (And also /abandonclaims as well which I believe is supposed to require griefprevention.claims.delete )
-
View User Profile
-
Send Message
Posted Sep 24, 2013@BC_Programming
Apologies for not being clearer. I did in fact leave the "GriefPrevention." off of my World Config reference but was speaking of the same option.
However, I discovered the source of my confusion over the permission. In the page for the newer "7.8 and Later GriefPrevention Configuration" changes that I followed and you also referred me to it states:
"GriefPrevention.Claims.CreationRequiresPermission default:false
When set, Players will require the "griefprevention.createclaims" permission in order to create claims."
Although in the subsequent Permissions section it is clearly now griefprevention.claims.create as you stated.
Thank you for your prompt response and hopefully my identifying this typo will eliminate the confusion for others.
p.s. Although I did begin at the top of this page and follow the new guide as necessary for the dev builds (I too lament many people do not really read thoroughly anymore ;-) ), I would suggest adding a link to the new docs within the "Development Builds" section itself. Like:
Development builds can be found here (link to builds)
Guide for current development builds can be found here (link to new doc)
-
View User Profile
-
Send Message
Posted Sep 24, 2013@brian163b
Neither of those permissions exist.
See Here.
You want "griefprevention.claims.create". As the permission. The Configuration item is "GriefPrevention.Claims.CreationRequiresPermission" in the World Configuration.
-
View User Profile
-
Send Message
Posted Sep 23, 2013Running dev build 172. Have Claims.CreationRequiresPermission set to true and took away griefprevention.createclaims perm. But players can still use golden spade to create claims.
If I'm missing something I hope it's not too obvious. TIA ;-)
-
View User Profile
-
Send Message
Posted Sep 23, 2013@xbenas
For the moment. The poll on this page was created ages ago and seems to be about something along those lines. I plan to make that configurable so that players with certain trusts can be the defender of a siege of a claim they have that trust in.
EDIT: Actually it looks like I might have already changed it, as is, the defender can have Access Trust and be sieged. I don't know if this actually works, though.
-
View User Profile
-
Send Message
Posted Sep 23, 2013@xbenas
It depends. I have around 42 plugins and only 3 or 4 had to be updated
@geekyservers
true fact ;-)
-
View User Profile
-
Send Message
Posted Sep 23, 2013Best plugin ever! I've been using this almost a full year and it has NEVER failed me.
-
View User Profile
-
Send Message
Posted Sep 23, 2013@BC_Programming
If I live in my friend's claim, and my friend lives in mine, does this mean we are siege-proof?
-
View User Profile
-
Send Message
Posted Sep 23, 2013@hellishinc
the ABSORPTION effect was added in 1.6.2. The MCPC version you are running only implements the 1.5.2 Bukkit API, or implements the 1.6.2 API improperly.
That Error is not in the current build.
<<quote>>GP is not generating a "config.yml" anywhere. It also re-adds items that I add to the "world.yml""_template.yml" (possible this was removed?) is also no longer being mirrored.
Edit 2:
Claims are not being saved with the combination that I currently am running. I will revert back to build 95 which was stable for 152 and do some more testing. <</quote>>
All of these are because the MCPC version you are running doesn't implement the 1.6.2 API properly. If it implemented it properly the PotionEffectType.ABSORPTION field would not be missing. Chances are it implements the 1.5.2 API and has 1.6.2 Forge support or something to that effect. This breaks everything else because the plugin was only really half-initialized. When the exception occurs control skips over every piece of initialization logic and jumps right back to the Bukkit's Exception handler. No events are registered as a result, as far as I can tell, and generally nothing working in such a case would not surprise me. It occurs before any configuration information is saved.
@xbenas
It depends on the plugin. Many plugins- GP is one of them- use the Bukkit API and nothing else. Some plugins need to use things outside the bukkit API, and access internal Minecraft classes. If a plugin uses internal Minecraft classes it will need to be changed. 1.6.4 doesn't, as far as I know, change anything API-wise, so GP should be fine. I updated my test server to the 1.6.4 CraftBukkit dev build and GP still runs fine.
-
View User Profile
-
Send Message
Posted Sep 23, 2013@ThisUsernameIsMine
Seems like most of my used plugins don't spit errors even tough I am using 1.6.4.
Is this normal, since it doesn't really differentiate from 1.6.2, or am I just lucky?
-
View User Profile
-
Send Message
Posted Sep 23, 2013@xbenas
Yes. If not, try the latest dev-build @ Jenkins.
-
View User Profile
-
Send Message
Posted Sep 23, 2013Working in 1.6.4?
-
View User Profile
-
Send Message
Posted Sep 22, 2013@EmberC
It works on a ratio. 1.0 = 100% return. So 90% would be 0.9.
Aside from the missing features for 16x build 95 is working almost flawlessly.
I had this error with the new builds as well. How can I make it recognize the "interesting" metavalue that ChickenBones uses? I'm sure i could use a wildcard but then that would also protect his enderchests which for some reason mess with the way the chest works. (Using a diamond on the chest makes it private. GP seems to not allow this and the contents are still interactable by anyone even if the chest is containter protected.)
edit: These are some results for when the config breaks (not being created).
131: not created.
127: not.
126: not.
125: created.
123: created.
116: created.
So it seems that 126 is when the creation of config.yml stopped working.
-
View User Profile
-
Send Message
Posted Sep 22, 2013What do i need to set the AbandonReturnRatio: 0.0 variable to in order to return claim blocks to their previous amount?
If I claim 20 and abandon it I want those 20 to be returned.