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 19, 2015@bigscary
Its just new sub-claims that do not get saved after a reboot. As for the invincible players stuck in defenceless, I think it may be something to do with logging in and out, I asked a few players if they knew how it was done and this is the only thing they observed from the player that was doing it, Sadly he wont tell me how hes exploiting this, so its got to be reproducible.
edit: getting another bug, A player was complaining they couldn't resize a claim as it was just spazzing out making the claim random sizes, it was, he showed me, he set a claim, went to resize it tried to make a new claim corner, and the original claim was resized to roughly half the size. I tried it and it did the same thing, I then got him to destroy it and re-make it, this seemed to set, then it all of a sudden by itself changed size! it was like half the claim just got shrunk.
-
View User Profile
-
Send Message
Posted Feb 18, 2015Hi, I've watched the admin guides with great interest. This looks to be wonderful. However, before I change over my servers, I need to know... can this handle bungeecord linked spigot servers? Can it fetch the UUIDs from Mojang across offline servers? Because I'm already finding that worldguard is having issues there (cannot add users to regions unless they are actually in game at the time). No doubt this will not be an issue, as players will ofc be in game when they claim land. But I still need to know; does this handle the growing community of spigot/bungeecord servers? I really think all plugins need to consider working with this aspect if they can, or it could be the death of server networks. Thanks for this plugin, btw. I would happily pay for it if it works well, and you felt you should be reimbursed. But your voluntary efforts are greatly appreciated, I'm sure! Ahh hang on just read your details about offline players in the update logs. Yes, you are right, performance is vital. You would be compromising that if changes were made to work with offline spigot servers, perhaps. So long as players are able to do what they normally should in an offline server, I'll be content. I guess I'll have to test it to find out. If anyone out there has my sort of server setup and has tried this plugin, can you let me know the results? Thanks in advance.
-
View User Profile
-
Send Message
Posted Feb 18, 2015@markdf
Use /claimexplosions. The plugin tells you about this command when you place TNT in your land claim.
@P0WeRZz
Create an administrative claim with /adminclaims, then give it to the player with /transferclaim. This is described in the "creating claims for others" section of the how-to guide linked above.
@GodsDead
Only new subclaims, or all subclaims are lost?
I'll do my best to figure out the cause of your "players are always invincible" issue. Just have to figure out how to reproduce it first...
I think I fixed that economy issue in the latest version.
About the permission, will-do.
-
View User Profile
-
Send Message
Posted Feb 18, 2015Can there be a command to claim for someone else? My server is not really big so I'd like to help players as much as i can. Unfortunately, there is no good dutch tutorial available so i need to do everyone myself. Some people just dont get it.
I'd like to just ./nowiclaimfor [player] And just make their claim. (Ofcourse that command is just an example ;) )
-
View User Profile
-
Send Message
Posted Feb 18, 2015Few issues that exist:
Request:
-
View User Profile
-
Send Message
Posted Feb 18, 2015I cant see an option, but is it possible for an owner to be able to use tnt within their own claimed areas? Some players like to use tnt to excavate.
-
View User Profile
-
Send Message
Posted Feb 17, 2015@maclarenss
Try updating vault and your economy plugins. If that doesn't fix it, start by asking your economy plugin author about that.
@Phreag
Please pastebin your complete boot logs. :)
@switorik
Are you on the latest version? I think I recently changed this to allow zombies to do damage to villagers in land claims.
@The_PC_Tech_Guy
That's possible, but I don't want to do it. That's exactly what the laziest spammers do - copy/paste the same message again and again. I don't want several lines of spam to go out before it gets filtered. The new tolerance is to allow a repeat message as long as it's at least 10 seconds after the last time it was sent. Should be good for most cases I think, when you consider typing time involved in the usual conversation. It can be tweaked more, just let me know if you actually still see a problem after this. :)
-
View User Profile
-
Send Message
Posted Feb 17, 201510.7.1 Updates
Please take a few moments to vote for Grief Prevention! :) We're only 35 total 5-star reviews away from being the top plugin on the spigot site, which is absolutely a reachable goal. Thanks for your support! http://www.spigotmc.org/resources/griefprevention.1884/
-
View User Profile
-
Send Message
Posted Feb 17, 2015@bigscary
Thanks for the fast response, I have another suggestion related to it - is it possible you can allow a repeated phrase to go through two or three times (preferably configurable) before it's muted? Some players say "lol" about 2 or 3 times in response to another player, for example.
-
View User Profile
-
Send Message
Posted Feb 17, 2015I'm having an issue where zombies can not attack villagers in claims. I don't know if this is a bug or a desired effect.
I have tested this by summoning a zombie/villager in a claimed area and in a non claimed area. Both try to attack the villager, only the non claimed area can hurt the villager.
-
View User Profile
-
Send Message
Posted Feb 17, 2015On my Server startup it takes a long long time loading Griefprevention:
[20:16:10 INFO]: [GriefPrevention] Enabling GriefPrevention v10.6.3 [20:16:10 INFO]: GriefPrevention: Grief Prevention boot start. [20:16:10 INFO]: GriefPrevention: Finished loading configuration. [20:16:10 INFO]: GriefPrevention: 2620 total claims loaded. [20:16:11 INFO]: GriefPrevention: Customizable messages loaded. [20:16:11 INFO]: GriefPrevention: Successfully hooked into WorldGuard. [20:16:11 INFO]: GriefPrevention: Finished loading data (Database Mode). - - > Now it takes about 7 Minutes to continue booting.
Whats the Reason? Hardware: Core i7 4790K, 32GB DDR3, SSD
Thx :)
-
View User Profile
-
Send Message
Posted Feb 17, 2015griefprev not working with FE economy when i sell/buy blocks
[21:10:16] [Server thread/ERROR]: null org.bukkit.command.CommandException: Unhandled exception executing command 'sellclaimblocks' in plugin GriefPrevention v10.7 at org.bukkit.command.PluginCommand.execute(PluginCommand.java:46) [spigot-1.8-R0.1-SNAPSHOT-latest.jar:git-Spigot-b73910a-726656b] at org.bukkit.command.SimpleCommandMap.dispatch(SimpleCommandMap.java:141) [spigot-1.8-R0.1-SNAPSHOT-latest.jar:git-Spigot-b73910a-726656b] at org.bukkit.craftbukkit.v1_8_R1.CraftServer.dispatchCommand(CraftServer.java:646) [spigot-1.8-R0.1-SNAPSHOT-latest.jar:git-Spigot-b73910a-726656b] at net.minecraft.server.v1_8_R1.PlayerConnection.handleCommand(PlayerConnection.java:1115) [spigot-1.8-R0.1-SNAPSHOT-latest.jar:git-Spigot-b73910a-726656b] at net.minecraft.server.v1_8_R1.PlayerConnection.a(PlayerConnection.java:950) [spigot-1.8-R0.1-SNAPSHOT-latest.jar:git-Spigot-b73910a-726656b] at net.minecraft.server.v1_8_R1.PacketPlayInChat.a(PacketPlayInChat.java:26) [spigot-1.8-R0.1-SNAPSHOT-latest.jar:git-Spigot-b73910a-726656b] at net.minecraft.server.v1_8_R1.PacketPlayInChat.a(PacketPlayInChat.java:53) [spigot-1.8-R0.1-SNAPSHOT-latest.jar:git-Spigot-b73910a-726656b] at net.minecraft.server.v1_8_R1.PacketHandleTask.run(SourceFile:13) [spigot-1.8-R0.1-SNAPSHOT-latest.jar:git-Spigot-b73910a-726656b] at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) [?:1.8.0_25] at java.util.concurrent.FutureTask.run(FutureTask.java:266) [?:1.8.0_25] at net.minecraft.server.v1_8_R1.MinecraftServer.z(MinecraftServer.java:696) [spigot-1.8-R0.1-SNAPSHOT-latest.jar:git-Spigot-b73910a-726656b] at net.minecraft.server.v1_8_R1.DedicatedServer.z(DedicatedServer.java:316) [spigot-1.8-R0.1-SNAPSHOT-latest.jar:git-Spigot-b73910a-726656b] at net.minecraft.server.v1_8_R1.MinecraftServer.y(MinecraftServer.java:634) [spigot-1.8-R0.1-SNAPSHOT-latest.jar:git-Spigot-b73910a-726656b] at net.minecraft.server.v1_8_R1.MinecraftServer.run(MinecraftServer.java:537) [spigot-1.8-R0.1-SNAPSHOT-latest.jar:git-Spigot-b73910a-726656b] at java.lang.Thread.run(Thread.java:745) [?:1.8.0_25] Caused by: java.lang.AbstractMethodError: org.melonbrew.fe.Economy_Fe.depositPlayer(Lorg/bukkit/OfflinePlayer;D)Lnet/milkbowl/vault/economy/EconomyResponse; at me.ryanhamshire.GriefPrevention.GriefPrevention.onCommand(GriefPrevention.java:1417) [?:?] at org.bukkit.command.PluginCommand.execute(PluginCommand.java:44) [spigot-1.8-R0.1-SNAPSHOT-latest.jar:git-Spigot-b73910a-726656b] ... 14 more
-
View User Profile
-
Send Message
Posted Feb 16, 2015@Konsider
They only get added when players aren't standing around doing nothing. Maybe your players are complaining but don't realize they have to move around and do stuff?
@zedadiaswick
I'll add that command you suggested.
You can already trust permission groups for all levels except for /permissiontrust.
@jenks1999
Hm okay first, that stack trace starts with the /acb command, has nothing to do with right clicking. Second, that's a super odd error, I think maybe rebooting your server or possibly just reloading will fix it.
@GodsDead
Will address the selling blocks issue. Players should not be able to sell their initial blocks.
@The_PC_Tech_Guy
Sure thing.
@raum
Please explain "wither cage exploiting"? Allowing wither damage to claims would give a griefer a great tool - spawn a wither near someone else's house, then run around and let it destroy everything. Thoughts on a way to balance these goals?
EDIT: If you're talking about one of the wither skulls not being destroyed as it should, that's a server bug that the Spigot/CraftBukkit guys haven't fixed yet. It's not a bug in the GriefPrevention code.
@delsolsi213
Yep, use the 1.7.10 version linked above.
@IamMadKitty
If your players are in creative mode, you want that - otherwise griefing disaster. If they're not, see the setup/config page. You'll need to update your config file to indicate that world is a survival world instead of a creative world.
-
View User Profile
-
Send Message
Posted Feb 16, 2015Hey, I'm having a problem with players having to create their claim before building anywhere.. How can I fix that?
-
View User Profile
-
Send Message
Posted Feb 15, 2015is there any 1.7.10 compatible versions that work with name changing?
-
View User Profile
-
Send Message
Posted Feb 15, 2015Wither explosions are not damaging claims, and the options to allow this seem to no longer be in the config - was this bundled with something else? "BlockSurfaceCreeperExplosions" and "BlockSurfaceOtherExplosions" doesn't effect it at all.
The amount of wither cage exploiting due to claim blocks being protected is ridiculous.
To Clarify: I'm aware that withers can't be created inside a claim - However it's not difficult to place the last head, and quickly claim the cage before it's done spawning.
-
View User Profile
-
Send Message
Posted Feb 14, 2015Is it possible you can add a time limit regarding repeating a word or phrase? One person was responding to me saying "okay," and I saw in the console that he was muted at one point - perhaps add a (configurable) reset of 1-2 minutes.
-
View User Profile
-
Send Message
Posted Feb 14, 2015@bigscary
The claim-count issue seems to have fixed the players that were having problems, These players were on -20,000 claim blocks, but after I updated to 10.7 They were back at 0 without me changing anything.
Today I found a game-breaking issue, Luckily the player told me, that he has infinite claims, it seems to be locked to him alone, The player is able to sell his 1400 claims, log out and log in again and he still had the 1400, to repeat the process. This is extremely dangerous and can be easily exploited, I hope that it is just this one player, and I have no idea why its happened. Edit: if any player sells all thier claims exactly and relog they get some back for free when they rejoin - game breaking.
-
View User Profile
-
Send Message
Posted Feb 14, 2015Players are not gaining blocks over time in SQL mode and i cant give players extra blocks.
I assume i missed something here.
Also this plugin seems to conflict with mcmmo. it keeps converting back to skills when right clicking the floor for region adjustment.
[10:28:04 ERROR]: null org.bukkit.command.CommandException: Unhandled exception executing command 'acb' in plugin GriefPrevention v10.6.2 at org.bukkit.command.PluginCommand.execute(PluginCommand.java:46) [spigot_server.jar:git-Spigot-b1e6da1-17962f6] at org.bukkit.command.SimpleCommandMap.dispatch(SimpleCommandMap.java:141) [spigot_server.jar:git-Spigot-b1e6da1-17962f6] at org.bukkit.craftbukkit.v1_8_R1.CraftServer.dispatchCommand(CraftServer.java:645) [spigot_server.jar:git-Spigot-b1e6da1-17962f6] at net.minecraft.server.v1_8_R1.PlayerConnection.handleCommand(PlayerConnection.java:1115) [spigot_server.jar:git-Spigot-b1e6da1-17962f6] at net.minecraft.server.v1_8_R1.PlayerConnection.a(PlayerConnection.java:950) [spigot_server.jar:git-Spigot-b1e6da1-17962f6] at net.minecraft.server.v1_8_R1.PacketPlayInChat.a(PacketPlayInChat.java:26) [spigot_server.jar:git-Spigot-b1e6da1-17962f6] at net.minecraft.server.v1_8_R1.PacketPlayInChat.a(PacketPlayInChat.java:53) [spigot_server.jar:git-Spigot-b1e6da1-17962f6] at net.minecraft.server.v1_8_R1.PacketHandleTask.run(SourceFile:13) [spigot_server.jar:git-Spigot-b1e6da1-17962f6] at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471) [?:1.7.0_25] at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334) [?:1.7.0_25] at java.util.concurrent.FutureTask.run(FutureTask.java:166) [?:1.7.0_25] at net.minecraft.server.v1_8_R1.MinecraftServer.z(MinecraftServer.java:683) [spigot_server.jar:git-Spigot-b1e6da1-17962f6] at net.minecraft.server.v1_8_R1.DedicatedServer.z(DedicatedServer.java:316) [spigot_server.jar:git-Spigot-b1e6da1-17962f6] at net.minecraft.server.v1_8_R1.MinecraftServer.y(MinecraftServer.java:623) [spigot_server.jar:git-Spigot-b1e6da1-17962f6] at net.minecraft.server.v1_8_R1.MinecraftServer.run(MinecraftServer.java:526) [spigot_server.jar:git-Spigot-b1e6da1-17962f6] at java.lang.Thread.run(Thread.java:724) [?:1.7.0_25] Caused by: java.lang.NoClassDefFoundError: me/ryanhamshire/GriefPrevention/DataStore$SavePlayerDataThread at me.ryanhamshire.GriefPrevention.DataStore.savePlayerData(DataStore.java:752) [?:?] at me.ryanhamshire.GriefPrevention.GriefPrevention.onCommand(GriefPrevention.java:1702) [?:?] at org.bukkit.command.PluginCommand.execute(PluginCommand.java:44) [spigot_server.jar:git-Spigot-b1e6da1-17962f6] ... 15 more
-
View User Profile
-
Send Message
Posted Feb 14, 2015@bigscary
Ah, that is a shame to hear about managers and subdivisions.
I may not have been clear, my request was more along the lines of "please bring back /adjustaccruedclaimblocks". I knew the config would be reloaded, just didn't realise it would alter anyone's total. My fault for not testing that. I really appreciated being able to edit players accrued claim block value, please may we have that back?
I have a further request: Could you add in support for trusting permissions groups to have build/access/container trust? I'd like to allow players to have public areas, but limited to players who have played for at-least 15 hours to avoid drive-by griefing.