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 Oct 1, 2012Is there a way to make a claim of only 2x2 or 4x4?
-
View User Profile
-
Send Message
Posted Oct 1, 2012@bigscary
No, i'm using version 5.5.1 the version you recomended for tekkit
-
View User Profile
-
Send Message
Posted Oct 1, 2012@SuperSpyTX
Will do.
@zlepper
Are you on version 6.6?
@ryanwagner
Seems like a small thing to me. But I'll double check it, and fix it if it's broken. :)
@XtratiK
I don't think I will add this. It would be very complicated and in 10 months, you're the first to ask for it, so probably not a lot of folks would want it.
@anton8604
There is a /siege mode you can turn on. :) I don't plan to add any community claim block ownership.
@ray73864
Were you able to create your own claims in that area without /adminclaims? Since you have the permission requirement turned off, it's either all players can make claims there, or none can. If you talk to that player again soon, please see if you can get the exact error message from him, which will help me figure out the reason for his being blocked.
@instinxx
GP asks Minecraft whether or not a player has been on the server before. So if a player has never visited before, you won't be able to do things like /acb and /trust with that player. Why do you want to do this? Maybe there's another way to solve your problem.
@ray73864
Hmm I'm not sure how I could do that. Right now, players actually get blocks every 5 minutes, not on the hour. Seems like it would be very hard to get the math right? I'm not sure it's worth the risk to change that area of the code anyway - there have been bugs there in the past, and it's a sensitive feature area because any mistake could be a big problem because it results in too many or too few claim blocks.
@RasCas
You can translate everything in messages.yml. :)
@botg_smp
The claims are scanned gradually to keep boot fast and avoid lagging the server during uptime. His claim will eventually be removed.
@JSmoove98
You could have saved a day by reading the administrative details page. :) Set automatic new player claim radius to -1.
@chazwarp923
Do it like this for example, for container blocks: [127, 128, 129, 130] where each of those numbers is an ID for a Tekkit container. For example, steam engines should be listed because players can put coal in them.
@LeeTheENTP
If he's not getting an error message explaining why he can't dump lava there, then it's not GriefPrevention. You can try posting a plugin list, but I can't guarantee that I'll recognize all the plugins on it.
@defkult
world.getSeaLevel() - 4
I think the sea level reported by Bukkit is 64, but the actual water level in the world is 60. I'm not 100% certain of that. Try standing next to a stream and pressing F3 to get your Y coordinate.
@sirmyllox
Thanks, I appreciate your help. :)
-
View User Profile
-
Send Message
Posted Oct 1, 2012@ryanwagner
Actually, I'd call that a blessing! Those paintings weren't done by Monet or Constable, now were they? :D
-
View User Profile
-
Send Message
Posted Oct 1, 2012Hi.
Bigscary, i respect your choice of not making region specific commands and features. I hope you dont mind that i have requested an addon plugin to GP.
I know there are users of this plugin who would like to see such feature, please support the request by taking the poll in my plugin request.
you can find it @ http://forums.bukkit.org/threads/req-griefprevention-addon.103434/
cheers sirmyllox
@JSmoove98 I Believe you should set "AutomaticNewPlayerClaimsRadius:" to -1
-
View User Profile
-
Send Message
Posted Oct 1, 2012@bigscary
I love this plugin! However there is one simple feature missing which would allow for so much more flexibility.
I am setting up the plugins for a mostly-vanilla pvp server and do thorough testing before running it with new plugin configuration.
As I was testing I found this issue: The ability for people to use /BuyClaimBlocks is a way for them to protect their money in the form of claim-block assets so that they can't lose their money on death and it can't be transferred to the player who defeated them (gold nuggets are currency and you lose all that you are carrying at the time).
Is there a way (or could it be added) to make it so that users cannot purchase claimblocks, but instead as they make a claim it charges directly from their money after highlighting the claim and prompting the user for confirmation asking if they actually want to purchase that land.
If there is no way of doing this currently or you don't think it should be added to the plugin, then would you mind if I try to add it into the plugin for my server? (I've not made a plugin before but I have Java experience) If this doesn't end up working I might have to use a different anti-greifing plugin that does take money directly on claiming land, but I really like this plugin and hope that this works.
-
View User Profile
-
Send Message
Posted Oct 1, 2012I retested with 6.6 and I am still getting creepers blowing paintings off the walls when they explode.
I am also on 1.3.2 R1 now and still have the same issue.
-
View User Profile
-
Send Message
Posted Oct 1, 2012Hi,
I've been using this plugin on my server for a while now, but on the latest release I ran into a few issues with the addition of the blocked teleportation during pvp.
It would seem that it blocks players being teleported after they have died in some arena events and instead of spawning them in the 'spectator' area, it will respawn them back to their point of death inside the arena.
I've tried unblocking the commands, but that didn't seem to work. I figure is has something to do with the pvp timer persitisting after these 'fake' deaths maybe.
I've had to switch back to the previous version for now, but hope I can get the benefit of the other updates in a future release..
-
View User Profile
-
Send Message
Posted Sep 30, 2012@LeeTheENTP
Do you know the y value off the top of your head by chance?
-
View User Profile
-
Send Message
Posted Sep 30, 2012@defkult
Y-coordinate value. Bigscary probably figured that overall, under a certain Y-value is under the surface.
-
View User Profile
-
Send Message
Posted Sep 30, 2012How does this plugin determine if the tnt block is placed underground or not?
-
View User Profile
-
Send Message
Posted Sep 30, 2012Alright, well now I have a problem that I'm not sure how to solve. Whenever my buddy tries to dump lava in his claim, it disappears. This also happens outside his claim and underground. Is there anything that can cause this? I can give a plugins list if you need it.
-
View User Profile
-
Send Message
Posted Sep 30, 2012Could I Please Get An example Config Cause im Not Sure How To Add Tekkit Blocks To The List Of Things That Need Permission To Open
-
View User Profile
-
Send Message
Posted Sep 30, 2012How do I stop it from creating a claim when someone places a chest? Also, how do I stop it from remiving lava and water when someone unclaims there land?
-
View User Profile
-
Send Message
Posted Sep 30, 2012@botg_smp
I think the claims removed by IdleLimitDays are only actually deleted when the server is rebooted/reloaded. Give it a try. :)
-
View User Profile
-
Send Message
Posted Sep 30, 2012I've got 'IdleLimitDays: 30' and have reloaded the plugin, however I still have a player with a claim that is not being deleted, they last logged on 35 days ago... any idea?
-
View User Profile
-
Send Message
Posted Sep 30, 2012I like this one, thanks.
Are there already any german locales or is this plugin english only?
-
View User Profile
-
Send Message
Posted Sep 30, 2012@instinxx
I would just use /adminclaims to make the claim and /transferclaim <player_name> to change the ownership of that claim to a named player. Easier than messing about with the server files. ;)
<edit> player doesn't have to be logged in for you to transfer the ownership of a claim to them.
-
View User Profile
-
Send Message
Posted Sep 29, 2012@bigscary
I can't seem to reproduce it, but the guy that told me about it said that it happens in our creative plots world and it then allows him to build in any plot. I don't have GP enabled in that world, so it shouldn't even be affecting it.
I have had a few people try it and they can't do it. I even had him try it and he couldn't replicate it. So, until someone can show me that it works, it's fixed.
-
View User Profile
-
Send Message
Posted Sep 29, 2012one of my mods on our server came up with a nice idea for the "blocks per hour" system, another config option that would allow you to turn the "blocks per hour" into an "exponential" system.
For instance: ExponentialBlocksPerHour
if set to a value higher than 1, it would take your current blocks amount and multiply it by that number and give you the answer.
So if you have 100 blocks, and the value is 1.5, you would now have 150 blocks. at 700 blocks you would have 1050.
Is this a possibility? the default value for the config option would be 1, which would tell it to use the regular 'BlocksPerHour', anything lower than 1 would default to that too, anything higher would go to an exponential system.