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 Oct 31, 2014@dhannyjsb
Couple of very serious bugs. If you're running it, check your logs.
@switorik
Yep. On the todo list.
@mcly
You need to figure out the correct yaml syntax. Usually colons are problematic. As for nether portals, that's a won't fix for now - take the portal down and put up another outside the land claim - I think that will reconnect the nether portal to the new overworld portal. The problem is that it's impossible to know who's making a nether portal - so it's either never allow them to pop up in claims, or always. I choose always because it's so rare to get a new nether portal in general, unless you're running some plugin that changes how they're placed and linked. I'm interested in solving this problem, just haven't come up with a good solution.
-
View User Profile
-
Send Message
Posted Oct 31, 2014Hi, just some bugs:
1. I still can't change the short links in language file 2. Nether portals are randomly appearing at spawn, inside administrative claims.
Thanks.
-
View User Profile
-
Send Message
Posted Oct 31, 2014Can you add the ability to see all claims around you when you shift click the ground?
-
View User Profile
-
Send Message
Posted Oct 31, 2014@bigscary
why ?
-
View User Profile
-
Send Message
Posted Oct 30, 2014Looks like 10 of you got 8.6.3 - it's broken, sorry. :( Please go back to 8.6.2.
-
View User Profile
-
Send Message
Posted Oct 30, 2014@Bobcat00
I should update the docs - now only building extends your claim downward, not breaking (performance boost).
-
View User Profile
-
Send Message
Posted Oct 30, 2014@LordDWT
As a player digs or builds underneath his claim, his claim automatically sinks lower with him. So all he has to do is break or place a block further down within the x and z limits of his claim, and his claim will extend deeper automatically. (In the other direction, I think all claims automatically extend to the sky.)
You can't have multiple claims stacked vertically.
-
View User Profile
-
Send Message
Posted Oct 30, 2014So if one makes a claim and it extends in the ground say 10 blocks and you wanted to claim more area underneath your claim or someone else for that matter how would you do that? It always says overlapping claim. If you abandonclaim and then reclaim further down that it a major chore for large claims and still no one can claim anywhere underneath your claim.
-
View User Profile
-
Send Message
Posted Oct 29, 2014@bigscary
I think sk89q has actually made a system in 1.7.10 to use game registries from a plugin. I'm not positive on that, though, but I know he frequents his IRC channel at http:skq.me/irc/irc.esper.net/sk89q/ if you want to ask. I could actually ask for you, if you're pressed for time. Just let me know if you want me to!
Edit: Actually, I know Essentials works with game registry string-ids since I remember typing in the strings to give items.
-
View User Profile
-
Send Message
Posted Oct 29, 20148.6.2 Updates
-
View User Profile
-
Send Message
Posted Oct 29, 2014@MPigna
I checked on minecarts - both inside and outside land claims, they break by cactus and fire. Maybe check to ensure you're on the latest version of GP and test again?
@Brycey92
Nope, but I assume whatever platform I move to after this will have support for game registry identifiers instead of numerical identifiers. I've got my eye on spongepowered.org, but it's not definite yet which plugin platform will turn out to be the most popular.
-
View User Profile
-
Send Message
Posted Oct 29, 2014@bigscary
Wait, there's a Forge version of GP that uses the game registry? Is it compatible with Vault and the Bukkit permissions systems if ran in Cauldron?
-
View User Profile
-
Send Message
Posted Oct 29, 2014@bigscary
@TakoMT
I was also initially inclined to a claim 'gutter' idea (as @TakoMT mentioned), but then it doesn't really make sense at some point. If the gutter prevents claim expansion as well, then people can still lock a claim's edge with their own gutter, or if it does allow expansion, then a player can place, then expand the claim to lock someone else's. For it to work well, it may require more complex logic and more data storage to compare claim ages and let the older one expand past newer gutters (which may seem unfair to the newer claim's owner).
It also may prevent users from using multiple claims to claim odd-shaded structures, so some slightly more complex logic would need to be in-place to allow gutter bypassing of their own claims, or maybe even of friend's claims to do dual-player claiming (in that case, may prompt a gutter-trust command of some sort).
The only situation I can think of it being useful is if you only want to prevent builds in close proximity on servers where building outside claims and claim resizing isn't allowed.
-
View User Profile
-
Send Message
Posted Oct 29, 20148.6.1 Updates
@TakoMT
I don't think it's something I will add, but maybe sometime in the distant future if more ask for it. I prefer players just learn to claim what they don't want others to claim - if you claim your house but not your yard, don't be surprised if someone else decides to build something there, right?
@Sirse
Click the blue "files" link above to see the full list of all downloads, with a compatible CB version for each.
@MPigna
The current rule is to only allow direct damage from players with the right permission, at least inside land claims. I will look into environmental damage, but I won't enable it unless I can still protect against explosions.
@Brycey92
Probably not for the Bukkit version of Grief Prevention, since Bukkit doesn't give me access to the game registry. GP already uses some smart detection (blocks with inventories, entities which are "animals" rather than monsters, etc).
@SPellegrom
Sounds like the issue I just fixed in 8.6.1. :) I will look into the sheep coloring.
@Koz4christ
Thanks for noticing! About 20 releases since I resumed work on this project in early September. :)
@ashpokeman
Visit the setup and config link above.
-
View User Profile
-
Send Message
Posted Oct 29, 2014@ashpokeman
Just set a price in the economy-section in config.yml
-
View User Profile
-
Send Message
Posted Oct 29, 2014buyclaimblocks isnt enabled
how do i enable it
-
View User Profile
-
Send Message
Posted Oct 29, 2014Most active plugin developer ever!
-
View User Profile
-
Send Message
Posted Oct 28, 2014Hi. I've ran into two problems last night with GP 8.6.
First one is a database error after restarting the server. "Because there was a problem with the database, GriefPrevention will not function properly."
Log: http://p.0xcafeba.be/avapaliduc.vbs
GP Config: http://p.0xcafeba.be/obadeyamob.sm
SQL dump: http://dump.pellegrom.org/spgt/GriefPreventionSurvival_2014-10-29.sql
Looks like the error is in subclaim (id -1): world;-1322;36;-2091 world;-1300;39;-2057
GP started without any errors after removing that entry from the SQL database.
Second problem that one of my users told me today is that it's possible for them to dye another one's sheep in a claim without having any implicit or explicit permissions. I can reproduce it. It's on the same server as mentioned above, with the same config.
I really appreciate any help you can provide :)
-
View User Profile
-
Send Message
Posted Oct 28, 2014@Sirse
GP version 7.7 for 1.5.1 will work just fine with 1.6.4. I know because that's the version I used for my server back when 1.6 was the latest version. Link to the file here: http://dev.bukkit.org/bukkit-plugins/grief-prevention/files/108-7-7/
-
View User Profile
-
Send Message
Posted Oct 28, 2014Hi, I've been using this plugin on production servers since MC 1.2.5, and now with the advent of 1.7.10 and the death of unchanging IDs, I was wondering if there was any way to either create a list of blocks requiring container trust using the game registry (minecraft:stone) or to just automatically detect mod blocks with tile entities or persistent inventories. If not, are those features planned for future updates?
Thanks