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 11, 2014Help... Anyone know how to make it so players cant destroy below sealevel on claims? Please reply back at my or msg me thanks!
-
View User Profile
-
Send Message
Posted Jan 11, 2014why cant people place water and mine tnt
-
View User Profile
-
Send Message
Posted Jan 11, 2014Hello,
i did what you told me for /ignore command and i have this when reload plugin:
http://pastebin.com/t1ejSK4Y
But, i still have samme issue as i posted at picture below.
Ignore command is still competing with essentials and i cant use it.
also i have
But doors are not locked for untrusted player.
Cheers :)
-
View User Profile
-
Send Message
Posted Jan 10, 2014hmm for some odd reason ver B: 7.8-beta-b197 for CB 1.6.4-R2.0 Dec 03, 2013 is not making a new file folder on my server. could someone please help me figure this out?
-
View User Profile
-
Send Message
Posted Jan 10, 2014@Nentify
maxClaimBlocks is a per-world configuration setting. It may be changed to allow adjustment per group (or per permission or something) in the future. But this is unlikely to happen soon.
Small additions like this are one of the main reasons an actual stable release of 7.8 has been delayed. That said, one idea for whatever comes up would be a "calculated" maximum. For example, perhaps some settings on config.yml to set values for specific permissions. You could use negative values and then those settings would add or subtract from the maximum of each world for those in that group. Primarily I would want to avoid actually adding the data to the DataStore, since any changes to the schema or amount of data written has a good chance of wiping people's data, which is obviously something to avoid.
-
View User Profile
-
Send Message
Posted Jan 10, 2014@BC_Programming
Please forgive me, i was so tired and did so many /reloads that i actually wrote wrong command. Whole text of mine is OK if you use /ignore instead /reload.
Sorry, its just mine common typo problem. But seems you catch a point and give me right info how to disable certain commands.
many thnx for great plugin and i really admire how much patient you are. You have guitar strings nerves :)
Cheers!
-
View User Profile
-
Send Message
Posted Jan 10, 2014Any word on claim block caps? Was hoping for a response on the ticket.
-
View User Profile
-
Send Message
Posted Jan 10, 2014Hi, is this plugin work when you have the faction plugin too?
-
View User Profile
-
Send Message
Posted Jan 9, 2014@BC_Programming
Thanks for your help.
Found that it was an issue with NoCheatPlus so my bad. :P
Good work on the plugin anyway with the recent changes for 7.8! I seen some people hating on it in the comments but the customizability available is really fantastic.
-
View User Profile
-
Send Message
Posted Jan 9, 2014@ha11oga11o
you can disable GP commands in config.yml, I added it specifically when folks mentioned Essentials had an ignore feature.
The setting should be GriefPrevention.DisabledCommands. So if you want to disable GP's ignore command:
That should prevent GP from hooking the disabled commands at all.
reload isn't a command GP hooks, so that would seem to be something else. as far as I'm aware /reload is a bukkit command. GP's reload command is /gpreload to avoid issues with /reload. based on the pic though it looks like your problem is actually with GP hooking ignore, which Essentials also hooks.
@_McLive_
Which build are you running? Thanks :)
@diannetea
Actually, the files aren't there- The player name specified in the message is almost certainly not the same case as the files themselves. *nix Filesystems being case sensitive is a massive pain in this regard- worse still is keeping things working with case-insensitive file systems. #239 had some attempted fixes to address the fact that GP was in fact creating two player data files, one with the case of the actual user name, and one all lowercase, which was causing issues on case-sensitive file-systems because the file updated wouldn't match the one that was loaded after a restart.
@Willbbz
I've not the bother to check specifically, but it may be that b213 (which if memory serves is the version made available on Bukkit currently) might not be respecting that option.
It is notable that even with that option disabled the same event handler will process eavesdropping for each message.
I would recommend giving the permission LordEcchi mentioned a shot first. There are some issues regarding case sensitivity and playerData and File Systems and other boring stuff that appears to be causing some people to lose PlayerData (Which is ironic given that the original purpose of the fix was to prevent losing PlayerData...)
@SGrayMe
If you get more details be sure to include what Server version and of course type (eg, Spigot, or maybe modded server or whatever) is being used. That sounds similar to behaviour that occured when GP 7.7 was run on an Aether 2 server via BukkitForge.
You might also discover more information if you set the DebugLevel in config.yml to Verbose. Be warned that it emits a crapton of information, and is usually best only run for short sessions.
The issues previously were that the different event classes ended up actually having different DataStores. so resizing a claim would resize the claim within the datastore used by the Player Handler, but then the Block Handler would not see that change- so blocks could be placed within the area the claim was seemingly expanded to.
it's weird that /gpreload would actually fix a problem, since it seems to be a source of them most of the time!
@ondaedj
Only question I have now is where would I find a list of settings that currently can't be changed, if such a thing even exists?
The settings not being changable is a bug. I only know about those two in b213 (off the top of my head). But there may be others I am not remembering.
@ultra1108
If I get an older version of GriefPrevention, will it make it so players don't have to claim land or do /ignoreclaims to build in all worlds?
You can set GriefPrevention.CreativeRules to false in the appropriate World Config's to disable that functionality. That setting defaults to whether that world is in Creative mode or not, iirc. If you don't want claims to work at all in a world, you can disable GriefPrevention.Claims.Enabled. If you don't want GP to do anything at all with a World, you can set GriefPrevention.Enabled for that worlds configuration.
-
View User Profile
-
Send Message
Posted Jan 9, 2014@Willbbz griefprevention.spam.chat give that permission to all groups, that's what I did on my server to disable the spam features.
-
View User Profile
-
Send Message
Posted Jan 9, 2014Creepers still seem to be able to knock items out of item frames, even with creeper block damage set to deny
-
View User Profile
-
Send Message
Posted Jan 9, 2014I got this crash. Seems to be GriefPrevention
http://hastebin.com/comemayomo.avrasm
-
View User Profile
-
Send Message
Posted Jan 9, 2014Hello all,
im using DEV builds too, and have problem with /reload command. Seems its fighting for ownership with Essentials /reload command but thing is; when i type /reload [player] nothing happens.
Is there any ways to completely disable that command from GP?
https://dl.dropboxusercontent.com/u/31483374/GP_Problem_Ignore_cmd.jpg
Please help. Many thnx :)
-
View User Profile
-
Send Message
Posted Jan 9, 2014:( I did /gpreload and the console filled with this (approximately ALL of my regular players)
But I looked in the folder and there ARE files for them.
Using GP dev build #239
-
View User Profile
-
Send Message
Posted Jan 9, 2014@BC_Programming
Hey I'm using the latest build available on dev.bukkit.org
Trying to disable spam filter entirely as whenever a player spams and is kiced/banned the server seems to not respond. Just hangs when I look at the console.
If it's just happening to me it's very likely a plugin could just be conflicting with it but none the less I'm looking to just disable this feature.
My current config under spam looks like this
However it doesn't seem to have disabled it. Can you see anything that might be causing this?
Thanks
-
View User Profile
-
Send Message
Posted Jan 9, 2014For the SQL database, could you please explain the player values accruedblocks and bonusblocks? Which contain the default blocks given, which the per-hour blocks, the admin given blocks via /acb and where are the buyclaimblocks stored?
-
View User Profile
-
Send Message
Posted Jan 8, 2014Hello there, Is there a way to deny mobs in a admin claim ?
-
View User Profile
-
Send Message
Posted Jan 8, 2014@BC_Programming
Yep, it does. I just didn't know that existed ;)
-
View User Profile
-
Send Message
Posted Jan 8, 2014There seems to be some persistent claim manipulation issues continuing into the latest dev builds. I'm not really sure how to clearly specify these issues beyond, sometimes an action against a current claim will work and sometimes something "weird" will happen. Like when trying to resize an admin claim, it will fail and attempting to unclaim/reclaim will make it constantly try to make the claim one block in size. Sometimes "/gpreload" appears to snap behavior back to normal, but only temporarily.
Had similar issues with the initial 'beta' version pushed to DBO, but it had seemed things were fixed until again updating recently to the latest dev.
I understand choosing to go with the dev builds comes with risking things being broken this way, though falling back to a version that appeared to be "safe" means losing some of the horse fixes (which the horse issues have been testing the patience of my members).
I'm working with another person to figure out better what's going on and if we get some progress before a solution is gotten, I'll share, but I figured you should know something that you thought fixed has reared up again.