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 Jan 19, 2014Is there a way to perhaps add an option in the config to "protect end portals"? I'm tired of seeing people claiming them and ruining the fun for everyone.
-
View User Profile
-
Send Message
Posted Jan 19, 2014@anfereon
This could potentially solve the problem, however, part of the game experience is to be able to get the stuff required to FIND the end, not have one given to you. If everything was given to you, this game wouldn't be fun.
-
View User Profile
-
Send Message
Posted Jan 19, 2014@GodsDead
Admin perms dont work, at all. Adding all the admin perms to a users group dousnt do anything, they have to be OP to use the admin claim blocks.
Admin perms work fine. There is only one place in the entire codebase where Players are checked to see if they are Op and those are unrelated and deal with notification of automatic bans.
Interestingly, all the admin perms you say do not work default to set for all ops.
EDIT: also, you can add Dragon Eggs to the BlockPlaceOverrides and prevent them from being placed.
-
View User Profile
-
Send Message
Posted Jan 19, 2014No option to disable Dragon Spawn Eggs in Worlds. As a saftey feature, just in case some dragon eggs were spawned I would love to be able to make it so they cannot be "laid" . Admin perms dont work, at all. Adding all the admin perms to a users group dousnt do anything, they have to be OP to use the admin claim blocks.
-
View User Profile
-
Send Message
Posted Jan 19, 2014@Maximvdw
This (the playerdata stuff) has nothing to do with the database or the database implementation and only occurs with the file storage implementation.
In fact, the migration from flat to database has been disabled somewhat for that reason, in that it now requires a setting (GriefPrevention.AllowAutomaticMigration) to be set before it will do so.
@digimbyte
you can use /ignoreclaims. This should allow you to resize and make changes to claims owned by other players.
-
View User Profile
-
Send Message
Posted Jan 19, 2014Love this plugin, always swear by it. but recently started a server thats quiet busy and i've realized being an admin that sometimes i need to override or edit another persons claim
However I cant seem to find it as '/ac' despite saying its resizing, wants to create a new admin claim so its not multi-functional as I thought. is there a way for admins and moderators to adjust a persons claim as needed to help those new players out when they fail?
I have only one limitation and that if an update is needed, it needs to be 1.5.2 compatible since the server runs 3rd party extensions.
Thanks in advance
-
View User Profile
-
Send Message
Posted Jan 19, 2014@BC_Programming
Think this is the same as my mysql data wipe? I discovered btw when I first started the new plugin it had no mysql settings in the new generated config, and GP started saving in the flatfile. When I joined after starting the server, I saved my 'new user' claims to the flatfile.
Then I edited the config to support mysql, and restarted the server.
The plugin started to migrate the flatfile to mysql deleting all other data.
The problem did not occur when I:
-
View User Profile
-
Send Message
Posted Jan 19, 2014I'm unable to get the problem to occur no matter what I do. I Did make some recent changes to the flat data store to address the player's claims not being added to their data after a gpreload, but they neither disappear when I /gpreload nor do the bonus blocks I've given myself over time.
My best guess is that it is only a problem on *nix due to changes to filename casing. I'll try running the server in a Linux VM.
EDIT: OK first run went fine. I copied the same server to a Linux VM and everything was intact.
However, while the player data folder had lowercased names for the two accounts I test with, I found on Linux the plugin also saved uppercase names when shut down, which is the opposite of what is intended- so on Linux it was saving uppercase but preferring lowercase. Previously the lower-cased filenames were actually stubs created by another bug. (meaning they had default data, eg. 100 claim blocks).
This is build #257 now.
I deleted the upper-cased names from the PlayerData and revised the appropriate code and tested again.
It did not reset and all the data was saved properly. In fact in the process of testing I stayed on the server for 10 minutes- so both the accounts also received extra claim blocks in the process.
This was related to a previous attempt to fix a reported *nix issue whereby the playerData would have a cased name (eg BC_Programming) as well as a lowercased name (bc_programming). Unfortunately the one piece of that fix I missed was making sure all data got saved to lowercased filenames.
I'm not sure what effect this may have, for systems with already messed-up settings. If you have a backup of PlayerData from before the issues started to occur, you should be able to use those.
-
View User Profile
-
Send Message
Posted Jan 19, 2014@BC_Programming To clarify a bit on what I've done...we've been running 7.7 for quite a while. However back at the start of January due to storage issues and data from all different versions of Grief Prevention ranging back 3 years or so when it first came out on BigScary's server (I inherited his test server) we decided to do a complete server wipe and start over. Thus when I set up the server, we had no previous files from 7.7. Just a fresh 7.8. The problem though is they've been playing with 7.8 since the start of January and many claims and builds have gone up. Now with this bug, a little more than half of a months work and claim-blocks gain has been for nothing. 19 days, 200 players, all their hours logged to get claim blocks simply gone. Erased when I updated to a newer build that was listed as both successful and stable in hopes of bug fixes.
If you could be so kind as to let me know just what sort of information you need from this server in order to better help sort this out and hopefully solve this horrid bug I'd be more than willing to do what I can. I know nothing of coding or anything of the sort but I'll try.
I realize a lot of people seem upset with the direction the plugin is going and I'm liking to think it's just cause it's in a migration period. A hectic mess at the moment with so many changes going on. It's true that the plugin WAS simpler when BigScary managed it but it's also true that we have LOTS more customization options available to use. This has been my favorite plugin in all of minecraft when combined with Population Density and honestly...I just want to see it working and in a clear and precise manner that's both easy to customize and update without worry or fear of something getting messed up.
@anfereon
Same problem =/
@TJW28
The same happened with me. At first everyone was negative, their claims no longer showing up via /claimslist. However when I checked the ClaimData folder they still existed. Even in game when I check for them by right clicking with a stick, they're all still there and protect like normal. They just don't show up.
Furthermore I've noticed upon a server restart or /reload? No matter how long someones been online, their claim blocks reset to the default, 100 starting blocks. This even applies to myself when I award myself claim blocks as a test. What I did was aware myself 300,000 blocks, make a claim, use /reload, checked and the claim was still there. However I was now back at 100. Another odd feature I noticed, I tried the same thing with one of my mods claims sorta. I awarded myself 300,000 blocks, ignored claims and went to go adjust their claim by 1 block. Upon doing so they went from the default 100 to far into the negatives. Was a large claim so they were now -4000 or so. Again however upon /reload they went back to 100 and their claim remained re-sized.
-
View User Profile
-
Send Message
Posted Jan 19, 2014I'm still seeing messages in the console on start-up about GP unable to load claimdata for players, Also, and more importantly, Lots of players now have negative claimblocks and some even report some claims no longer there. I dont see errors in the logs,
Im using the latest Build #256, but this seems to have started a few builds back.
Is this just happening to me, or anyone else seeing similar?
Thanks
-
View User Profile
-
Send Message
Posted Jan 19, 2014OK so I updated to #253 and now, sometimes when players change claims (I don't know what they have to do exactly) their remaining claimblocks get set to - something. This - is differnet from player to player. I don't really have time to test this right now. Could you just make this plugin work.
-
View User Profile
-
Send Message
Posted Jan 19, 2014Can you please elaborate on how to use the
WorldConfig: SingleWorld: <None> TemplateFile: plugins/GriefPrevention/WorldConfigs/_template.cfg
config option? ive looked all over these pages and have found nothing on it.
-
View User Profile
-
Send Message
Posted Jan 19, 2014I'm sorry if this has already been mentioned, but I'm running GriefPrevention v7.8, and Minecraft 1.7.2. My "Moderators" have the griefprevention.ignoreclaims, and also the griefprevention.claims.ignore claim, but it's not allowing them to ignore the claims, stating:
"I'm sorry, but you do not have the permission to perform this command. Please contact the server administrators if you believe that this is in error."
Thanks for your help!
-
View User Profile
-
Send Message
Posted Jan 18, 2014@smc87
Do you have a more complete stack trace?
@LEOcab
Yeah about that. There's no upgrade guide to upgrade from the 7.6 branch.
Delete old jar. Add new jar. run server.
I tried it in a test server and it created a whole new folder for the plugin, leaving all my previous claims & configuration files in the old version's folder.
It creates a new folder. claim and player data is copied over. The only thing not carried over is configs.
I don't want what happened to @Smac3223 to happen to me.
Their issue is unrelated to migrating from 7.7 and earlier.
If you find a dev or beta build of 7.8 does not work- or even manages to mess up the migration- all the previous data is still present in GriefPreventionData. As the main page explains over a few paragraphs, the data folder was changed and this allows 7.8 to "migrate" by detecting when an old folder for 7.7 and earlier exists but not one for 7.8, and simply copies the folder and carries on, which will copy flat data.
Is every update going to reset the claim blocks?
The claim blocks on my testing server's flat file data store have not ever reset themselves to my knowledge. You pose this question, as if it is intended. It's not. And without any actual information it is unactionable because I cannot see this behaviour- I still have a ridiculous number of claim blocks from when I gave myself something like a million last May.
-
View User Profile
-
Send Message
Posted Jan 18, 2014Something is definately wrong with players claimslist disapearing. They have claims, but it looks like they have none when /claimslist is used. I will report when i find out more about this.
-
View User Profile
-
Send Message
Posted Jan 18, 2014hello, can anyone help me with this.....i seen this alot in logs. running latest spigot and latest GP dev version. Wondering if its anything to do with entity-tracking range of players in spigot?
22:52:57] [Server thread/ERROR]: Could not pass event PlayerInteractEvent to GriefPrevention v7.8 org.bukkit.event.EventException at org.bukkit.plugin.java.JavaPluginLoader$1.execute(JavaPluginLoader.java:320) [2014-01-17-19-03-26-spigot.jar:git-Spigot-1245] at org.bukkit.plugin.RegisteredListener.callEvent(RegisteredListener.java:62) [2014-01-17-19-03-26-spigot.jar:git-Spigot-1245] at org.bukkit.plugin.TimedRegisteredListener.callEvent(TimedRegisteredListener.java:30) [2014-01-17-19-03-26-spigot.jar:git-Spigot-1245] at org.bukkit.plugin.SimplePluginManager.fireEvent(SimplePluginManager.java:482) [2014-01-17-19-03-26-spigot.jar:git-Spigot-1245] at org.bukkit.plugin.SimplePluginManager.callEvent(SimplePluginManager.java:467) [2014-01-17-19-03-26-spigot.jar:git-Spigot-1245] at org.bukkit.craftbukkit.v1_7_R1.event.CraftEventFactory.callPlayerInteractEvent(CraftEventFactory.java:208) [2014-01-17-19-03-26-spigot.jar:git-Spigot-1245] at org.bukkit.craftbukkit.v1_7_R1.event.CraftEventFactory.callPlayerInteractEvent(CraftEventFactory.java:178) [2014-01-17-19-03-26-spigot.jar:git-Spigot-1245] at net.minecraft.server.v1_7_R1.PlayerConnection.a(PlayerConnection.java:1011) [2014-01-17-19-03-26-spigot.jar:git-Spigot-1245] at net.minecraft.server.v1_7_R1.PacketPlayInArmAnimation.a(SourceFile:43) [2014-01-17-19-03-26-spigot.jar:git-Spigot-1245] at net.minecraft.server.v1_7_R1.PacketPlayInArmAnimation.handle(SourceFile:9) [2014-01-17-19-03-26-spigot.jar:git-Spigot-1245] at net.minecraft.server.v1_7_R1.NetworkManager.a(NetworkManager.java:147) [2014-01-17-19-03-26-spigot.jar:git-Spigot-1245] at net.minecraft.server.v1_7_R1.ServerConnection.c(SourceFile:134) [2014-01-17-19-03-26-spigot.jar:git-Spigot-1245] at net.minecraft.server.v1_7_R1.MinecraftServer.u(MinecraftServer.java:678) [2014-01-17-19-03-26-spigot.jar:git-Spigot-1245] at net.minecraft.server.v1_7_R1.DedicatedServer.u(DedicatedServer.java:273) [2014-01-17-19-03-26-spigot.jar:git-Spigot-1245] at net.minecraft.server.v1_7_R1.MinecraftServer.t(MinecraftServer.java:540) [2014-01-17-19-03-26-spigot.jar:git-Spigot-1245] at net.minecraft.server.v1_7_R1.MinecraftServer.run(MinecraftServer.java:446) [2014-01-17-19-03-26-spigot.jar:git-Spigot-1245] at net.minecraft.server.v1_7_R1.ThreadServerApplication.run(SourceFile:617) [2014-01-17-19-03-26-spigot.jar:git-Spigot-1245] Caused by: java.lang.NullPointerException
-
View User Profile
-
Send Message
Posted Jan 18, 2014Would it be possible to add the ability to purchase claim blocks with physical items such as obsidian or ingots?
-
View User Profile
-
Send Message
Posted Jan 18, 2014@Smac3223
Yeah about that. There's no upgrade guide to upgrade from the 7.6 branch. I tried it in a test server and it created a whole new folder for the plugin, leaving all my previous claims & configuration files in the old version's folder. I don't want what happened to @Smac3223 to happen to me. Could you please write a step-by-step upgrade guide? I really want to have the new version on my server but I don't want to wake up one morning and find my server in chaos because I forgot to convert one particular setting to the new format. Thank you!
-
View User Profile
-
Send Message
Posted Jan 18, 2014Updated to latest build...it simply replaced all my players claim blocks data back to 100.
This is a MAJOR issue for those who allow claim blocks for donations. Is every update going to reset the claim blocks? Am I going to have to edit by hand hundreds of entries to correct claim data?
Cause at the moment there are a ton of players on my server who's numbers are now in the negatives. And I have no idea how to fix this.
Edit:I've deleted the plugin entirely, reinstalled it but not before backing up the playerdata and claimdata. When the plugin was reinstalled I dumped those two back into the Grief Prevention Folder and restarted the server. In game? The claims exist. They're all there and still protect everything just fine. However they cannot be found via /claimslist. In addition when using /claimslist on a player it lists nothing. They're not in the negatives anymore but rather back at 100 with no claims listed. So they exist in the world, but not when I look them up in game.
-
View User Profile
-
Send Message
Posted Jan 18, 2014@omgitsmit
Just build a public portal and destroy the others.