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 8, 2012Hey guys thanks for the bug reports, I'm gonna fix it asap.
On the auto claim thing, having lots of tiny claims is a bad thing for performance, and because claims can't overlap, they wouldn't fit together well in lots of places. Also, allowing griefers to create claims easily without a shovel can be disastrous.
The reason we can't do a limit for claim count is because often, a player will make a small claim and outgrow it, but then find that he has neighbors so he can't expand. WIth a claim limit, players like that will end up in a situation where they have to choose between abandoning their hard-won build to griefers, and going to another server to build more.
Thanks very much for the suggestions!
-
View User Profile
-
Send Message
Posted Apr 8, 2012Midnighte: You get the message that you are charged, but if you remember remaning blocks before and after the usage of /ac you will find out they are same. eg you are not charged.
This does not apply if you are resizing a claim. If you are resizing a claim, the claim are ALWAYS charged to the original claim owner, regardless of /ac or /bc. (if the claim is originally a adminclaim - then its not charged)
BTW Suggestion 1: A possiblity to limit *number* of claims a player may own, regardless of size. In this way, "griefing" by placing many unneccessary small claims can be prevented by this limit and then its safe to give the players higher "accruedblocksperhour", initialblocks, and its safe to reduce the "minimum claim size" too.
BTW suggestion 2: A "autoclaim" mode: Can be in configuration: "autoclaim: true" or "autoclaim: false" When the plugin is in Autoclaim mode, every chest player places will award a "initial claim" assuming player still hasn't consumed all claims or blocks he may place, and assuming the chest isnt already placed in a claim player owns. Golden shovel is never used and have no function in "autoclaim" mode. (except for admin claims, where autoclaim mode will have no function and golden shovel is always used) To extend the claim, you simply put any placeable block/item on the claim boundary. This will then cause the claim to extend in that direction with one block (assuming you have enough blocks to extend your claim). Blocks placed outside of a claim have then no effect. If you put a block in a corner, both sides of corner will then extend. In this way, player don't need to think of the claims, they just build and the claims resize of their own. A warning in chat could be issued if the player places a block on the boundary and don't have enough blocks to extend the claim: "WARNING: If you continue to build in this direction, the blocks that extend out in this direction will not be protected from griefing".
The small problem I have on my server is that players never realize they need to resize their claims when their buildings get large. Thats why I suggest a autoclaim mode.
-
View User Profile
-
Send Message
Posted Apr 8, 2012I noticed that /ac does admin claim mode, but when I claim stuff it charges the user using /ac instead of not charging at it suggests.
-
View User Profile
-
Send Message
Posted Apr 8, 2012@DrFusion I re-enabled logblock so i could undo changes easily.
-
View User Profile
-
Send Message
Posted Apr 8, 2012@Midnighte
that happened to my server >.<, good thing i still have worldguard :D
-
View User Profile
-
Send Message
Posted Apr 7, 2012@Adondriel
You can't have /siege without land claims. Is that what you're asking for?
@Confuzzled77
Everybody has permission unless you enable the "claims require permission" config option.
@DrFusion
That config variable doesn't do anything anymore. Just delete it. If you want to turn PvP on or off for your whole server, use server.properties. For specific worlds, use another plugin like WorldGuard or Essentials to set those options.
@DrFusion
/IgnoreClaims
@Ignitor0
No, there's no group support. You can grant permission for everyone or for single players, but not for groups defined by other plugins.
-
View User Profile
-
Send Message
Posted Apr 7, 2012@leezallen
Yep will be happy to link from here. :)
-
View User Profile
-
Send Message
Posted Apr 7, 2012Let's say that I have city protected by Grief Prevention. Inside the city, there're lots of buttons, levers, chests, etc. I want that all users that are in Members group can use them but they can't build or destroy any blocks. Are there and commands to do this?
Because it's very inpractictal to add by single user.
-
View User Profile
-
Send Message
Posted Apr 7, 2012admin bypass command?
-
View User Profile
-
Send Message
Posted Apr 7, 2012@TaterTotsYum
I thought that I would look at economy using Vault supported plugins seeing as it is used for GP! Then maybe items after that if there is enough interest..
I will create an official page for this today to keep the chat of this page!
Lee
-
View User Profile
-
Send Message
Posted Apr 6, 2012PvP: Enabled: true
is that if pvp is enabled in claims or globally?
-
View User Profile
-
Send Message
Posted Apr 6, 2012@mrcheesete0
That works i guess.... lol
-
View User Profile
-
Send Message
Posted Apr 6, 2012Then set claims to require permission, and dont give anyone the permission, set tree top protection to false, set spam protection to false, and just use the PVP and Siege.
-
View User Profile
-
Send Message
Posted Apr 6, 2012@bigscary
I mean i don't want the grief prevention, i want the PvP prevention!(along with seigeing)
-
View User Profile
-
Send Message
Posted Apr 6, 2012Permissions to create claims?
-
View User Profile
-
Send Message
Posted Apr 6, 2012@leezallen
What will you be using as currency? items or iconomy ect. I'm looking forward to your plugin! :)
-
View User Profile
-
Send Message
Posted Apr 6, 2012leez let me know when you finish.
-
View User Profile
-
Send Message
Posted Apr 6, 2012@bigscary
Have now been using this mod since the early days and still think it is the best solution around but now it is time to give something back! I am working on a plugin using the API for the buying and selling of claims (eventually leasing)! As soon as I have something will you link from here? It is going to be a good 5 days or so.... my Java is rusty!
-
View User Profile
-
Send Message
Posted Apr 6, 2012@bigscary I watched them all, and didnt get any answers on that, but ill look again in a few minutes. edit: I read my post again, it should say that are not square/rectangle. Similar to that found in faction.
On a second note, be able to give titles to people who live within your area.
-
View User Profile
-
Send Message
Posted Apr 6, 2012@Adondriel
I don't know what you mean by "pvp logger prevention", or "forcing your users to switch how they protect their stuff".
If what you mean to ask is how do turn off the /siege thing so that blocks can never be broken... the default is to have siege off entirely. Or you can leave siege on, but empty the breakable blocks list.
@Midnighte
Please read the instructions above or watch the 4 minute basics video before asking questions. You'll get your answer much faster.
@Phonix420
Well that's odd. Since I can't control lightning strikes, I haven't been able to test this really. But when I place fire with flint/steel, it does eventually burn out. How long did you wait?