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 Feb 22, 20121.8.1 updates!
This is the first non-beta release of GriefPrevention. WOOHOO! Lots of bug fixes.
1. /trust and family are now case insensitive, and work for online and offline players, even for players who are on the server for the very first time.
2. Similarly, /deleteallclaims should work.
3. Exploded trees will not leave treetops.
4. Booted players will still get their claim blocks.
5. Endermen "griefing" your claim might be fixed. Or it might not, reports vary. :)
-
View User Profile
-
Send Message
Posted Feb 22, 2012Your update to add permissions made my day also, could i ask for multiworld claimblocks and perhaps MySQL support?
thank you again ;)
-
View User Profile
-
Send Message
Posted Feb 22, 2012@Tux2
they can't for me, check your other plugs ;)
@zathrus_writer
yeah i used to use creeper heal back in 1.7.3 its good and all however this plugin satisfies my needs, protect users crap, and i don't care if everything outside the claim is destroyed, it doesn't mean shit to me :P and since that chunk restore was added now i can just sit in the air and click click click done this is great for when populated areas get stripped of resources, granted that diamond ore someone found is in the same place as before but hes still gotta get his ass down there XD
-
View User Profile
-
Send Message
Posted Feb 22, 2012@Tux2 amazing! I was really worried about implementing this after your wool generator bug report... I feel much better now :-P
-
View User Profile
-
Send Message
Posted Feb 22, 2012@cvxx7q
Gotcha, I'll give some technical info:
This is running in a Xen VPS off of SSD hard drives. The OS is CentOS release 5.6 (Final)
These times are taken from the same timings file with CraftBukkit 1.1-R4. I run both because of the mall in my beginner's world. Otherwise Residence would be gone.
Residence v2.4.4
PlayerQuitEvent Time: 186000 Count: 11 Avg: 16909
PlayerMoveEvent Time: 1623366000 Count: 178754 Avg: 9081
PlayerInteractEvent Time: 380329000 Count: 7160 Avg: 53118
BlockBreakEvent (and others) Time: 130141000 Count: 2225 Avg: 58490
BlockPistonExtendEvent Time: 37790000 Count: 209 Avg: 180813
BlockPistonRetractEvent Time: 23456000 Count: 209 Avg: 112229
EntityDamageEvent (and others) Time: 212100000 Count: 8240 Avg: 25740
EndermanPickupEvent Time: 8559000 Count: 236 Avg: 36266
EntityExplodeEvent Time: 298000 Count: 6 Avg: 49666
BlockBurnEvent Time: 246000 Count: 4 Avg: 61500
BlockPlaceEvent Time: 85224000 Count: 1918 Avg: 44433
BlockFromToEvent Time: 293887000 Count: 9692 Avg: 30322
PlayerChatEvent Time: 99000 Count: 10 Avg: 9900
CreatureSpawnEvent Time: 476778000 Count: 25481 Avg: 18711
BlockSpreadEvent Time: 8043000 Count: 298 Avg: 26989
PlayerBucketEmptyEvent Time: 3359000 Count: 78 Avg: 43064
BlockIgniteEvent Time: 31886000 Count: 967 Avg: 32974
PlayerBucketFillEvent Time: 4425000 Count: 87 Avg: 50862
ExplosionPrimeEvent Time: 566000 Count: 6 Avg: 94333
PaintingBreakEvent Time: 2591000 Count: 391 Avg: 6626
EndermanPlaceEvent Time: 916000 Count: 27 Avg: 33925
Total time 3324245000 (3s)
GriefPrevention v1.8
PlayerJoinEvent Time: 13889000 Count: 14 Avg: 992071
PlayerQuitEvent Time: 4945000 Count: 11 Avg: 449545
PlayerRespawnEvent Time: 178000 Count: 4 Avg: 44500
PlayerInteractEvent Time: 223979000 Count: 7160 Avg: 31281
BlockBreakEvent (and others) Time: 68671000 Count: 2225 Avg: 30863
BlockPistonExtendEvent Time: 10382000 Count: 209 Avg: 49674
BlockPistonRetractEvent Time: 1331000 Count: 209 Avg: 6368
EntityDamageEvent (and others) Time: 19862000 Count: 8240 Avg: 2410
EntityExplodeEvent Time: 2491000 Count: 6 Avg: 415166
BlockBurnEvent Time: 84000 Count: 4 Avg: 21000
BlockPlaceEvent Time: 37564000 Count: 1918 Avg: 19584
BlockFromToEvent Time: 193128000 Count: 9692 Avg: 19926
PlayerChatEvent Time: 32000 Count: 10 Avg: 3200
BlockSpreadEvent Time: 1154000 Count: 298 Avg: 3872
PlayerBucketEmptyEvent Time: 1900000 Count: 78 Avg: 24358
BlockIgniteEvent Time: 3872000 Count: 967 Avg: 4004
PlayerCommandPreprocessEvent Time: 86000 Count: 27 Avg: 3185
PlayerLoginEvent Time: 43000 Count: 14 Avg: 3071
PlayerPickupItemEvent Time: 17167000 Count: 5838 Avg: 2940
PlayerBedEnterEvent Time: 231000 Count: 3 Avg: 77000
PlayerBucketFillEvent Time: 2474000 Count: 87 Avg: 28436
PaintingBreakEvent Time: 1428000 Count: 391 Avg: 3652
PlayerItemHeldEvent Time: 36370000 Count: 1959 Avg: 18565
PlayerInteractEntityEvent Time: 137000 Count: 7 Avg: 19571
Total time 641398000 (0s)
Also, seems the wool dupe bug was a setting in CreeperHeal I forgot to disable regarding regenerating burned blocks.
EDIT: Forgot to report that griefers can still put out fires on netherrack with this plugin installed which is very frustrating to my players.
-
View User Profile
-
Send Message
Posted Feb 22, 2012does this handle moded blocks? ie ic2 buildcraft etc?
-
View User Profile
-
Send Message
Posted Feb 21, 2012watch this video
http://www.youtube.com/watch?v=rJp86_tj9KQ&feature=related
imagine the people asking for fire support are the guy in the red shirt (aka Fry)
and the old guy is BigScary
......
Point Illustrated: people don't seem to pay enough attention, and as you can imagine this can become annoying so pay a little more attention and save frustrating the author having to explain something over and over ;)
@bigscary, perhaps the explanation for not allowing fire should be added in a small FAQ list, if you think it will actually get read..
@Tux2
another thing is the plugin writes to individual files and doesn't have to re-parse a huge single file of claims, this allows the OS's I/O queue to schedule stuff, how reliable this is? depends on the OS and its scheduler, of course someone will tell you *nix's have the best I/O however each one is different, since this is indeed running a server (in every aspect) i hear UNIX as a server OS is very scalable and therefore considered "best" however this will always differ due to configuration.
-
View User Profile
-
Send Message
Posted Feb 21, 2012@Tux2
thanks for the valuable info :-) ... now I'm starting to miss a toggleable "allow-fire" flag in the config file as well :-D
-
View User Profile
-
Send Message
Posted Feb 21, 2012@Tux2
why did it take you so long to report this? lol u told me about this over a week ago XD
-
View User Profile
-
Send Message
Posted Feb 21, 2012@leezallen
yes, shutdown the server and edit the claim files or else no
-
View User Profile
-
Send Message
Posted Feb 21, 2012I haven't got many issues with the plugin but I got:
00:31:08 [SEVERE] Could not pass event org.bukkit.event.player.PlayerInteractEvent to GriefPrevention java.lang.IllegalStateException: Start block missed in BlockIterator at org.bukkit.util.BlockIterator.<init>(BlockIterator.java:167) at org.bukkit.util.BlockIterator.<init>(BlockIterator.java:254) at org.bukkit.util.BlockIterator.<init>(BlockIterator.java:287) at org.bukkit.craftbukkit.entity.CraftLivingEntity.getLineOfSight(CraftLivingEntity.java:90) at org.bukkit.craftbukkit.entity.CraftLivingEntity.getTargetBlock(CraftLivingEntity.java:116) at me.ryanhamshire.GriefPrevention.PlayerEventHandler.onPlayerInteract(PlayerEventHandler.java:352) at org.bukkit.plugin.java.JavaPluginLoader$11.execute(JavaPluginLoader.java:340) at org.bukkit.plugin.RegisteredListener.callEvent(RegisteredListener.java:61) at org.bukkit.plugin.SimplePluginManager.callEvent(SimplePluginManager.java:460) at org.bukkit.craftbukkit.event.CraftEventFactory.callPlayerInteractEvent(CraftEventFactory.java:187) at org.bukkit.craftbukkit.event.CraftEventFactory.callPlayerInteractEvent(CraftEventFactory.java:157) at net.minecraft.server.NetServerHandler.a(NetServerHandler.java:852) at net.minecraft.server.Packet18ArmAnimation.handle(SourceFile:38) at net.minecraft.server.NetworkManager.b(NetworkManager.java:226) at net.minecraft.server.NetServerHandler.a(NetServerHandler.java:100) at net.minecraft.server.NetworkListenThread.a(NetworkListenThread.java:78) at net.minecraft.server.MinecraftServer.w(MinecraftServer.java:537) at net.minecraft.server.MinecraftServer.run(MinecraftServer.java:435) at net.minecraft.server.ThreadServerApplication.run(SourceFile:465) 00:31:08 [SEVERE] Could not pass event org.bukkit.event.player.PlayerInteractEvent to GriefPrevention java.lang.IllegalStateException: Start block missed in BlockIterator at org.bukkit.util.BlockIterator.<init>(BlockIterator.java:167) at org.bukkit.util.BlockIterator.<init>(BlockIterator.java:254) at org.bukkit.util.BlockIterator.<init>(BlockIterator.java:287) at org.bukkit.craftbukkit.entity.CraftLivingEntity.getLineOfSight(CraftLivingEntity.java:90) at org.bukkit.craftbukkit.entity.CraftLivingEntity.getTargetBlock(CraftLivingEntity.java:116) at me.ryanhamshire.GriefPrevention.PlayerEventHandler.onPlayerInteract(PlayerEventHandler.java:352) at org.bukkit.plugin.java.JavaPluginLoader$11.execute(JavaPluginLoader.java:340) at org.bukkit.plugin.RegisteredListener.callEvent(RegisteredListener.java:61) at org.bukkit.plugin.SimplePluginManager.callEvent(SimplePluginManager.java:460) at org.bukkit.craftbukkit.event.CraftEventFactory.callPlayerInteractEvent(CraftEventFactory.java:187) at org.bukkit.craftbukkit.event.CraftEventFactory.callPlayerInteractEvent(CraftEventFactory.java:157) at net.minecraft.server.NetServerHandler.a(NetServerHandler.java:852) at net.minecraft.server.Packet18ArmAnimation.handle(SourceFile:38) at net.minecraft.server.NetworkManager.b(NetworkManager.java:226) at net.minecraft.server.NetServerHandler.a(NetServerHandler.java:100) at net.minecraft.server.NetworkListenThread.a(NetworkListenThread.java:78) at net.minecraft.server.MinecraftServer.w(MinecraftServer.java:537) at net.minecraft.server.MinecraftServer.run(MinecraftServer.java:435) at net.minecraft.server.ThreadServerApplication.run(SourceFile:465) Not a huge issue, only noticed it once but it could have happened a couple of times. Just thought i'd report it
-
View User Profile
-
Send Message
Posted Feb 21, 2012@zathrus_writer
I can't say anything about huge servers but my server consistently has around 4-17 players on it all the time. I haven't noticed any lag associated with this plugin and have benchmarked it and found it more efficient than residence. (Both running off of flat files on my server)
-
View User Profile
-
Send Message
Posted Feb 21, 2012I've got a BIG bug here with grief prevention. Evidently since fire can't burn wool and wood planks anymore my users have found out how to make "wool and plank" generators. Concept:
Place wool, place a fire right behind the wool on burning netherrack. Build en-masse and profit! I've had players gather thousands upon thousands of wool in the matter of an hour using this method. I had one player leave it running when he went offline and he lagged the whole spawn until we finally got down there to remove all the entities. If you could figure out a way to disable this I would be extremely grateful.
-
View User Profile
-
Send Message
Posted Feb 21, 2012Hi couple of questions!!!!
1. Are you thinking of adding group protection to areas as well as players?
2. Is there anyway of transferring ownership of a claim?
-
View User Profile
-
Send Message
Posted Feb 21, 2012@bigscary
oh, then I must have misunderstand the video about admin claims... is shows some sort of a chest gadget which has a wooden sword and claims to regenerate that sword after about 5 minutes... so it's some other plugin you use for that?
and sry for the waterfall of questions, but I'm a bit concerned as to how nicely this could scale if no DB is used for large servers - any benchmarks / experience on that anyone? I know author says DB is a hassle, but DBs have indexes and don't need to search through a whole text file as I see it (maybe I'm wrong here with how this plugin works), so I'd like to know :-)
-
View User Profile
-
Send Message
Posted Feb 21, 2012@Jadedwolfs
When you equip your golden shovel, you'll be told how many claim blocks you have (assuming you have at least enough to create the minimum size claim). There's no command to check another player's claim blocks, but if you really want to know, add the two numbers together you see in the player's grief prevention data file. The first is how many they've earned through play, the second is how many they've purchased or been gifted by admins.
@CrystalPriizon
No, that kick problem with the end is either a craftbukkit issue or a Mojang issue. It will happen whether you have this plugin installed or not.
When fire spreads, there's no way to tell reliably who originated the fire. So the only safe thing to do is to block all fire spread, sorry. You can still use fire on netherrack to decorate, and on obsidian to create a portal.
Check the admin details page. There's not a list, but the permissions are highlighted in bold. I'll work on a list, but right now I have a lot of bugs and features to work on.
-
View User Profile
-
Send Message
Posted Feb 21, 2012@zathrus_writer
Chests don't regenerate stuff with this plugin. If you're running another plugin that does that sort of thing, then you might use GriefPrevention to protect that chest from being destroyed or blocked by a player.
@Arahsi666
Yeah, sorry, nothing I can do about other plugins which allow players to edit the world anonymously.
-
View User Profile
-
Send Message
Posted Feb 20, 2012@CrystalPriizon
http://dev.bukkit.org/server-mods/grief-prevention/pages/administrative-details/
bottom section.....
-
View User Profile
-
Send Message
Posted Feb 20, 2012Is there a list of permissions somewhere? I'm sure there is I just can't seem to find it. I already watched the videos and would like to not have to watch through a video to remind myself of a command that I forget.
-
View User Profile
-
Send Message
Posted Feb 20, 2012@spblat
i dont use them, they do plant sapplings and remove treetops but i dont "see" it enough to go "oh yeah thats how it works" plus they seem to mess with my friends obsession for giant custom trees... lol