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 12, 2012Hi.
I have GP enabled Worlds set to two of my Worlds. but i get the message: NoTeleportPvPCombat: Text: You can't teleport while fighting another player.
when im in one of my hungergames Worlds .. thus preventing hunger games from teleporting me to lobby when i die ... can i bypass this in some way? or disable the pvp protection in GP ?
EDIT: CombatTimeoutSeconds: -1 <<< helped me :)
Thanks
sirmyllox
-
View User Profile
-
Send Message
Posted Oct 12, 2012Hey, I'm sure you remember me having issues with lava igniting nearby blocks, and you said that it was actually a glitch that you fixed. I've been running my server for about a year, and have used your plugin ever since, right now half my server is on fire and it really sucks that I have to modify everything because of lava. Is there anyway you can make this "glitch" optional?
-
View User Profile
-
Send Message
Posted Oct 11, 2012@bigscary
No I haven't found a log in the last months of logs for that particular claim. Found a lot of others though (they look like this: [INFO] GriefPrevention: Removed playername's unused claim @ world(545,45,292)).
Is it possible to make the 7 day and 14 day limit configurable or to disable the cleanup task completely maybe? Then if peoples servers do lag I guess that is their problem. But I think it should be configurable at least since servers come in all sizes.
Also had another idea, could even use a permission node because I have players who go inactive and ask me not to delete their stuff or derank them, especially staff members or long time players who go away but always come back now and then. It sucks when their stuff is griefed and I have to try to piece it together from old rollback databases or whatever else.
In my case I have chest protections and everything else disabled as well because I use LWC.
-
View User Profile
-
Send Message
Posted Oct 11, 2012@ryvix
No, claims belonging to active players will never be removed. So confirmed, you did find a log entry? If so, it's a bug I need to look into.
@myCraftServer
I think it would conflict with the "don't break blocks above sea level with explosions" rule, which is an important protection against large scale wilderness griefing. :\
@VietNg
I guess I could alias it. But you're not deleting the land. Just your claim of that area of land (the land itself is still there). :)
-
View User Profile
-
Send Message
Posted Oct 11, 2012Have you ever considered changing the command from /claim to /land? For instance, /DeleteLand :)
-
View User Profile
-
Send Message
Posted Oct 11, 2012What I think would be good for siege, is an option to have soft blocks, medium blocks and hard blocks.
Hard Blocks: can't be destroyed
Medium Blocks: can be destroyed with TNT
Soft Blocks: can be destroyed with tools/hand.
This would let you 'breach' a wall using TNT. This would be awesome for our server, -Daniel
-
View User Profile
-
Send Message
Posted Oct 11, 2012@bigscary
The claim she had was a claim with a giant sheep with some wool and wood planks and stone brick and fences in it. It was probably about 500 blocks in size. Are you saying even if I tell it not to remove claims it will delete this claim eventually even when the player comes on every day?
-
View User Profile
-
Send Message
Posted Oct 11, 2012@deleted_8314868
Hi rong, I'll check into this. I may have made a mistake somewhere. What do you mean by "it registers"? The sea level change should only impact /restorenature, lava/water dumping, and explosions, and nothing else.
@ChilleCharlie
I don't remember - are you running a creative mode world? If so, that's normal. Removing a claim removes any build there. That's a necessary feature to prevent griefers from claiming + building + unclaiming + building + unclaiming... to cover your world with giant penises, lava towers, swastikas, and other ugly garbage.
@Desertive
If a claim doesn't have anything substantial built in it, it will disappear when the player has been gone for two weeks. When a player gets a free chest claim and doesn't expand it or create additional claims and then is gone a full week, it disappears. Those are the only situations where a claim will disappear, and both require that the player be gone a while, and most importantly, both will be logged in your server log.
It's an important performance consideration to clean up these types of land claims, that's why there's no option to turn it off (performance trumps all other considerations, because a laggy server is a useless server).
Having this information in mind, I think you can effectively investigate specific instances by checking your logs, or asking a couple of quick questions and possibly visiting the location. :) Please let me know if you investigate and afterward believe claims are being removed for any other reasons.
@RasCas
Correction, it's not GP that wrecks your config file. The problem you describe is the same for all plugins. I'm very glad you got the translation done, thanks for posting it! :)
@MCCharlieCraft
It used to be that way, but then folks complained that players could buy any number of blocks. So I can't win. :\ A config option wouldn't be great here, because everyone would be confused as to what exactly it does, since the distinction is nuanced.
@ryvix
See my response to desertive above. I can't remember exactly right now, but I think the rule is a claim will stay even when the player has been gone if he has at least 25 player blocks, where a chest block counts as 10. The purpose of the feature is to remove claims which essentially are just protecting a random slice of wilderness. Please check your server logs for any mention of that player's claims being deleted to confirm your suspicion.
@DeathStapler
/IgnoreClaims. I just thought of a way to stop people from asking this every day. :) Stay tuned for a fix in a future version.
-
View User Profile
-
Send Message
Posted Oct 11, 2012Is there a permission that I can set to allow Admins to open doors, chests, etc. on the claim?
-
View User Profile
-
Send Message
Posted Oct 11, 2012@Desertive
I believe this has happened to me too. At least one protection has randomly disappeared and that player comes on daily and did not remove the protection themself. I thought it had happened before but didn't think much of it at the time. But now that it happened again this isn't looking very good. I have my idle limit settings disabled (set to 0) in the config and new player claims are disabled (set to -1).
-
View User Profile
-
Send Message
Posted Oct 11, 2012Can I make a suggestion?
Make these 2 things separate.
Total Claimable Blocks = # Max Claimable blocks gained thru time based gain = #
This way players would stop gaining extra blocks based on time at a certain point, and would still be able to upgrade with currency. (if vault was installed)
-
View User Profile
-
Send Message
Posted Oct 11, 2012Finally here's my german translation: http://dev.bukkit.org/paste/6380/
It was real hard, because GP overwrites the whole messages.yml with english again if the slightest error occurs. :-(
-
View User Profile
-
Send Message
Posted Oct 11, 2012Hi again.
There have been some rumour going around in my server that the protections just remove themselves sometimes. I know that they can do the protection wrong, but is there a possibility to turn debuggin on? That it will log to console (or other file) when somebody creates a protection, moves it or removes it. This way I can confirm is there a problem.
Thanks for the answer. -D
-
View User Profile
-
Send Message
Posted Oct 11, 2012Today i was surprised by something new, Someone removed his claim, and that also removed half of his house wich was mad of wool... and offcourse there was no way to undo it.. i really still hope one day you might add a way to disable restorenature.. i dont need it on a shovel i dont need it at all, but i dont really care for it beeing there, what i do hate terribly is stuff like this, it removes something and it cannot be undone in any way.. I will be watching some vids and also very soon might start taking java classes, if i can i will add flags, i expect it to take a while though thanks for your tips
-
View User Profile
-
Send Message
Posted Oct 11, 2012@bigscary
I've been trying to use the sea level override, but it does not seem to be working. I set it to 55 but it still registers as somewhere around 60-62 (can't recall the exact data atm)
Does anyone else have problems with the sea level override?
-
View User Profile
-
Send Message
Posted Oct 11, 2012@bigscary
Sounds good, but right now it is outdated. Let's hope, that the developper will update it pretty soon.
-
View User Profile
-
Send Message
Posted Oct 10, 2012@ChilleCharlie
No, getting PvP'd when PvP is turned on is not griefing. There's already spawn camping protection built in, and players can keep bad guys out with an iron door + button. If you want players to opt out of PvP when they're not feeling it, give them a plugin with /pvp toggle.
Maybe somebody will create an extension plugin which will let you add flags like "no pvp", but I've been waiting a long time for somebody to do it and no luck yet.
@Zidane3838
No, sorry. Maybe you don't mind a little CAPS, but most players are annoyed by it.
@ChilleCharlie
Use Eclipse. Watch some youtube tutorials specific to Minecraft plugin development to get your initial setup going.
@RasCas
There's a real estate extension plugin. :) See link above. It's not exactly what you're asking for, but it's pretty close.
@sirmyllox
I'm not planning to do any of the extension ideas myself, precisely because I'm already overbooked on maintenance. I'm the dev for 5 plugins, and run 4 public servers. I'd love to see some of these things done (especially the flags, so people can stop using WorldGuard), but I won't commit the bandwidth to do it myself.
@ThisUsernameIsMine
This plugin has been available for almost a year now, and you're the first to even mention this area. I think you're looking for problems where there are none. :) Anyway, you can delete them yourself as I mentioned. Let me know if this actually becomes a for real issue for you in practice - in that case, I will reconsider (no promises for changes).
@deleted_8314868
You're correct in that sea level is used to determine underground. Try reducing the sea level in your config by one more.
Also, silk touch to get ice block, place ice block near lava. Ice block melts, turning lava into obsidian. This doesn't work to grief claims because the water will not flow from outside the claim (where the ice block was placed) to inside the claim, but it would work to place water outside of claims. Because it takes a lot of effort to get the silk touch and collect the ice and the result isn't awful (/RN to clean up water) I haven't bothered to block this. Maybe I should.
-
View User Profile
-
Send Message
Posted Oct 10, 2012Actually, ignore that, seems the problem is that buckets actually can be placed at level 59. (sea level is 58 in my map) Would setting my sea level lower fix this? I'll try.
EDIT: Nope. Humbly requesting a setting be added for what is defined as ''the underground''.
-
View User Profile
-
Send Message
Posted Oct 10, 2012Hey, my map is a custom one where, amongst other things, water is replaced with lava. So, as you can probably imagine, the function to enable water placing in claims only is invaluable to me.
This morning however, i woke up to an entire lava lake having been turned into obsidian. The bucket-blocking had bugged out again.
It happens occasionally, seemingly randomly, without me changing any settings at all. Could anyone tell what I'm doing wrong to make this happen? I'll attach a paste of my config if that helps.
http://pastebin.com/jnzmY6D0
-
View User Profile
-
Send Message
Posted Oct 10, 2012@bigscary
None of them are useless, those players may return later. I run four test servers, and the biggest one has 11,098 player data files. The total size of all these files is only 340 kilobytes.
The (real) total usage also depends on the cluser size of your hdd ;-)