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 20, 2014Now i just wonder, how many dev builds do i have to step back, to get rid of the error [00:05:03 INFO]: [GriefPrevention] Unable to save data for player Fungreenfox. Details: [00:05:03 WARN]: com.mysql.jdbc.exceptions.jdbc4.MySQLSyntaxErrorException: You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near ''name','lastlogin','accruedblocks','bonusblocks','clearonjoin') VALUES ('Fungre' at line 1
-
View User Profile
-
Send Message
Posted Feb 20, 2014@pr4xt3roy
/giveclaim requires owners right the property. So he/she can only give own claim away.
/transferclaim is an admin tool, can transfer any claim.
-
View User Profile
-
Send Message
Posted Feb 20, 2014This is weird, it seems to block only 1 thing from everyone including me with all permissions, whenever I post my own website it is blocked for "spam" yet I can post ANY other site.
-
View User Profile
-
Send Message
Posted Feb 20, 2014Quick question...
If an admin can transfer anyone's claim using /giveclaim, then what is the purpose of /transferclaim ?
the way I understand it, /giveclaim would be for users and /trsnsferclaim for admins... but they seem to do exacly the same no?
The only difference I see is that using /transferclaim without any parameter will transfer a claim into an admin claim. But /giveclaim could do that too (when you have proper permissino) and you would have one less command to worry about.
No?
-
View User Profile
-
Send Message
Posted Feb 20, 2014Despite what is set in the config, players on my server are still able to PvP inside any GriefPrevention claims. Things like breaking blocks and even potion splash is still protected against in the claim, however. If a WorldGuard region is set to no pvp, they can't PvP there, so I'm fairly certain it has to do with the plugin... has anyone else had this issue, or is there something I'm not setting up correctly?
-
View User Profile
-
Send Message
Posted Feb 20, 2014Does this work with votecatcher
-
View User Profile
-
Send Message
Posted Feb 19, 2014OK there are a few things unclear to me:
1. What is entity cleanup task?
2. If I set "AllClaimDays: 40" and disable ClaimCleanup like so: ClaimCleanup: Interval: 300 Quantity: 5 MaximumSize: 25 MaxInvestmentScore: 100 Enabled: false Will claims still get removed after 40 days of inactivity?
3. If a player creates his first claim with a chest and than resizes it. Will this claim still be considered as chestclaim (that gets removed after 7 days) or not?
4. How exactly does this claim removing work? I just want to know about allclaimdays function. When does it check if claims are not used over 40 days? Because I do sometimes find claims that belong to player who didn't play for more than 40 days.
5. Does a player have to build anything on a claim so it doesn't get automatically removed or is it enough for him to just log on the server?
6. What if a claim belongs to player A and player B has a trust to build on it. Will the claim get removed if player A doesn't log on in 40 days even if player B is building things on player A's claim?
I am currently using b213 and there are so many random bugs and claims that should be automatically unclaimed. I am also setting things up for a new server and am trying to use b277. Should I start with this build or can I expect problems in long term? This plugin was awesome till 7.8. Now there are just so many bugs an I have a really hard time using it. Please devote some more time fixing bugs. And ty for all the work you do :D
-
View User Profile
-
Send Message
Posted Feb 19, 2014Latest version 277 started spewing mysql syntax errors ocasionally. http://pastebin.com/2HZ8Zipy
-
View User Profile
-
Send Message
Posted Feb 18, 2014Hello I have for 4 Server with bungeecord, i have installed griefprevention on one Server, but it the Permission won't work. I have griefprevention.* with Owner, but the player have griefprevention.claims and griefprevention.buysellclaimblocks. But the player cant do anything with these permissions. I will be happy if you can answer! I have skype: marv5games
-
View User Profile
-
Send Message
Posted Feb 18, 2014It would be cool if there was an option to turn off the setting so it protects all blocks vertically. So you would click the 2 corners kinda like world edit to make your claim. Therefore the blocks per hour earned would go literally per block not by every vertical column.
-
View User Profile
-
Send Message
Posted Feb 18, 2014Also it seems to throw errors when people use minecarts to ride?
[22:34:05 ERROR]: Could not pass event PlayerInteractEntityEvent to GriefPrevention v7.8 org.bukkit.event.EventException at org.bukkit.plugin.java.JavaPluginLoader$1.execute(JavaPluginLoader.java:320) [craftbukkit-1.7.2-R0.3.jar:git-Bukkit-1.7.2-R0.3-b3020jnks] at org.bukkit.plugin.RegisteredListener.callEvent(RegisteredListener.java:62) [craftbukkit-1.7.2-R0.3.jar:git-Bukkit-1.7.2-R0.3-b3020jnks] at org.bukkit.plugin.SimplePluginManager.fireEvent(SimplePluginManager.java:486) [craftbukkit-1.7.2-R0.3.jar:git-Bukkit-1.7.2-R0.3-b3020jnks] at org.bukkit.plugin.SimplePluginManager.callEvent(SimplePluginManager.java:471) [craftbukkit-1.7.2-R0.3.jar:git-Bukkit-1.7.2-R0.3-b3020jnks] at net.minecraft.server.v1_7_R1.PlayerConnection.a(PlayerConnection.java:1068) [craftbukkit-1.7.2-R0.3.jar:git-Bukkit-1.7.2-R0.3-b3020jnks] at net.minecraft.server.v1_7_R1.PacketPlayInUseEntity.a(SourceFile:55) [craftbukkit-1.7.2-R0.3.jar:git-Bukkit-1.7.2-R0.3-b3020jnks] at net.minecraft.server.v1_7_R1.PacketPlayInUseEntity.handle(SourceFile:10) [craftbukkit-1.7.2-R0.3.jar:git-Bukkit-1.7.2-R0.3-b3020jnks] at net.minecraft.server.v1_7_R1.NetworkManager.a(NetworkManager.java:146) [craftbukkit-1.7.2-R0.3.jar:git-Bukkit-1.7.2-R0.3-b3020jnks] at net.minecraft.server.v1_7_R1.ServerConnection.c(SourceFile:134) [craftbukkit-1.7.2-R0.3.jar:git-Bukkit-1.7.2-R0.3-b3020jnks] at net.minecraft.server.v1_7_R1.MinecraftServer.u(MinecraftServer.java:655) [craftbukkit-1.7.2-R0.3.jar:git-Bukkit-1.7.2-R0.3-b3020jnks] at net.minecraft.server.v1_7_R1.DedicatedServer.u(DedicatedServer.java:250) [craftbukkit-1.7.2-R0.3.jar:git-Bukkit-1.7.2-R0.3-b3020jnks] at net.minecraft.server.v1_7_R1.MinecraftServer.t(MinecraftServer.java:545) [craftbukkit-1.7.2-R0.3.jar:git-Bukkit-1.7.2-R0.3-b3020jnks] at net.minecraft.server.v1_7_R1.MinecraftServer.run(MinecraftServer.java:457) [craftbukkit-1.7.2-R0.3.jar:git-Bukkit-1.7.2-R0.3-b3020jnks] at net.minecraft.server.v1_7_R1.ThreadServerApplication.run(SourceFile:617) [craftbukkit-1.7.2-R0.3.jar:git-Bukkit-1.7.2-R0.3-b3020jnks] Caused by: java.lang.NullPointerException at me.ryanhamshire.GriefPrevention.PlayerEventHandler.onPlayerInteractEntity(PlayerEventHandler.java:2255) [?:?] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) [?:1.7.0_51] at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) [?:1.7.0_51] at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) [?:1.7.0_51] at java.lang.reflect.Method.invoke(Method.java:606) [?:1.7.0_51] at org.bukkit.plugin.java.JavaPluginLoader$1.execute(JavaPluginLoader.java:318) [craftbukkit-1.7.2-R0.3.jar:git-Bukkit-1.7.2-R0.3-b3020
-
View User Profile
-
Send Message
Posted Feb 18, 2014How come dev build 177 let user claim using minecarts?...
-
View User Profile
-
Send Message
Posted Feb 18, 2014I wanted to try this, but the integration for other protection plugins (Townships/Factions/Towny/etc) don't seem to be there.
-
View User Profile
-
Send Message
Posted Feb 18, 2014@CraftThatBlock
Flags does this and its already in the list.
-
View User Profile
-
Send Message
Posted Feb 18, 2014Mind adding http://dev.bukkit.org/bukkit-plugins/ctb-gpmessages/ to the extensions list? Thanks.
-
View User Profile
-
Send Message
Posted Feb 17, 2014@GodsDead
It does. I just had the same issue. What you need to do (as per the Essentials documentation) is add an alias to bukkit.yml (if on 1.6) or commands.yml (if on 1.7) mapping /ignore to /eignore. This will make Essentials overwrite GriefPrevention's /ignore. There is documentation for bukkit.yml/command.yml aliases on the Bukkit wiki.
-
View User Profile
-
Send Message
Posted Feb 17, 2014Hi Guys I am having a lot of issues with this mod.
First off I really love the idea and I especially like the in-game help for players. This is EXACTLY what I am looking for, the ability for players to make claims. The visual claims guide is GOLD. Seriously it is a game changer for plugins.
However, I am having some extreme issues marrying this mod with my current server - essentials + worldguard + supercensor. My main world has global region defined and then survival zones inside global were users can place blocks. Ive been having to do some tricks to get this functionality all working, and when I think its good things break.
Essentials + worldguard is a basic setup everyone uses for their servers. I still want to define regions with worldguard not just administrative claims (unless you can claim the world)
I just wish the devs of this project would spend less time on added features and do just a little cleanup to make my life easy like:
1. A real permissions node table like the essentials plugin page has. 2. No-brainer opt-out permission nodes i can use for groups like the chat/spam/login cooldowns I dont want this functionality and I dont want to add a whole bunch of nodes to my file. 3. above and below lava/water placement is another issue of hassle for me. I want easy method to opt out of this for users, but still have their claims protected.
Basically, I already have worldguard + essentials working great on my server, and just want to have users make simple vault enabled claims in areas I have already designated. How can I do this without a whole bunch of configuring??
My 2cents here is this mod is trying to replace all other grief preventions.. and it just can't. it does well what it does, but please leave some hooks into existing systems for us admins that like the functionality of other mods as well. :) thanks!
-
View User Profile
-
Send Message
Posted Feb 17, 2014Does grief prevention have an /ignore command? Because im finding it hard to track down what is overwriting essentials ignore permission, If so what is the permission for it?
-
View User Profile
-
Send Message
Posted Feb 17, 2014I'm using 7.8-beta-b213 and I'm having trouble with the pvp protection in admin claims.
ProtectPlayersInLandClaims: PlayerOwnedClaims: false AdministrativeClaims: true
I set administrativeclaims to true and restart the server and it works. The next server restart, it turns back to false.
Anyone have a clue why it is doing this?
-
View User Profile
-
Send Message
Posted Feb 17, 2014Is 7.8 backwards compatible with 7.7? I'm wanting to go back, as 7.8 isn't providing the features I need that 7.7 did. A lot of mod blocks aren't being protected, despite trying to put in the right RegEx options. Subclaims are also disappearing etc.
@JoeLinder
I'd recommend just using 7.7. 7.8's got so many issues right now, especially for modded servers. Development seems to be slow too, so issues are taking a while to get a response.