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 Jul 13, 2013I had an idea: Changing the claim-creation tool/block! Mabye the owner of a server wants furnaces to create claims. All he/she would need to do is edit the config.
Edit: You can alredy do that in 7.7, er, sorry. It's a good thing I read the Admin page.
-
View User Profile
-
Send Message
Posted Jul 13, 2013@ToxicAirEvent
You can already do this with 7.8. Go into your world.yml file and make sure CreeperExplosions is set to this:
If you don't want block damage, check out:
There are settings for other types of mobs/explosions too.
-
View User Profile
-
Send Message
Posted Jul 13, 2013Is there any way to have creepers do damage inside of players land plots. I run a PVE server so creepers doing damage is a bigger part of the game since players are competing against the world we'd like to have all of the mobs do their default damages and effects.
This is making we wonder if there is any way to allow creepers to do damage inside of players claimed land but not have other explosions do damage?
-
View User Profile
-
Send Message
Posted Jul 13, 2013Hey BC_Programming, any idea when will 7.8 be out? I'm thinking of restarting the maps on my server, but can't if 7.8 would be out after I launch them.
-
View User Profile
-
Send Message
Posted Jul 13, 2013The 1.6.(1/2) build will protect stuff from being taken off of horses, right?
I'd assume so, but I'm just checking.
-
View User Profile
-
Send Message
Posted Jul 13, 2013@TJW28
bah that's an unrelated problem with the new Dispenser Rules, evidently I didn't deal with the Potion items as well as I thought. That and the other changes should appear in build #130, which should, if my working theory on it is correct, fix your weird claim issue.
-
View User Profile
-
Send Message
Posted Jul 13, 2013@BC_Programming
BC< im unable to manually recreate it, but it does just seem to occur after a period of time.
I thought the claim cleanup may of been a cause, so disabled that in all workds, but, its just happened again after approx 2 hours of uptime.
Now, ive also started seeing the folloing error in teh console, whether it is of any significance or not, im not sure. CONSOLE ERROR LOG
-
View User Profile
-
Send Message
Posted Jul 13, 2013@xOMutleyOx
If it persists please plop a stacktrace from the error :)
-
View User Profile
-
Send Message
Posted Jul 13, 2013@TJW28
Fascinating! Do you happen to know of a sure-fire way to reproduce it, though?
At first the thing where deleteclaim is unaware of the claim but the stick action is not seemed weird.
However, on investigation it made a bit more sense. Basically most Claim actions by players will "cache" the claim being dealt with as part of the Player data; so it sticks around. What I think might be happening is that the claim is not actually in the dataStore but it is still sticking around in the PlayerData for the players. Sicne that optimization doesn't really help much and seems like more a stopgap for the older sequential search algorithm, I've refactored it out (I left a compat function so API-using plugins still work, of course...). This should appear in the next dev build. I don't know if it will fix that particular problem but it seems reasonable- the DeleteClaim command doesn't pass in a cached Claim and the investigation tool does, as do some of the claim-operations.
-
View User Profile
-
Send Message
Posted Jul 13, 2013[SEVERE] Could not pass event PlayerInteractEvent to GriefPrevention v7.8
Getting this error when player trying to expand a claim.
Running build #126
Just noticed you are at #129 updating now.
-
View User Profile
-
Send Message
Posted Jul 13, 2013Hi BC, ive done a quick video showing an issue we seem to be having now.
Currently using build #129
CLICK HERE TO SEE
It seems that data isnt being written at the time the claim is being resized, deleted, or abandoned. When trying to adjust a claim, it says the claim must be 10 x 10, when it is in fact allready bigger than that. When trying to reduce a claims size by clicking on a corner, it says a claim would be overlapping an existing claim. (There are not other claims ( ive checked used the new Crouch and click feature )
As soon as the server is rebooted, everything works as normal for a period of time, before the issues starts over again.
Thanks
-
View User Profile
-
Send Message
Posted Jul 13, 2013@deleted_9935739
Seems like you are on a build before #124.
-
View User Profile
-
Send Message
Posted Jul 12, 2013These keep showing up in the logs every few minutes. http://pastebin.com/t2HiRzpy
-
View User Profile
-
Send Message
Posted Jul 12, 2013@Blokizaki
Beyond 7.7 GriefPrevention now uses World-Specific configurations, so it would be possible to change the investigation item on a per-world basis.
I would guess that the behaviour you see is a bug, since worlds that don't have claims enabled (ClaimsEnabledWorlds list, if memory serves) shouldn't be performing any claim-oriented logic. I'm not sure if the bug persists in the current builds but I guess I ought to look into that as well.
-
View User Profile
-
Send Message
Posted Jul 12, 2013Hi, I'm liking GP and how easy it is for players to use. I need a little help though . . .
I've disabled GP in specific worlds. However, when I try to use the Stick for PVPArena (to highlight regions), it still tells me "no one has claimed this block" and I can't override it to use it for PVParena.
Is there a way to disable the stick on a per world basis? I know this seems so nit picky :) I don't want to change it in the config setup because your point about it being in the videos is very valid.
Thanks for your time!
-
View User Profile
-
Send Message
Posted Jul 12, 2013@BC_Programming
Thanks for the response. ^_^
-
View User Profile
-
Send Message
Posted Jul 12, 2013@BaffledCanadian
You can set GriefPrevention.NoSurvivalBuildingOutsideClaims to true to do what you want.
-
View User Profile
-
Send Message
Posted Jul 12, 2013@deleted_9935739
You'll need to put "placeholder" commands. I'm not sure what would work as a good no-op, though.
On transfer claims, I think I may have misunderstood the logic. It seems like it's not working as intended which isn't surprising since the original idea for what perms would be required in certain cases is kinda confusing.
/transferclaim [SourcePlayer] [TargetPlayer]
Basically we have three cases: the case with no arguments, the case with one argument, and the case with two arguments.
No Arguments will be for making a claim an admin claim, and will require adminclaims permission.
a single argument will be for transferring a owned claim that the player is in to another player. If the player owns the claim, it should require transferclaims permission. If not, it will require adminclaims permission.
Two arguments is for forcefully giving the claim the first player is on to the second player and should require both permissions.
I don't think it works as intended currently, though.
-
View User Profile
-
Send Message
Posted Jul 12, 2013Hi, I've been using your plugin for a few weeks now and I like the premise of it. I do have a question or two.
Is it possible to set it so players can only build after they have set up a claim as oppose to build anywhere even if no claim has been set?
Basically, I want to set it so players cannot place blocks on the map, unless they have claimed that area, but still can destroy blocks (eg: cut down trees, dig, etc) in the wild on unclaimed land. So players have to place down a claim using GP to be able to build.
-
View User Profile
-
Send Message
Posted Jul 12, 2013So i got this plugin how do i make it so people can use it on some worlds? like a creative world or pvp world?