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 Feb 14, 2015@bigscary
There are many, many modded 1.7.10 servers which need decent grief protection; There is every point in adding it - Also, there is new versions of cauldron (sponge, glowstone projects etc) So there is every point in continuing mod support.
Most of the servers on technicpack.net are running 1.7.10 and having to ban wrenches and so many items because none of the current protection plugins are good enough.
AE2 block IDs are different when placed, so adding the IDs to the config doesn't work.
-
View User Profile
-
Send Message
Posted Feb 13, 2015Using latest Spigot 1.8.1 and this line set in the Grief Prevention config:
BlocksAccruedPerHour: 10
No blocks are getting added to anyone per hour. Any reason why that might be? Thanks!
-
View User Profile
-
Send Message
Posted Feb 13, 2015@GodsDead
No plans to add any new features to the siege thing, but bug reports are welcome if you can get more details on what causes the "stuck"? Also if you can define what stuck means to you in this context, that would be great. As for negative claim blocks, try /claimslist <playername> to investigate further. How are those players picking up items and tools? Off the ground? From containers? Using slash commands like /kit?
@zedadiaswick
Yep, intentional. It's not that they shouldn't be able to do it, just that when I looked into getting it done, it was looking scary (lots of potential for bugs). I decided it wasn't worth the bug pile.
Yes, the notes about updating to 1.8 said that you'll get a new config file and you'll have to customize it again if you made any changes (like max claim blocks). I just took that notice down yesterday, since it had been up for months now. Maybe I took it down too soon. :)
@yepidoodles
/gpblockinfo was added in a much later version than the one you're running. None of the 1.7.10 versions have that command - sorry! :(
I did have a plan to add the feature your describe, but the cauldron guy stopped working on cauldron before I could get it done. So now there's no point in adding it, since there won't be a cauldron version to hook Forge 1.8 to Bukkit 1.8. You can consider adding blocks people would right-click on with the wrench to your "block ids requiring container trust" list, which would stop all right clicks (even without wrench in hand). If taking that step doesn't solve the problem, then the problem is in your mod and you'll have to ask the mod author to make sure he's firing the appropriate events so that bukkit plugins can cancel the wrench actions.
-
View User Profile
-
Send Message
Posted Feb 13, 2015I run a Modded 1.7.10 server and using GP (Best 1.7.10 protection I could find; thank you for that!) I noticed your /gpblockinfo command doesn't work (Unknown command. Type "/help" for help.) And this is where I'm now having issues - We're using the Mod Applied Energistics 2 - which, when placed, most of their blocks run off data values, rather than the original ID (So /gpblockinfo would come in super handy right now!). The blocks can be picked up when wrenched - so even if you can't get the /gpblockinfo to work; I suggest attempting to make another config setting which stops you from right clicking a block with an item in your hand (i.e. a wrench) when in a claim. I have no knowledge on plugin/ mod-making; but the general principle I'm asking for is; *right clicks with item in hand* > doesn't allow you to do that
I really hope you read this and you can do something about it, as it would make Admin's like me, lives so much easier.
Thanks - Alice
-
View User Profile
-
Send Message
Posted Feb 13, 2015Have found managers of a claim may not create subdivisions. Is this intentional? It seems obvious to me and my players that managers of the top level claim would be able to make subdivisions, though can understand not wanting others to be able to edit the structure of a claim. Could this be changed, or perhaps add a config option be added to enable managers to create subdivisions?
Also, I found the default config following updating from the beta limited players to 80,000 claim blocks again. As I had changed this, some players had earnt and spent more than this on claims. I have also found, after changing that option, that the /adjustaccruedclaimblocks command is now missing. Could this be brought back? I'd like to be able to change their accrued claim blocks to resolve issues like without giving the bonus claim blocks. (Though I understand 10.7 resolves this automatically, I would like to be able to adjust their accrued up for this who had saved up a large number to claim a big project before my mistake in leaving the default 80,000 in the generated config)
Good to have you back on the project, bigscary! ^_^
-
View User Profile
-
Send Message
Posted Feb 13, 2015Im having a few bugs reported since moving to GP 1.6.3 (Ill update to 1.7 today)
On a sidenote, is there any plans to work on the siege engine?
-
View User Profile
-
Send Message
Posted Feb 13, 2015dear is there are having a bug that when i setting the MaximumDepth=40 player still can make a claim under 40depth please help
-
View User Profile
-
Send Message
Posted Feb 12, 2015@bigscary
Sorry, I'm not really good at english. What does exactly mean "administrative claim". No one can claim over it but anyone can build in it ?
-
View User Profile
-
Send Message
Posted Feb 12, 201510.7 Updates
Please take a few moments to vote for Grief Prevention! :) We're only 35 total 5-star reviews away from being the top plugin on the spigot site, which is absolutely a reachable goal. Thanks for your support! http://www.spigotmc.org/resources/griefprevention.1884/
@jwpwns
"initial" means "first time they log in after GP is installed". If claim blocks were reduced back to initial every time a player played, no one would ever accumulate any land claim blocks. The version I released just now does, however, increase to the new initial value you set as needed.
@maclarenss
I think it's a bug, let me look into it. :) I don't remember whether I disabled it and left in the config option by mistake, or meant for it to work and accidentally broke it.
-
View User Profile
-
Send Message
Posted Feb 11, 2015I am setting to InitialBlocks: 600 and it says i have 1216 blocks ???? even if i set InitialBlocks: to 40000 it will still say 1216 blocks i Restared the sever it wonrt change why?
-
View User Profile
-
Send Message
Posted Feb 11, 2015hi!i have settings in config AutomaticNatureRestoration:SurvivalWorlds: true but when private expired,Nature NOT Restoration,only claim remove..pls tell me how enable NatureRestoration? version griefpr.=last.version bukkit=1.8.1 last
-
View User Profile
-
Send Message
Posted Feb 11, 2015@Phreag
Passwords are less secure, and awkward to use. You can allow the public access to a small part of your land claim by creating a subdivision around the area, then standing inside that area and typing /accesstrust public or /containertrust public or /trust public, depending on the level of permission you want to give everyone.
@donpot
Only vanilla items, no support (in that feature) for specifying IDs and data values. Sorry!
@sakura_blades
Still on the todo list, close to the top. :)
@Jikoo_K
Sure thing, next version.
-
View User Profile
-
Send Message
Posted Feb 11, 2015Would it be possible to get a permission defaulting to true for /givepet?
I allow users to have dogs, but they have to either tame them themselves and breed or use a special ingame mechanic. I'd like to allow my mods to still be able to use the command for special cases, but I don't want players opening their own kennels and trading dogs to others.
For now I've just aliased /givepet to another command in commands.yml (basic users cannot use /griefprevention:givepet or any similar command where plugin is specified, mods can) but I would appreciate a cleaner solution.
-
View User Profile
-
Send Message
Posted Feb 10, 2015@bigscary
It doesn't appear the latest release is resolving my issue of old config settings for initial claim blocks. Was that update intended in this latest release, or another one?
-
View User Profile
-
Send Message
Posted Feb 10, 2015its looks awesome! and me and my buddy gonna use it for our Custom modded server.
BUT!
i have a question, im a modder my self, and i was thinking instead of using a Golden Shovel and a stick, is it possible to use an item from a mod? Or only vanilla iteams?
Best Regards Donpot
-
View User Profile
-
Send Message
Posted Feb 10, 2015@Phreag
Or you could just disable GP's hold on chests and doors and use LWC with it? :P That's what I do.
-
View User Profile
-
Send Message
Posted Feb 10, 2015I Have a Suggestion:
Would it be Possible to add a password protection for chests, doors, buttons etc?
- everything is by default protected like it is now - if you put a password on a chest/door/trapdoor/container/ you have to enter it to use it. - also you can completely unlock a single chest or button in your claim for public access
This would be like an integration of LWC features to griefprevention ;)
-
View User Profile
-
Send Message
Posted Feb 9, 201510.6.3 Updates
Please take a few moments to vote for Grief Prevention! :) We're only 35 total 5-star reviews away from being the top plugin on the spigot site, which is absolutely a reachable goal. Thanks for your support! http://www.spigotmc.org/resources/griefprevention.1884/
@sakura_blades
If you haven't given them any bonus blocks with /acb, the easy fix is to delete their player dat files. Then they'll be treated as new players the next time they log in, and get the new default initial blocks. Or you can wait for me to deliver you a fix in the next version.
@erik1988
I have a fix in the next version for self damage causing a player to be "in combat". For example, hurting yourself with an ender pearl. I can't be 100% certain this will solve all cases, but I feel pretty good about it.
@Duning
Looks like an already-fixed bug - maybe you need to update? If you update and still have that problem, please tell me which GP version you're using and whether you're in flat file (default) or database mode. Thanks! :)
-
View User Profile
-
Send Message
Posted Feb 8, 2015@Brycey92
It works ingame, but i cant get my console to type both brackets.
-
View User Profile
-
Send Message
Posted Feb 7, 2015I'm getting an strange error when resizing subdivisions...