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 Sep 28, 2014What is the permission to let people use /claimslist on other people so:
/claimslist <name> Whats the permission for that?
-
View User Profile
-
Send Message
Posted Sep 28, 2014Hey BigScary! Not sure if this is related to the update but here is the log you requested when I use the /accesstrust public command. Pastebin
-
View User Profile
-
Send Message
Posted Sep 28, 2014I want to localization this plugin in korean but
it does not allow unicode, can you change them?
sorry for my bad english : (
-
View User Profile
-
Send Message
Posted Sep 28, 2014Is there a way to allow creeper explosions in cliams? I already have "creeperheal" so I would love that the players would get an extra challenge.
-
View User Profile
-
Send Message
Posted Sep 27, 20148.1.4 Updates
-
View User Profile
-
Send Message
Posted Sep 27, 2014@Willcomputerguy799
I need your upgrade logs at the very least. Can you use your backup to restore your data to what it was before your upgraded, then reboot to get those logs for me?
@Feeriix
It's strange that is all the detail you have. In 8.1.4, I made that logging more detailed. Please try again with that new version and share the more detailed log output.
@Mizar6
Fixed in 8.1.4. Thanks very much for the investigation work - you definitely saved me time. :)
@frostlord22
Thanks for bringing this to my attention - I don't have enough players on my test server yet to notice this kind of thing myself. I made some adjustments in 8.1.4, but I don't expect you'll get much out of it. It's possible I could do some multithreading to make this not faster, but at least not cause any lag - but it's looking like it will be a big mess (meaning very likely to cause bugs in this very important area of the plugin). The trouble comes from having to search through the list of players who've visited your server since it opened, which can be a long list. For now, I'm going to postpone this to see if maybe the Sponge API will provide a more efficient approach so that I won't have to take risks here. If I get impatient, I'll reconsider a fix for Bukkit. I'm not sure where the sudden difference in performance as you experience is coming from - possibly from recent Bukkit changes to optimize searches on UUID instead of searches by player name - since everyone's running a Beta or Dev version of Bukkit right now, I think that's a likely cause (lack of further streamlining, which would have been done for a "recommended" build).
-
View User Profile
-
Send Message
Posted Sep 27, 2014The latest verions seems to be extremely laggy, that's way diffrent to what the plugin used to be; efficient.
4.2ghz OC'ed machine. Some examples: 753.23% 2.26 s 376.61 ms 0.0 0.0k Command: containertrust 0.39% 197.49% 11.06 s 98.75 ms 0.0 0.1k BlockEventHandler::onTreeGrow(StructureGrowEvent)
When the user doesn't exsists it could get as high as 1second. Same with trust untrust unclaimall ect ect..
-
View User Profile
-
Send Message
Posted Sep 27, 2014I think /trust public is broken in the 8.1.2 version. I upgraded from 7.8 and no one could build in the world guard plots which I put an admin claim around with trust public. I deleted the GP admin clam and people can build.
I created the admin claim again and then did /trust public and once again no one can build. I using PermissionsBukkit, and everything worked fine until I upgraded.
I tested older versions and the problem exists in 8.1.0 through 8.1.3. The problem does not exist in version 8.0.3.
Forgot to mention that what gets downloaded for 8.1.3 says it is 8.1.2 on sever boot.
I can read a bit of java code and this change seems to be part of the problematic change, maybe the rest of this null key for public didn't get finished?
- //also everyone is a member of the "public", so check for public permission
- ClaimPermission permissionLevel = this.playerNameToClaimPermissionMap.get("public");
+ //also everyone is a member of the "public", so check for public permission, indicated by a null key
+ ClaimPermission permissionLevel = this.playerIDToClaimPermissionMap.get(null);
But this section didn't change:
//also check for public permission
- ClaimPermission permissionLevel = this.playerNameToClaimPermissionMap.get("public");
+ ClaimPermission permissionLevel = this.playerIDToClaimPermissionMap.get("public");
Nor did this section
//check for public container or build permission
- ClaimPermission permissionLevel = this.playerNameToClaimPermissionMap.get("public");
+ ClaimPermission permissionLevel = this.playerIDToClaimPermissionMap.get("public");
I don't understand enough of this plugin to suggest the fix, just hopping that this comment get a fix out faster.
-
View User Profile
-
Send Message
Posted Sep 27, 2014@bigscary
It's the only log entry I get. I have been using mysql from the start and I am sure the database details are correct. Are the GP database tables corrupt? http://pastebin.com/jb54ec9i
Thanks for the reply.
-
View User Profile
-
Send Message
Posted Sep 26, 2014@bigscary
I don't think I have the log from then. I'm using BungeeCord, so the server itself is set to offline-mode for Bungee, but Bungee is set to online-mode, as the server is premium. Also, I am using flat file. What do you mean by data before I upgraded? The player data and claims data? I do have a backup of that if that's what you're referring to.
-
View User Profile
-
Send Message
Posted Sep 26, 2014@bigscary
I have sent you the logs and data via PM.
Thanks again for all your help!
-
View User Profile
-
Send Message
Posted Sep 26, 2014@Willcomputerguy799
There are some clues here, but not enough to solve the case. I need your boot logs from the first time you ran with 8.1 or later GP, to see if I can find any problems there. Also are you in online mode or offline mode, and are you using flat file storage or database? It would help even more if you could share with me a snapshot of your data from before you upgraded.
@Feeriix
Is there more to that log entry? Usually this means GP just can't connect to your database, so double-check your SQL url, login, and pass. Is this the first time you're trying to use a database, or have you been running in database mode on previous versions of GP?
-
View User Profile
-
Send Message
Posted Sep 26, 2014Can't seem to update to any 8.x build. Using 7.7. Keep getting this error (using mysql):
Because there was a problem with the database, GriefPrevention will not function properly. Either update the database config settings resolve the issue, or delete those lines from your config.yml so that GriefPrevention can use the file system to store data.
What could be the issue? It works fine using flatfile.. Config: http://pastebin.com/rrm0iMZ4
-
View User Profile
-
Send Message
Posted Sep 26, 2014Uh, I'm having a problem. I downloaded the latest build of Griefprevention because it supports UUIDs... well.. my players are complaining that they get this error when they try to build within their claim: "You don't have <name>'s permission to build here". If my name were MinecraftPlayer, then it'd say "You don't have MinecraftPlayer's permission to build here". The other problem I'm having is that the plugin is lagging a lot. When I right click with a stick, to see claimed land, it takes 5 seconds or so to show in chat. It's not my lag, and before I updated it was fine. Kinda weird. Any help would be really appreciated.
Edit: Players can build within each other's claims if they're trusted. Also, I restarted the server and GriefPrevention starts up fine, with no errors. Edit again: Players' claim blocks are screwed up, but mine are fine. I'm also not experiencing the problems the players are. Even as not OP and not admin in Pex. After talking to a few players, apparently most people are having problems but a few players aren't having problems, including myself.
I am running Spigot 1.8 #1649
-
View User Profile
-
Send Message
Posted Sep 26, 2014@s4ndal1
You're absolutely right, my change in 8.1.3 won't help you because it's specific to database mode - that was my mistake making that recommendation to you. The logs you shared before don't indicate a problem, but I suspect there may be something else in your logs that will. If you still have your complete logs from that boot attempt, please share them. If not, please revert your data back to your snapshot and try booting with the latest version again so you can get a complete boot log.
Also for bonus points, if you can share your pre-UUID-update data with me, that would definitely help.
I'm sorry you're having to struggle through this. I will investigate as soon as possible.
@Bobcat00
Thanks for the assist!
-
View User Profile
-
Send Message
Posted Sep 26, 2014@themindstorm
You can use the claims.worlds configuration variable to list which worlds players may create claims in.
-
View User Profile
-
Send Message
Posted Sep 26, 2014@bigscary
"Fixed a mistake for DB-mode servers where the UUID migration would convert land claims to administrative unnecessarily."
I am unsure if this is going to address it, but I currently use a flatfile system, and I have attempted the conversion twice, and it does turn every single player owned claim into an administrative claim.
Once you give a reply I will go ahead and give it another test run.
-
View User Profile
-
Send Message
Posted Sep 26, 2014Can I disable this in my factions? I dont want people using it there.
Thanks
-
View User Profile
-
Send Message
Posted Sep 25, 2014@bigscary
I think you hit the nail on the head :) Version 8.1.3 FTW!
I've tested a few things and it seems that all is working now. I'll keep this version running on my server. Tnx for the quick update!
-
View User Profile
-
Send Message
Posted Sep 25, 2014@bigscary Offline mode, no. I've thought about doing that but not sure what implications would arise from it. But thanks for the logs advice, I'll look into that when I get a chance. Thanks for the reply, honored to be speaking to the Big Scary!!!, lol. :p