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 Dec 5, 2012@ThisUsernameIsMine
I'm using Spigot, had to go back to #285 to stop all the errors. None the less the plugin authors have to update a fix around this issue.
WorldGuard, GriefPrevention, GriefLog, and Factions are all effected by this change.
-
View User Profile
-
Send Message
Posted Dec 5, 2012@ Zilacon: I believe its due to a change in (Craft)Bukkit, starting from build #2505. Try an older build and u'll see ;-)
edit: Fire EntityFormBlockEvent for FallingBlocks. Adds BUKKIT-3078
https://github.com/Bukkit/CraftBukkit/commit/8ab8744ebde4eb5c348e6a47826091a5a355ec8b
-
View User Profile
-
Send Message
Posted Dec 5, 2012Getting this error like mad just spamming non stop.
I am using Spigot 1.4.5
-
View User Profile
-
Send Message
Posted Dec 5, 2012Hmm, couldn't edit the post below. But I'd like to report my problems solved. I don't know what did the trick. All I did was raise the amount of blocks gained to 20
-
View User Profile
-
Send Message
Posted Dec 5, 2012@bigscary
It's the way we are setting up our new survival world. Minimal protection. Maximal risk. If it is a little. We know. But we also realise this and are doing it very intentional.
But still nothing is gained. None of the 100 logged players acquired any blocks.
Edit: I upped it to 20 to see what happens. But I don't think that's it. Are you sure there is not some permission I am missing. All I gave them was:
- griefprevention.createclaims
-
View User Profile
-
Send Message
Posted Dec 5, 2012@gjwakker
That bug is already fixed, please update to 7.1.1 and check again. :) If you still have a problem, please tell me and I will look into it (this will mean it's a separate issue that I need to fix).
@TMAC_Kratos
Like Isaac mentioned, if you give containertrust, that's a higher level trust than accesstrust, so it includes accesstrust. Similarly, /trust gives build, container, and access trust.
@dorrax
It doesn't work for creative mode players, and it will be disabled if you were recently in pvp combat, or you disabled it altogether in the config file.
@techen84
Yep, I could do that. But I don't think I will - it's kind of a pain to get ice, and griefers generally don't think of it. Also your /restorenature will wipe it in a flash, and any player can walk over and place a block in the water source to remove it as well.
@RemyPas
Do you mean ten per hour? That means that every 5 minutes or so, supposing the player is moving around a reasonable amount, he will get like 1 block. I can see where a lot of players may get the impression that they're not getting blocks at all.
Really, with a rate that slow, you may as well just turn it off. Increasing a 10x10 claim by 1 block in width would cost the player a whole hour of active playtime, which seems extreme. :)
-
View User Profile
-
Send Message
Posted Dec 5, 2012Hi there,
This plugin has been running perfecly for me. but since I updated my world and did a clean install to wipe all data and claims. The blocks per hour aren't given to my players anymore. I have looked at every setting and I can't seem to find what is wrong. Only thing I did is lower them to ten. But I don't think that's the issue.
Maybe one of you can point me in the right direction.
-
View User Profile
-
Send Message
Posted Dec 5, 2012@TMAC_Kratos
From what I understand, /containertrust gives access to doors, buttons, chests, beds, craft tables, and furnaces. /accesstrust strips everything except access to buttons and doors only.
So if you give someone containertrust, they also have accesstrust
-
View User Profile
-
Send Message
Posted Dec 5, 2012This plugin is EXTRA. I download 1.2.5 version for tekkit and it WORKS :D
-
View User Profile
-
Send Message
Posted Dec 4, 2012Had a tricky griefer place ice blocks in wilderness to get them to melt and make water flow outside of claims. Any way of preventing ice from melting outside of claims ?
-
View User Profile
-
Send Message
Posted Dec 4, 2012@bigscary
Haha it's cool.
-
View User Profile
-
Send Message
Posted Dec 4, 2012I'm having trouble figuring out how to give items to chests I don't have access to. I read that it can be done by left clicking a player's chest, but it's not working. I thought the config was set right, but maybe I'm missing something.
-
View User Profile
-
Send Message
Posted Dec 4, 2012I can not figure this out. Is there a way to give multiple permissions. For instance give the public accesstrust and containertrust.
When i give them containertrust then try to give them accesstrust it removes them from containertrust according to the trustlist command. Is there a way to give them both?
-
View User Profile
-
Send Message
Posted Dec 4, 2012version: v6.9
server verion: 1.4.5-R0.2
can anyone tell me why some players giving this error when I want to see how much land they have?
2012-12-04 21:57:41 [INFO] gjwakker issued server command: /ClaimsList bettyb2000 2012-12-04 21:57:41 [SEVERE] null org.bukkit.command.CommandException: Unhandled exception executing command 'claimslist' in plugin GriefPrevention v6.9 at org.bukkit.command.PluginCommand.execute(PluginCommand.java:46) at org.bukkit.command.SimpleCommandMap.dispatch(SimpleCommandMap.java:186) at org.bukkit.craftbukkit.CraftServer.dispatchCommand(CraftServer.java:502) at net.minecraft.server.NetServerHandler.handleCommand(NetServerHandler.java:985) at net.minecraft.server.NetServerHandler.chat(NetServerHandler.java:903) at net.minecraft.server.NetServerHandler.a(NetServerHandler.java:858) at net.minecraftserverhook.NetServerHandlerProxy.a(NetServerHandlerProxy.java:124) at net.minecraft.server.Packet3Chat.handle(Packet3Chat.java:44) at net.minecraft.server.NetworkManager.b(NetworkManager.java:290) at net.minecraft.server.NetServerHandler.d(NetServerHandler.java:113) at net.minecraft.server.ServerConnection.b(SourceFile:39) at net.minecraft.server.DedicatedServerConnection.b(SourceFile:30) at net.minecraft.server.MinecraftServer.r(MinecraftServer.java:595) at net.minecraft.server.DedicatedServer.r(DedicatedServer.java:222) at net.minecraft.server.MinecraftServer.q(MinecraftServer.java:493) at net.minecraft.server.MinecraftServer.run(MinecraftServer.java:426) at net.minecraft.server.ThreadServerApplication.run(SourceFile:856) Caused by: java.lang.NullPointerException at me.ryanhamshire.GriefPrevention.DataStore.getGroupBonusBlocks(DataStore.java:96) at me.ryanhamshire.GriefPrevention.PlayerData.getRemainingClaimBlocks(PlayerData.java:145) at me.ryanhamshire.GriefPrevention.GriefPrevention.onCommand(GriefPrevention.java:1431) at org.bukkit.command.PluginCommand.execute(PluginCommand.java:44) ... 16 more
-
View User Profile
-
Send Message
Posted Dec 4, 2012@krisdestruction
Oops. Not worth another update just to fix the version number. My bad. :)
@MastaC1058
No sorry, it's either on for everyone, or off for everyone. It's best to have it on for everyone - there's no player which shouldn't protect his builds. If you have another plugin which is offering its own protection in some areas, then I understand your frustration, but it's a rare case to have two block protection plugins on the same server.
It's possible to do that but I haven't because messing with the already complicated resizing code is a nasty business sure to result in lots of bugs, and extremely large claims are rare. If you've created an enormous claim, chances are you're a moderator or operator, and you can use the /tp command to teleport yourself for quick travel, and you might have access to other plugins like WorldEdit, which allows you to right click with the compass for fast travel as well.
-
View User Profile
-
Send Message
Posted Dec 3, 2012Is there a method/command/permission node to disable the WarnWhenBuildingOutsideClaims message for certain people?
Also, would it be possible to modify it so that players can click on the gold blocks in between the corners of a protection to resize that side? Some of the builds on my server are massive, to the point where you can't see the most of the build from the corners.
-
View User Profile
-
Send Message
Posted Dec 3, 2012@bunnyhop100
Tekkit is dead, move onto FTB.
@bunnyhop100
Create a separate world. That's the easiest solution!
Hey big, the version number in 7.1.1 shows as 7.1 instead of 7.1.1.
-
View User Profile
-
Send Message
Posted Dec 3, 2012@RamizWWW
It does work on Tekkit. Read "notes for tekkit servers" above.
@Akabei
There's a config option to disable that. It's supposed to be annoying - if any player is placing lots of blocks outside of his land claims, he's just going to get massively griefed later. It only fires every 15 or so blocks, and ignores trash blocks like dirt, so it doesn't annoy players who are smart enough to do the absolute minimum to protect their work. I promise you the occasional ignoramus who complains about this feature to you is far less annoying than the crowd of players whining later that their builds were griefed because they forgot to expand them after adding that new room.
@FordRacer2007
If you're running a pvp server, you should expect that players will not trust each other. It would be an awful lot of work for me to implement that, and I expect very few players would actually use it. :\ You could suggest to your players that if they don't trust someone, they should gear up before teleporting them over. Then if that player starts a fight, they can kill him.
@Tonysp
This comes up a lot, sorry I can't help you. Something MUST have changed on your end. The database code hasn't been touched in like 20 versions, and the reason I never update it is to avoid nasty bugs that are impossibly hard to investigate and fix. :)
@2Andri
You need to set your sea level in GP's config file. This happens because GP fills holes where it thinks sea level is, and you're running a plugin which changes sea level. If you tell GP where your actual sea level is, this problem will go away. :)
@Carambaz
Even a private server needs land claims. Someone on your server is a jerk waiting to happen, even if only your friends are there. :)
Yep, just clear the worlds list. I think it will auto-reset to all worlds - if it does that, then just put the name of a world that doesn't really exist in there.
@Luficer
Yep, I'm aware of this. It takes a lot of doing to gather up ice and melt it, so I've left it alone. :) Thanks for pointing it out. I could make a rule that ice can't be placed outside of land claims above sea level (same as dumping water buckets), but I don't think it's necessary.
@JaguarJo
Unfortunately, it is impossible for any Bukkit plugin to limit or roll back damage done by EE tools (actually, there's a list of about 60 items which are griefing tools in Tekkit which can't be limited by Bukkit plugins). I recommend TekkitCustomizer for better banning in the future. See "notes for tekkit servers" above.
@killerb1n4ry
Thank you for your compliments. :) The likely problem is that you're running a Tekkit server and are running the wrong version of GP (you need 5.5.1). If that's not it, then one of your other plugins is causing you a problem - and it's a painful process to figure out which one. The best you can do is disable them one at a time until the problem goes away.
@getpsimon
Sorry, it's impossible for me to predict all the crazy things other plugins could do to break Grief Prevention. It's up to you to avoid server plugins which conflict - for example if you were to allow all your players to use world edit, it wouldn't be possible for ANY other plugin to stop them from editing anywhere they want.
@ridddle
As far as I know, the only way is to create a CHEST claim by placing the chest right next to the border of the other claim. This should be a very limited problem, because each player can only have one chest claim at a time.
@Andyroo654
It can't be disabled. But it doesn't work in administrative claims (/adminclaims), so if you have a special place where you don't want players escaping, that's the way to do it. Even if you could disable it, it wouldn't be a good idea - without it, you or one of your moderators must personally respond to save a player from getting stuck, which happens more often than you might expect. The /trapped command empowers players to save themselves immediately rather than waiting for who knows how long for a moderator to help them, and isn't reasonably exploitable due to the lengthy cooldown period.
@bunnyhop100
The best you can do is to have one world for sieging, and another world without sieging. :\
@GrimAOD
I can just imagine the millions of exploits for a setup like that... for example, tossing infinite diamonds over the claim border, then walking outside and picking them up in survival mode. :) Because I think you might be the only server owner to ever use it if I do build it, and avoiding massive exploits would be an equally massive project, I won't add that. Sorry!
-
View User Profile
-
Send Message
Posted Dec 3, 2012Was wondering is it possible to make it so admin claims can set gamemode to creative while inside the claim and revert to servival on exiting am happy to donate to help implement this function
-
View User Profile
-
Send Message
Posted Dec 3, 2012@Andyroo654
You set permissions for configuring /trapped so nobody/everybody/somebody can use the command/function.
@bunnyhop100
I think siege mode is disabled by default and you have to specify your <world_name> in the config.yml to enable siege mode for that world.