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 23, 2013Do you think that you could make the monitored slash command for the spam detector case insensitive, please? I had a player come on my server and start spamming by using an uppercase command.
-
View User Profile
-
Send Message
Posted Jan 23, 2013@bigscary
There is one thing you can do about those cases: Adding the option to disable ender pearl use on claims. It would be a really nice feature as I am having to block ender pearls altogether on my server to prevent abuse. Plus isn't your plugin all about preventing abuse?
-
View User Profile
-
Send Message
Posted Jan 23, 2013@Moochiez
Not unless one of your worlds is a creative world. If it is, add its name to the "creative rules worlds" list. Then players will have to claim before building in that world. It's not an appropriate option for survival worlds because there are many other rules for those worlds, like for example monsters and animals not spawning outside of land claims (to prevent entity griefing through breeding, eggs, or villager machines).
@deleted_9935739
No sorry, tell your players to design their builds for ender pearl security. :) It will be an interesting building challenge for them.
EDIT: There are some Mojang bugs with ender pearls that allow players to walk through locked doors and some other blocks. There's nothing I can do about those cases.
@coletam
The smart ban only auto bans accounts which have never been on the server before. The only way to let those players on (if you really believe its not just the banned player trying to get back in), then you have to /pardon the original banned account (and potentially disable the smart ban, since you don't like how it works).
I will investigate to confirm there's not a new bug somewhere which has made my statements incorrect, but that's the design anyway (and it worked this way previously).
@Tr33x0rs
Sorry sir, I don't know how to fix your somehow mysteriously corrupted database. :\ I don't even understand exactly what that error message means.
@ircopdd
Root problem: 97 plugins. Sorry, can't help you. Be sure to keep your "limit surface water buckets" set to true.
@bunnyhop100
It's because grief prevention only listens for right click, which is how all the other containers and crafting blocks work. Maybe you could ask the other dev to switch to right click, or at least give you a config option for that?
@diannetea
Will you please provide more information about your problem? What are players doing with the ender pearls, and how big is the impact?
@yrula8
Very glad you like it. :)
-
View User Profile
-
Send Message
Posted Jan 22, 2013The best plugin I have ever used! Replaced it with 3 others that was lagging down the server. Simple and really intuitive for the players on my server, especially the video links. Now if they get griefed its their own fault for not expanding their protection area. Keep up the Great Work!
-
View User Profile
-
Send Message
Posted Jan 22, 2013I was just going to request the enderpearl thing, right now I have them completely disabled but I'd prefer they are just disabled in untrusted claims
-
View User Profile
-
Send Message
Posted Jan 22, 2013@bunnyhop100
I was able to solve this issue switching the block IDs to access trust required rather than container. So I no longer require assistance. Thank you
-
View User Profile
-
Send Message
Posted Jan 22, 2013The factorization mod uses a chestlike item called barrels which function a bit differently than opening a chest. By punching (left click) on the item a player can remove contents from the barrel.
Despite adding in the correct block ID, grief prevention seems to allow untrusted uses to perform this interaction with the block.
Do you have any suggestions on how to block such behavior with your plugin or is this something you could add into the plugin?
-
View User Profile
-
Send Message
Posted Jan 22, 2013Total duration: 6380.16 ms / 150 ticks
Average duration: 42.534 ms/tick
Selected event: BlockFromToEvent[LOWEST]
Plugin: GriefPrevention
Location: class me.ryanhamshire.GriefPrevention.BlockEventHandler
LimitSurfaceWaterBuckets: false
LimitSurfaceWaterBuckets: true
no work
is lag
please help me fix lag
thanks
my Computer
cpu i7 3930k
ram 32gb
i have 97 plugin
only GriefPrevention very lag
GriefPrevention: 5841 total claims loaded.
GriefPrevention: 1371 players have staked claims.
-
View User Profile
-
Send Message
Posted Jan 21, 2013Not exactly sure how or why this happened, but my plugin stopped working and I'm receiving the message of - [INFO] GriefPrevention: Table './mc4844/griefprevention_nextclaimid' is marked as crashed and last (automatic?) repair failed
My host apparently tried to repair the database, but was unable to. I am not sure what this entails. Should I try to delete the table, or is this going to reset all my claims? Thanks for the help, I'm really hoping I dont have all my claims reset, but if i do, i do... Here's a pastebin of the error:
http://pastebin.com/PxJsuW0U Thanks!
-
View User Profile
-
Send Message
Posted Jan 21, 2013@bigscary
I'm pretty sure I know my players on the server... I never said they first joined just right after they were banned. They were playing for well over a few months and one of them broke a rule, which I banned for. So their sibling join later on, and got banned as well. This happened a few times on players I've talked to in the past and I even watched them build together. I would like to know who would actually have two computers on playing 2 accounts at the same time, moving at the same time...as I never seen this happen before.
Another scenario that may be possible is that Brother 1 and 2 both share a computer and takes turn. Brother 1 gets banned, so Brother 2 may log in after to ask why Brother 1 got banned.
This happens a lot on my server since my server has a lot of family players that are either brother/sister or even moms and dads playing. And I really don't think they are the same player, you know, the feeling you have that you know its not the same players and they are telling the truth?
and DetectiveButler, Since I started the map over with a new one, they have no player records on the map. All the files they do have was deleted (essentials and GP playerdata)
-
View User Profile
-
Send Message
Posted Jan 21, 2013Can you make it so that players can't use enderpearls to teleport into/in someone else's claim?
-
View User Profile
-
Send Message
Posted Jan 21, 2013Hi, is it possible to make it so that players in World A can only build and destroy within their plot but on World B they can build and destroy everywhere. Thanks
-
View User Profile
-
Send Message
Posted Jan 21, 2013@Chaett
Oh, yep. I can make a minor change to fix that. I'll try to remember for the next version.
@DetectiveButler
Sorry bro, I just don't have enough free time to try supporting Tekkit Lite, FTB, CraftBukkitPlusPlus, Spout, and all the other variants. Probably there's some problem with Bukkit Forge. One hint I can give you - find out which Minecraft version your Tekkit Lite is based on, and be sure to get a Grief Prevention version made for that version of CraftBukkit. For example, try 5.5.1.
@ManBeastPigDev
It actually says "plant" that here? It's definitely not Grief Prevention. I have no messages involving planting anything.
@confuser
I'm wondering why you're the only person complaining of this issue. Perhaps one of your other plugins is doing something not-so-normal with chunks? No, I'm not subscribed to the chunk load event.
@coletam
The sibling or friend is not actually a sibling or friend. It's very likely the same player lying to you about not being himself, so that you will allow him in. Ask yourself - why would a new player come join the server for the first time AFTER his friend or brother was banned? Well, he wouldn't. If this were a friend or brother who had been playing with the banned player before you banned him, then that friend or brother would not be auto-banned because he had been on the server before. So it must be the banned player is trying to trick you.
@thorincumming
Oh, you want the list to be empty? Then add a world to the list which isn't a world. Like "fake_world". Then GP will not default back to all worlds.
-
View User Profile
-
Send Message
Posted Jan 21, 2013@coletam
I have no clue if this is the answer, however, have you tried deleting their player file from the world data directory?
-
View User Profile
-
Send Message
Posted Jan 21, 2013Hello,
Recently, I have used your SmartBan feature and it has been banning griefers with multiple accounts. However, if a sibling or friend tries to join, they will get autobanned as well. I decided to turn off the SmartBan feature and Essentials is still giving them "The ban hammer has spoken" even after I deleted their name from the banplayers.txt file.
Is there a way to unban the players that were banned from SmartBan? Or is there a folder that I am not seeing that is keeping the player banned? I deleted their player files from essentials, I deleted their PlayerData from the GriefPrevention folder, as well as deleting their name from the banplayer.txt list.
Tried googling it, but seems like I am the only player with this problem?
-
View User Profile
-
Send Message
Posted Jan 21, 2013@bigscary
And im doing that but it keeps re-adding them...
-
View User Profile
-
Send Message
Posted Jan 20, 2013@TheReverend403
Like I mentioned, my knowledge on the subject is limited. If the port is impossible at this time, at least I know a little more than I did a day ago.
-
View User Profile
-
Send Message
Posted Jan 20, 2013<<reply 1205100>> *How do i get this right? Only shows ' <reply 1205100>' and not the actual post I am replying to?*
@ManBeastPigDev
I've had the problem with flower pots also and I noticed other people who also had this problem on forums. Seems it was caused by WorldGuard 5.7.
The latest dev build has it fixed (WorldGuard 5.7.1). Here is the link to the creators Jenkins page:
http://build.sk89q.com/job/WorldGuard/
-
View User Profile
-
Send Message
Posted Jan 20, 2013Still getting concurrent exceptions causing server crashes. Are you using the ChunkLoadEvent at all?
-
View User Profile
-
Send Message
Posted Jan 20, 2013@DetectiveButler
That's because plugin support for Tekkit Lite is VERY limited.
You are aware that BukkitForge is very early work, right?