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 17, 2013@Odense36
Yes, you can use the /adjustbonusclaimblocks command on a permission. New players to get this permission will gain the blocks after the command. People who lose that permission also lose the bonus claim blocks.
-
View User Profile
-
Send Message
Posted Sep 17, 2013This is a nice plugin!
I was wondering if it's possible to limit a normal member's claimed plots and make it higher for VIP's?
-
View User Profile
-
Send Message
Posted Sep 17, 2013This is the most amazing plugin i've ever seen
-
View User Profile
-
Send Message
Posted Sep 17, 2013@Durell_1011
use /accesstrust public
-
View User Profile
-
Send Message
Posted Sep 16, 2013@BC_Programming
Yeah but it would be hard to do that with every single player? Is there a solution for groups?
-
View User Profile
-
Send Message
Posted Sep 16, 2013@Durell_1011
Give them access trust in the claim.
@Smac3223
No ETA. You can use the dev build. I'd say a lot more care is taken with the dev build than with the Beta Releases of some plugins.
Main reason I'm not just relabelling the development build is because before it goes beta or release it needs to be well documented and I'll have to pore over the existing pages and update them to reflect changes I've made. Another reason is that if I did update or even release a beta version I imagine there would be an influx of tickets and comments that would require attention, and as it is my IRL job is in a bit of a "death march" trying to rush through a lot of features and fixes for the next flagship product release, so I don't know if I'd have the time to respond to comments and tickets in a timely fashion and therefore figure that releasing it as is- even if I think the plugin itself is pretty close to being good to go- would be a bit irresponsible.
-
View User Profile
-
Send Message
Posted Sep 16, 2013Huge fan of the plugin and have been using it since the days of BigScary being author. I'm actually running his original test server for Population Density and Grief Prevention that he handed down to me for being one of the longest remaining players on his server who was basically a guinea pig for him in making these plugins, lol. That and I tried my best to help the community and get players to see how great the plugins work in unison.
That being said I'm just wondering if there's going to be an update any time soon. The "Recent Files" shows the version is still for 1.5.1. I know it's compatible with the latest version of Minecraft but I'm simply curious. If there is, any ETA? If not then I have a question regarding a new server. You see unfortunately my server has been seeing some world corruption and according to my hosting providers support team I should do my best to just start a new world entirely before it's too late.
With this server being up and running for nearly two years now we have a lot of pointless data stored and we're likely to do a full complete wipe and start completely from scratch. Far as I know that means the latest version of Bukkit, latest version of Population Density, Nocheatplus, and I'm here inquiring about which version would be best in regards to Grief Prevention. Other than that we have little plugins I'll just have to redownload such as the console scheduler and the vanishing one.
Anyway any help or information you can provide will be greatly appreciated ^_^
-
View User Profile
-
Send Message
Posted Sep 16, 2013One more question,
How can you config that players can only toggle Buttons and levers in admin claims or subdivided claims?
Is there a permissions node for that?
-
View User Profile
-
Send Message
Posted Sep 15, 2013@BC_Programming
Wow, would be awesome.
Thanks anyway!
-
View User Profile
-
Send Message
Posted Sep 15, 2013Working on a Dutch translation ;D
-
View User Profile
-
Send Message
Posted Sep 14, 2013@BC_Programming
Thank you SO much, everything works great on the server.
This is like the best plugin ever, keep making it better :D. Thanks!
-
View User Profile
-
Send Message
Posted Sep 14, 2013@BC_Programming
I was using 145 for so long I got used to being able to make admin claims in worlds that had claims off. It's sometimes hard to keep up-to-date with what is in prior versions and what is development for 7.8 GP. I will make sure to review the 7.8 documentation :)
-
View User Profile
-
Send Message
Posted Sep 14, 2013@Sargewood
Disabling claims disables claims and all claims-related logic.
They can probably still create claims because there is no GriefPrevention.CreateClaims node, it's griefprevention.claims.create
-
View User Profile
-
Send Message
Posted Sep 14, 2013In 172 with claims: false in that world's config file I can't make admin claims in it any more nor does it respect made claims. To work around it, I tried setting claims to true and setting "griefprevention.createclaims" (copy and pasted from above) to a negative permissions node to prevent default players from creating claims in that world. Somehow they can still create claims in the world.
-
View User Profile
-
Send Message
Posted Sep 13, 2013@elirock12
The world is in creative mode. for 7.7 and earlier remove it from the "creativeworldrules" list in config.yml. for 7.8 and later, set "CreativeRules" to false in the world configuration.
-
View User Profile
-
Send Message
Posted Sep 13, 2013hey, i need help with this plugins. Every time i try to build outside a claim i get this message "You can't build here unless you claim some land first. Land claim help: http://tinyurl.com/c7bajb8 To override, use /IgnoreClaims Same happens when i try to break blocks outside a claim. Is there a way to fix this in the config? Also i cant drop blocks or item anywhere, that may not be due to this plugins so if it's not sorry for bringing it up.
-
View User Profile
-
Send Message
Posted Sep 13, 2013@Eelviny
For some reason Bukkit denies permissions on the console. It is denied before the command is ever invoked.
-
View User Profile
-
Send Message
Posted Sep 13, 2013@BC_Programming
Flags & GPFlags are constrained to Boolean values. Stuff it can turn on or off (or in this case a flag that is either up or down).
Sounds like a neat idea for a plugin, but I don't think it's a good fit for the Flags architecture.
-
View User Profile
-
Send Message
Posted Sep 13, 2013Not wanting to post this as a ticket as I just randomly tested, nothing more: Tried /gpreload in console, said I had no permission. Pretty sure console should be able to do that.
-
View User Profile
-
Send Message
Posted Sep 12, 2013@Durell_1011 I don't think that should be added. It would be VERY easy to add but since it could itself be a large sort of plugin-capability (eg. give items when player enters a claim, give potion effects when a player enters a claim, take items away when they leave, etc. It probably fits better in a separate plugin. I'd go so far as to say GP-Flags, but I don't even know if it would be ideal there.
Thanks to the API no longer sucking (it exposes direct events for claim enter and exit that can be enabled and used by plugins) this would be pretty easy to add as a separate plugin. I would probably do it myself, and might do so if only for an example Plugin using the API. (which I did with GPEnderHoppers which ATM doesn't appear to be working)