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 Mar 7, 2014with the land claim. will the gold blocks and glowstone go away or does it stay there..
-
View User Profile
-
Send Message
Posted Mar 7, 2014Hi,
I've had brief experiences in the past with grief prevention, but for my server I need to be able to create an ungriefable claim that allows members to build and destroy their own blocks, but not my blocks or the "base" blocks. From reading this I wasn't sure if this plugin went into that specific of a situation.
thanks,
RBF
-
View User Profile
-
Send Message
Posted Mar 7, 2014@kemmeo Thanks for the reply
Server owner. I'm very open to staff to help administer this plugin. I'm savvy at many but this one for now is escaping me. I have the DB running on the pre 1.7.8 version.
The IP us mcempire.co its the survival server.
-
View User Profile
-
Send Message
Posted Mar 7, 2014This looks like a really heavy duty anti grief. Whats wrong with WorldGuard use instead?
-
View User Profile
-
Send Message
Posted Mar 7, 2014Since the 7.8 update I have not been able to get /ignoreclaims working. I have given my admins the perms griefprevention.ignoreclaims and griefprevention.claims.ignore but when the try to do the command it says they dont have perm to do the command. Please help! :)
-
View User Profile
-
Send Message
Posted Mar 6, 2014I would really need those questions answere. Please:
1. What is entity cleanup task?
2. If I set "AllClaimDays: 40" and disable ClaimCleanup like so: ClaimCleanup: Interval: 300 Quantity: 5 MaximumSize: 25 MaxInvestmentScore: 100 Enabled: false Will claims still get removed after 40 days of inactivity?
3. If a player creates his first claim with a chest and than resizes it. Will this claim still be considered as chestclaim (that gets removed after 7 days) or not?
4. How exactly does this automatic claim expiration work? I just want to know about allclaimdays function. When does it check if claims are not used over 40 days? Because I do sometimes find claims that belong to player who didn't play for more than 40 days.
5. Does a player have to build anything on a claim so it doesn't get automatically removed or is it enough for him to just log on the server?
6. What if a claim belongs to player A and player B has a trust to build on it. Will the claim get removed if player A doesn't log on in 40 days even if player B is building things on player A's claim?
I am currently using b213 and there are so many random bugs and claims that should be automatically unclaimed. I am also setting things up for a new server and am trying to use b277. Should I start with this build or can I expect problems in long term?
-
View User Profile
-
Send Message
Posted Mar 6, 2014Is there a way in GP 7.8 to allow universal container access regardless of claim ownership and permission? I'm looking at either a rule in the config or a permission node. We have another plugin to manage chest protections and no one can access crafting tables and enchanting tables, which should be free to everyone. I tried editing the GP config.yml to include a Rules subcategory with a Containers subcategory, but when I reloaded the server, those settings were deleted and nothing changed. Thanks in advance.
-
View User Profile
-
Send Message
Posted Mar 6, 2014@DarthRiddle
are you a user or a server owner/admin? if you are using GP on someone else's server, they probably didn't set it up right or something like that.
if you're the owner and having trouble understanding the plugin then I suggest you READ the messages the plugin sends you. its like this all the time on my server, so many people don't bother reading the instructions or watching the tutorial video and just spam the chat with "This St isn't working" without thinking.
-
View User Profile
-
Send Message
Posted Mar 6, 2014@Danikool48
You could try disabling the anti-Spam meassures in GP, don't remember if they have a specific option to allow punctuation in Ip's or URLs but I'm pretty sure they do.
-
View User Profile
-
Send Message
Posted Mar 5, 2014How do I block the feature that when someone types in an ip address it removes the periods. I need this plugin to keep the periods because it is messing with the mechanics of another plugin. Please help.
-
View User Profile
-
Send Message
Posted Mar 5, 2014I've been having issues recently with players not being able to breed animals in claims, and intermittently, other entity spawning issues. Is this a bug with GP or could another plugin be interfering? As far as I can tell, I've checked the world's config, and any relative-sounding option is enabled, and trusts have been checked, but breeding seems to be disabled entirely. Thanks in advance for any pointers here, it's the last big issue my server is having at the moment. We're using GP build #282 from the Jenkins site, and Spigot 1308.
-
View User Profile
-
Send Message
Posted Mar 4, 2014running the plugin om my server, its GREAT! However a week and 1000 claims later I did manager to run into 2 small problems. ( using 1.7.2 Beta on spigot)
1) players who have griefpreventio.claims.ignore and / or griefprevention.restorenature don't have access to the respective commands, in Groupmanager atleast.
2) the option to disallow PvP within player / admin claims keep resetting themselves to false for some reason.
Hope I'm not just a noob who can't setup permissions :b
-
View User Profile
-
Send Message
Posted Mar 3, 2014I'm a teacher and started running a server for elementary students about a month ago, so this looks great. I've been trying it out on a test server and had a couple questions. 1) I have certain areas set as no build in Worldguard (areas where I've built educational stuff so it doesn't get destroyed). Will this override GP, or do I need to set them all up as admin claims? 2) I was excited about the tree topping, for some reason 10 year olds never take down the whole tree. I have it set to true, but on my test server the tops never went away on their own, or replanted. I'm using the new dev build. Am I doing something wrong?
Thanks for the plugin, it looks like it will solve a lot of my headaches!
-
View User Profile
-
Send Message
Posted Mar 3, 2014Is there a way I can add a block that people cant get into on a claim because I'm running a 1.6.4 FTB server and people can get into me access terminals, Crafting terminals, Controllers, Interfaces, etc. So if someone could help me by telling me how to add a block id to stop people from accessing these items that would be great!
Thanks, Just Blazed
-
View User Profile
-
Send Message
Posted Mar 3, 2014649 pages of comments is a bit daunting to sort through so I apologize if this request has been made already.
I'd like a new trust level, /croptrust or /farmtrust.
Something that would include container and access, but only allow placing/breaking of crops (and/or animal interactions). I'm building a public wheat farm on my server, and for it to be public I have to allow building trust to everyone or nobody can replant after they harvest. But I'd like it better if the wheat (or carrots, potatoes, etc) were the only thing they could break/place. It would allow replanting without letting anyone mess with the mechanics or the structure.
-
View User Profile
-
Send Message
Posted Mar 2, 2014@bratpitt
Easiest solution to fix that is using a permissions plug in. I didn't use a permissions plug in for a long time, but players not being able to place lava or water buckets got old quickly.
PEX is pretty easy to set up as well as YAPP.
-
View User Profile
-
Send Message
Posted Mar 2, 2014Hi
Am not running any Permission plugin and want to change so player can use fire under sea level. Tought i only had to remove "RequiredPermissions:" and "- GriefPrevention.Lava"
But it comes back. Anyone with soloution?
-
View User Profile
-
Send Message
Posted Mar 2, 2014@BC_Programming
Please have a look: http://dev.bukkit.org/bukkit-plugins/grief-prevention/tickets/588-terrible-lag-on-server-startup/
-
View User Profile
-
Send Message
Posted Mar 2, 2014@Garrash
If you edit the Material Lists, you cannot have the Config Search option enabled. I haven't actually tested GP with a MCPC+ server since 1.4.7 when I was getting MystCraft working, but that should work. Only thing I can think of would be to remove the last portion, eg:
instead of:
@beetuna
The PlayerData files store The current claim blocks, the number of bonus claim blocks, and that is practically it. It also saves some claim information however it completely ignores that when it is read in since that information is acquired from the claims themselves when they are loaded.
There is however one downside in that resetting them to the initial allottment will actually make their remaining claim blocks negative, since they still have claims.
For example, the default is 100 blocks; so if I make a 100 block claim, it will show my remaining claim blocks as zero. However, 100 is still stored- the remaining blocks are calculated by subtracting the area of all the players claims from their accrued claim block total added to their bonus claim blocks.
-
View User Profile
-
Send Message
Posted Mar 1, 2014Is there no place to just enter item IDs in anymore? The Regex isn't finding My ME Access stuff in 1.6.4 and the systems aren't being protected, as these are massive amounts of items this is a huge issue for players.
I've tried editing at the end of the world files and it doesn't seem to work, has the format changed? I'm doing it like this: