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 20, 2012OK. This server would be PERFECT, and i mean PERFECT, if there were a few things added to it.
1. Permissions to switch the following features on and off for certain groups. 2. A way to have players, instead of requiring an admin to give the command, able to claim a single subplot in an area. 3. A way to allow defined areas to be claimed by players in #2.
It sucks, because without this I have to keep using world-guard. I would love to see these features. Thank you for your time plug-author.
-
View User Profile
-
Send Message
Posted Oct 20, 2012Hello, I am having trouble enabling claims on other worlds, the config is like this: Claims: Worlds: - world - world_the_end - world_nether - Resource
but the Resource world never gets claims enabled. I'm using the Transporter plugin to create and load the Resource world. Anyone knows why I have this problem?
-
View User Profile
-
Send Message
Posted Oct 20, 2012@EnergyCraft
Du har skjult den del af config filen, hvor fejlen er, og så kan jeg se at det ikke er den eneste fejl du har lavet.
You have hidden the part of the config with the error, and i can see, thet itøs not the only mistake you made.
-
View User Profile
-
Send Message
Posted Oct 20, 2012Heya i translatet everything now but i got a problem i tried a lot of things to fix this but coulden't here's a pic of what it's saying http://i.imgur.com/V4ILd.png
-
View User Profile
-
Send Message
Posted Oct 20, 2012can i prevent lava spread in claims, like i can with firespread ?
-
View User Profile
-
Send Message
Posted Oct 20, 2012Hey Bigscary, I have an idea for GriefPrevention.
If it wouldn't be too resource-consuming, I think it would be a nice idea to add the option for claim owners to toggle mob spawns.
I saw this with Towny, and I thought: why shouldn't GP be able to do this?
-
View User Profile
-
Send Message
Posted Oct 20, 2012@Juelz0312 If you have Essentials on your server, one of the plugins that comes in the Essentials bundle is EssentialsProtect. By default, it prevents players from placing/activating TNT/lava. I would just delete the plugin if I were you because GriefPrevention essentially (no pun intended) does the same thing, only better.
-
View User Profile
-
Send Message
Posted Oct 20, 2012lol i found a bug in version 6.8 Inside someone elses claim you can use sponge to remove the water? wtf i didnt even know that you could use sponge for removing water! but it can be done inside someone elses claim XD
-
View User Profile
-
Send Message
Posted Oct 19, 2012Hey BigScary,
Thanks, your the best really.
Yea i know what i changed, is absolutely not even close to the best solution. Though i have really not a single clue yet, nor time to figure out how to read stuff out of the config file. But as i said, im totally completely new with java so i was not going to do it right as i needed a solution for this fast. and learning java is not going to be fast... you must know that. I was getting really bored of searching through the files :) all the time or fixing up removed claims from admins, they all tend to make the mistake once... even though you tell them.
Awesome youve put it in the new version! :) ill replace it tommorow when i have some time for checking all the plugins again.
ps: i did make the mistake too myself so aint blaming anyone on it :) these are things you will find out.. you just will.. thats how you learn it.. but then there was no alternative to remove the claims so it was actually the only way, thats now solved :)
-
View User Profile
-
Send Message
Posted Oct 19, 2012Many thanks for the update, bigscary. It's all working like a wet dream. :) :) :)
-
View User Profile
-
Send Message
Posted Oct 19, 2012Users can't place tnt, what's the permission to place tnt? I can't seem to find it. Also the same with lava.
-
View User Profile
-
Send Message
Posted Oct 19, 2012@bigscary
Oh I just edited my previous post and didn't realize you had posted this one already. But yeah, I guess my problem still exists even if I set the sea level for some strange reason.
-
View User Profile
-
Send Message
Posted Oct 19, 2012@briankdk
The arena plugin developer can fix it. Instead of cancelling the death and teleporting the player, he should allow the player to die and just change the player's respawn point using the PlayerRespawnEvent. The end result will be the same - respawn at the right location, and the player can even be made to keep his items or whatever, but there will be no teleportation involved so GP will not complain.
As a temporary workaround, you could set the pvp counter length to zero in the config, but the side effect will be that players can log out during combat.
@xtremetom
Yep, there's no fix for that. Bukkit doesn't know about Tekkit pipes. Don't put containers on the edge of your claim, or extend your claim out one more block.
@ryvix
Yeah sorry, there's no automatic fix on my end. That's why I added the option to override sea level. For flat maps, when I ask Bukkit "what's the sea level?", it tells me 60-something, which is totally wrong for flat maps. So you guys as server admins have to tell me what the correct sea level is when you have a non-standard map generated.
-
View User Profile
-
Send Message
Posted Oct 19, 2012Thanks for adding a config =)
I also noticed in the creative worlds if you don't reset your sea level it will for some reason put random land chunks up at 63 as you fly around and they will overwrite stuff. These are worlds I created with Multiverse with Normal -t flat or whatever it is to make a creative world.
Edit: OK, so actually it seems even if I set the sea level to 5 and disable restore nature options it still places land up in the air when I stand in a claim in the creative world and do /deleteclaim.
-
View User Profile
-
Send Message
Posted Oct 19, 2012Bit of an issue...... u can pump items out of protected chests if they sit on the edge. Simple redstone wooden pipe setup.
-
View User Profile
-
Send Message
Posted Oct 19, 2012i cant get this arene to work, can it be Grief prevention that does son i cant die ?
http://dev.bukkit.org/server-mods/ultimatearena/?page=2#comments
-
View User Profile
-
Send Message
Posted Oct 19, 2012@RasCas
Just ignore it. It doesn't know the administrator who created the claim was you. I'll try to remember to remove that inactivity notification for administrative claims.
@zSwayz
Yep, see administrative details page linked above. I think you want to set new player chest claim radius to -1.
-
View User Profile
-
Send Message
Posted Oct 19, 2012Is there a way to remove the automatic new player claim radius for chests? i have LWC, and this just causes problems :S
-
View User Profile
-
Send Message
Posted Oct 19, 2012@bigscary
There seems to be a bug in the last login. With this version it says this block is owned by an administrator last login 367 days ago. But i am online ;-)
-
View User Profile
-
Send Message
Posted Oct 18, 20126.8 Updates!
@out2k
I don't think I fully undersatnd your questions. You can set the maximum accrued (meaning over time) blocks in the config file, which will set a max for most players. Then you can either use /acb on a per-player basis to reward donators, or use /acb with a permission node to give extra blocks, and then give players who donate that permission. Either way, they will get the # of claim blocks you specify. You don't have to worry about players taking over the map - I've had the defaults on for 10 months on my test server, and nobody has enough blocks that they could make life hard for other players.
10x10 means your area has to be at least 10 blocks wide and 10 blocks deep, which is at least 100 total claim blocks in area.
@Marenwynn
If you take a world out of the "claims.worlds" and "claims.creativerulesworlds" configs, then it will not require claims to build, and it will also be impossible to create claims there. I should warn you that any creative mode world with no land claiming requirement will be griefed to to the extreme, since any griefer can place his infinite supply of blocks anywhere he wants without limitation.
Not without using /siege, no. Siege is a good mechanic - it allows people to "attack bases" but only when the owner is there to defend his turf. Without that reasonable rule set, disconnecting from the server would open a player up to grief.
You can experiment with some ideas - for example you could have one world where there are no land claims. It doesn't even have to be a normal world, you could for example make your nether a pvp zone where no build can be protected.