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 30, 2012@megabytes
Actually, I need somebody to use my public API to develop a creative mode extension as a separate project. You up for it? You'd probably be creating admin claims as new players joined the server, and giving them permission there (they can build, but because they dont own the claim, they can't expand). Also you'd have to block wilderness build/break.
Additional features to be brainstormed at a later date.
-
View User Profile
-
Send Message
Posted Mar 30, 2012@Lostwave
I've suggested this to bigscary before. He said that he wants to make the plugin as friendly as possible. If you want, you can also remap them like I am doing right now. I can send you my scripts. I am switching from res.
-
View User Profile
-
Send Message
Posted Mar 30, 2012@mynameismonkey
stand in claim (may not be required) and type /ic
-
View User Profile
-
Send Message
Posted Mar 30, 2012Hi guys, I'm trying to figure out if this is a known change or just me. As of 3.0 - and I just upgraded to 3.2 to double check - as admin I can destroy a player's claim block but as admin I cannot build on a player's claim. Before 3.0 I could build and break anywhere. Is this as intended or have I messed something up? I don't see anything referencing this in change logs or comments.
-
View User Profile
-
Send Message
Posted Mar 30, 2012Bigscary u may now facedesk/rage
http://www.mojang.com/2012/03/minecraft-1-2-5-prerelease/
:P
-
View User Profile
-
Send Message
Posted Mar 30, 2012@Lostwave
i think he does have a point i thought something like this today actually, +1 on this, i think its well within the foundations of GP and its goals of simplicity ;)
-
View User Profile
-
Send Message
Posted Mar 30, 2012This is just a suggestion, but it would make things a lot easier....
Can you put all of your commands under a main command, Its too hard to remember the commands and find them in help.
something like /gp /gp trust <user> /gp ignoreclaims /gp bla bla
or at least a /gp command that lists all the commands so I don't have to keep coming to this page to remind myself of the commands. Because they are all so different, I can never find them in help.
Just my 2 cents.
-
View User Profile
-
Send Message
Posted Mar 29, 2012Thank you very much bigscary, this is an awesome plugin, you have done an excellent job, and you released source? Must donate now!
You so totally rock.
Peace.
cdrgnfly
-
View User Profile
-
Send Message
Posted Mar 29, 2012Also, bigscary. Would it be possible to add a time-out on claims? Like if the player hasn't been active in a week, their claims get deleted? I have a bunch of random claims all over the map where it's just half-built houses that won't get deleted.
-
View User Profile
-
Send Message
Posted Mar 29, 2012@krisdestruction
http://dev.bukkit.org/server-mods/grief-prevention/pages/Administrative-Details/
Bottom of page i think your meant to use /ic
-
View User Profile
-
Send Message
Posted Mar 29, 2012Can you please add permission nodes? As an admin, I'm unable to access a player's chest. I need that to ensure there's no xray or funny business >.<
-
View User Profile
-
Send Message
Posted Mar 29, 2012@bigscary
Woohoo, thank you! Anything source-wise you need help with? I'm ready to get my hands dirty :)
-
View User Profile
-
Send Message
Posted Mar 29, 2012@bigscary
I'll give a detailed explanation.
The shops are public, and no one can place blocks besides a sign. They can also access chests. Other people have been claiming areas of the shop which prevent people from opening their own shops.
-
View User Profile
-
Send Message
Posted Mar 29, 20123.2 Updates!
Source code released, see repository link in the blue navigation area above.
-
View User Profile
-
Send Message
Posted Mar 29, 2012@Qwahchees
No sorry, the /trust permission allows both build and break. There's no option to get only one or the other. Why not just give the shop owner the permission to build? Do you really think that someone will take that opportunity to grief in the tiny area they've been allocated for their shop, instead of having a shop? You could for example subdivide the shop so that the walls aren't part of the permission area, that way even the shop owner can't break them.
-
View User Profile
-
Send Message
Posted Mar 29, 2012Anything I can do to help speed along the release of the source? I'm hesitant to install any plugin that I can't dive into and I'm on the verge of writing something myself that draws inspiration from this and our existing GuardianBlocks plugin.
-
View User Profile
-
Send Message
Posted Mar 29, 2012@bigscary
It's not just that, the sign is hovering above the block that is claimed, which causes an issue with placing the sign beside the shop.
Is there a mode to be able to place a block, but not destroy or claim?
-
View User Profile
-
Send Message
Posted Mar 29, 2012@Fostenel
Can your redpower machines move around or change blocks from far away? If so, I don't think allowing the mod user account permission in your claim is a good idea. It seems to me, then, that a griefer could place a machine near but outside your claim, and then use it to change the inside of your claim.
The best approach would be to try to determine the "owner" of the machine. That's what I do for flowing water, flowing lava, and pistons. Basically, the owner of the machine is the owner of the claim where the machine is located, or no owner if in the wilderness. If the owner of the machine doesn't have permission to make a change, then the machine can't make it. Similarly, if machines can actually move around, they should be prevented from walking across claim boundaries unless the "from location" and "to location" are both owned by the same player.
-
View User Profile
-
Send Message
Posted Mar 29, 2012@bigscary
Thanks for the quick reply! I just saw some of the changes that you mentioned. I like the way you're going with it, and I didn't realize that there was a permission to allow lava. The permission is certainly a better way to go than a global option.
I was referring to the fake player "[RedPower]" in my post, I also meant the fake player with my use of "mod user". I haven't tested exactly were the issue lies as for as it working before and not now. It very well could be an oversight in the port to bukkit. I brought it up here, because a solution would be to allow the user to be trusted. Perhaps I can hack something up to create a player file in the worlds folder to allow it! I'm working on figuring out a little more about what might be going on. If I manually add the user [RedPower] to the ClaimData, it will work, so the player definitely exists and is being used, but permissions and op are no longer working for it for some reason.
-
View User Profile
-
Send Message
Posted Mar 29, 2012@xBladeM6x
No sir, probably won't ever happen. Don't get me wrong, I do see that some folks want it. It's just that the whole design has been based on non-stacked claims, and changing it now would destabilize everything and really hurt overall performance.
I think it's not as huge a deal as some think, anyway. After all, a Minecraft world is like 50x the size of the earth or whatever, so there's no real need to stack homes on top of each other because we'll never run out of space. It's just a "cool thing to do", not a "gotta have".