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 Jan 26, 2016Hey!
Everyone thats using this plugin, i've made a addon for this called GreifPrevention-Anti-Worldedit.
It hooks into GreifPrevention and only allows worldedit inside of a claim that is owned by the person doing the command. Theres also a group called Bypass, users in that group have access to use worldedit outside of claims. This plugin overrides OP and any permissions plugin.
Feel free to download it here GreifPrevention-Anti-Worldedit.
-
View User Profile
-
Send Message
Posted Jan 25, 2016@ManBeastPigDev
Yeesh... that sounds gnarly. Without any hints in the logs, I'd be guessing same as you. I will use my creativity, and try to imagine what the problem could be.
EDIT: Check your boot logs for the last few GP boots to see if there are any claim-related errors logged.
@aliyah555
There are only two reasons to get soft muted - either they used a word from the banned word list while they were still new to the server, or an admin muted them. Both of these types of mutes are logged in your server logs. The banned word list type of mute also appears in your GP logs, if you have enabled "admin activity" logs in your config file. Starting in the NEXT version I release, you'll also start seeing admin-mutes in the admin activity logs. Whether you're in the server logs or GP logs, the chat is also there so you should be able to determine why the player was muted. If you can't figure it out, talk to your admin about it.
@popcorn2222
Sorry no, I don't plan to ever try to release a newer version of GP for 1.7.10. It'd be a HUGE effort, especially considering there are fewer and fewer servers running that server version every day.
-
View User Profile
-
Send Message
Posted Jan 24, 2016@ManBeastPigDev
Can you identify which claims? Are they admin claims or personal claims?
@aliyah555
If you set Admin activity logging to true in the config, you will be able to discover who and when a player was automatically softmuted.
@popcorn2222
He likely will not - it would be a lot more work to maintain, especially considering API changes like BlockDamageEvent... not to mention that 1.9 is coming soon(tm).
-
View User Profile
-
Send Message
Posted Jan 24, 2016We are a 1.7.10 server, and have been using your plugin for a while. When I checked your downloads page, it seems you have had a lot of updates since the most recent 1.7.10 version. Do you plan on making another 1.7.10 version with all the latest features? Or is there already one that I somehow missed?
-
View User Profile
-
Send Message
Posted Jan 23, 2016I have a suggestion just because recently I've been having issue with bots coming into the server with Advertising Bots, Do you think you could make it where the banned words or which ever can warn Admins or Moderators that have a certain permission node that someone said a word that is on the banned words list when they are softmuted or maybe when someone is softmuted they have the option to put a reason and you could do like /smcheck {Ign} (I said that command because I already have a /check command to see why people are banned) To see why someone is softmuted. Because It's hard to tell why someone was softmuted because there isn't really anything that tells you why and with bigger servers it gets really confusing when you have like four people softmuted and they are talking to each other and you can't really see why they are softmuted.
-
View User Profile
-
Send Message
Posted Jan 23, 2016@ManBeastPigDev
I checked all the logs and the only claims that show expiring are the usual new players who abandoned new chest claims.
-
View User Profile
-
Send Message
Posted Jan 23, 2016I'm getting reports of claims abandoning themselves. 2 from staff so reliable. using latest ver.
I have a log for the last 2 weeks if you want it. I update usually the day after you release.
-
View User Profile
-
Send Message
Posted Jan 20, 2016@Bobcat00
Unused is only for creative mode worlds. It scans the actual blocks in the claim to count player blocks, then deletes the claim if there aren't many player blocks and the player has been gone for the days you specify.
Chest claim days are for automatic chest claims, identified by their size, and only deleted if the player also doesn't have any other land claims elsewhere. Idea is to identify claims from new players who left some days ago and haven't come back. Default days setting is more aggressive than the all claims days.
@puckman1971
Right on, well done. :) Maybe you want to drop griefprevention.claims as well, so the slash commands disappear from help.
@f117landers
Glad you figured it out. :)
@TheFemoDemo
With nothing in the logs to go on? No, sorry - please have another look for hints. Possibly the claims are expiring due to player inactivity? If yes, there would be notes in your server logs.
-
View User Profile
-
Send Message
Posted Jan 20, 2016TY expirations claim work fine!
-
View User Profile
-
Send Message
Posted Jan 18, 2016Player claims keep randomly deleting themselves. I can't seem to find any issue in the logs, so I have decided to post this here.
One player logged on to find her house unclaimed and her chests looted.
Any suggestions?
-
View User Profile
-
Send Message
Posted Jan 18, 2016jahangir13 helped sort me out. For those who are looking for the solution, I am using multicraft and used the default bukkit plugin (which is for MC 1.8). Solution is to stop the server, remove that version, manually download correct jar, ftp it into plugins, then start the server again.
-
View User Profile
-
Send Message
Posted Jan 18, 2016Thanks for this mod!
I am having an issue integrating it into my server though (Cauldron with Bukkit Essentials for 1.7.10 with group manager.) The players are permitted to use claims.* and essentials.build.*, but whenever a player goes to use the shovel, no text appears and nothing happens.
This happens with all groups, including those /op. Trying to switch between /basicclaims and /admin claims registers the change with the notification in the chat, but the shovel does nothing on right click.
If anyone is able to help with this, it would be greatly appreciated.
-
View User Profile
-
Send Message
Posted Jan 17, 2016Is there any way for me to migrate to using a database (mySQL) without losing current claim data for players?
-
View User Profile
-
Send Message
Posted Jan 16, 2016@puckman1971
Found it. To disable auto chest claims do this: AutomaticNewPlayerClaimsRadius: -1
And in your permissions manager do this: - -griefprevention.createclaims
In case people are wondering, I want the plugin to protect my server builds yet leave factions for players.
-
View User Profile
-
Send Message
Posted Jan 16, 2016Anyone know how I can disable the chest claims? I tried setting the auto claim, which I assume is part of the chest claim, to zero but it still makes a 1x1 claim for that chest.
I want to avoid lots of ramdon claims from where people plonked down their first chest.
-
View User Profile
-
Send Message
Posted Jan 16, 2016@bigscary
Thanks for your reply. Exactly how do ChestClaimDays and UnusedClaimDays work at the present time?
-
View User Profile
-
Send Message
Posted Jan 16, 2016@Bobcat00
You can still turn it off completely in the config file. Zero should do the trick.
It's crazy expensive to load all the chunks and then scan ALL the blocks in those chunks to determine what has been built - prohibitively so. And it still wouldn't solve the whole problem - sometimes players make small claims for example adjacent their larger claim where they don't build a lot for example a gravel road leading up to their mansion. That claim would still be expired, even if his others were not. You still have the admin claims conversion as an option, and I'm planning to add a flag to GPFlags to prevent expiration as well. Both involve administrative action I know, but I think you'll agree that's OK because this sort of situation probably doesn't come up very often.
@enight0000
There's no tp command, the plugin is purely anti-grief. Shop around for a better sethome plugin which automatically sets a player's home if he places a chest, places a bed, sleeps in a bed, or dies before he has set a home.
-
View User Profile
-
Send Message
Posted Jan 16, 2016Thx for your plugin! I have a question that if player forget the position of his claims and he did not set spawnpoint at home, how can he go back? I did not find any tp command
-
View User Profile
-
Send Message
Posted Jan 15, 2016You need to think about the AllClaims expiration some more. For one of the claims that expired on my server, the owner had been inactive for 18 months, but the claim had 10 other builders. The builders have been active recently. I don't think you want those claims to expire. I set the timeout to 1000 days until I can figure out what to do.
EDIT: I really don't like the idea of automatically expiring claims unless you can check to see if something substantial has been built in it first.
-
View User Profile
-
Send Message
Posted Jan 15, 2016GriefPrevention 13.6 is here!
@The_PC_Tech_Guy
Turns out I did actually break it, when I added support for dollar sign formatting codes in the messages.yml file (that message is regex, so it contains a dollar symbol which should NOT be converted to the formatting code point). Fixed in version 13.6.
Default logic is "how" followed by "claim", "protect", or "lock".