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 Jul 24, 2012@Pwnzsolo
I have no idea what you mean by gold ingots. This plugin does nothing with gold ingots. Maybe another one of your plugins has somehow attached gold ingots to use of the golden shovel? :) If that's the case, consider changing the config file so that you use a different tool for managing land claims.
@gusient
You're welcome!
@BoboTheTwit
I tried doing this before, and it didn't work out. The trouble is that the only way to guarantee the entire claim is cleaned up would be to use the aggressive restore nature mode, which would also damage the terrain if used without a human guiding it. :\
@myCraftServer
I'm aware of a bug in this area, or at least one has been reported. I need to double check my code. I'm going to look into this today, so please stay tuned. Thanks very much for your detailed bug report. I wish everyone who had an issue was so thorough in describing the problem! :)
Also, IDs with data values (187:2) are not supported. Just use the first number (187).
@Kakapo
This is described in the admin details page. Place an admin claim over the residence area, then use /trust public there. Now no one can claim there, but grief prevention will not enforce any building or access restrictions.
@midnighte2
Use /transferclaim to convert the administrative claim to a private one, then use /accesstrust public if you still want all players to use buttons and switches.
@Modelitup
You're running a creative mode server where you want dropped items to never disappear? That sounds very backward to me. Can you explain why you would do that? I don't think I fully understand your scenario. Are you running both creative and survival worlds on your server?
-
View User Profile
-
Send Message
Posted Jul 24, 2012Okay I've fixed my old problem, however I've got a new issue.
If I use ID's like this 187:2, they do stay in the config on server restart, but they do not work, as it's using a ':'. If I use 187.2 instead, it would delete the whole list of blocks and set that keys value back to default. How would I go about doing block ID's such as 187:2?
EDIT: Okay, I've just testing it using no sub-ids, so it's just the master ID and it blocks all the blocks that come under that ID. That's good. However, when I make a big list of the ID's like this : http://pastebin.com/xzRM7g2w : On server restart (to apply the new changes) all the block ID's dissapear from the list. Do you know why?
EDIT2: Okay, done more testing ;) Where I had taken out the Sub-id's, I had got multiple entries of the same block ID which it didn't like :) So basically, don't include Sub-ID's, don't have duplicate ID's in the list.
EDIT3: Block ID 149 in Tekkit (Crafting Table II) still allows you access even if in the container trust list.
-DanJames
-
View User Profile
-
Send Message
Posted Jul 24, 2012Is there any way to allow no cleanup of dropped items? I find this plugin is conflicting with plugins like "itemstay" where the items hover in place.
Great plugin, I wouldn't want to stop using if I could adjust this one thing.
-
View User Profile
-
Send Message
Posted Jul 23, 2012Is there any way to refuse chest access to Admin claims, unless listed.
-
View User Profile
-
Send Message
Posted Jul 23, 2012I tried to use Residence to claim purpose built buildings for new/old players alike and use its functionality for ownership and selling and renting, and this works EXCEPT GP maintains control of the blocks and the GP rules override the Residence rules. I have not figured out a way to give block rights priority to the residence owner over the admin GP claim site rights.
Is there a permission for this I have missed or will I need to request the services of a programmer to make some sort of API plugin to handle the ownership rights between the two plugins?
Thanks in advance.....
-
View User Profile
-
Send Message
Posted Jul 23, 2012Hey, is it possible to add an option for deleting claims in Creative Rules worlds? It would be great for that area to be regenerated, the claim removed, and the claim blocks returned.
Or, since you like the idea of users getting claims right in that world in the first place, maybe make griefprevention.admin (or whatever that permission node is) have the ability to delete claims in creative wolds?
Thanks!
-
View User Profile
-
Send Message
Posted Jul 23, 2012Would you be able to look at my config.yml and tell me if I'm doing something wrong please : http://pastebin.com/LpVRGdcf : I have tried putting an 'x' infront of the ID's as well ( as sometimes you have to do that for Mod ID's ) however players can still open them even while inside a claim.
Also, what do you do if the ID has a sub-id eg '126:4'.
EDIT: Sorry, didn't make it clear, I need the 'BlockIdsRequiringContainerTrust' section checked :)
Thanks, -Daniel
-
View User Profile
-
Send Message
Posted Jul 23, 2012@bigscary
Thanks, now I can protect all my creations on my server,
-
View User Profile
-
Send Message
Posted Jul 23, 2012My users keep getting this msg "need more gold ingots" when trying to re-size claims....even if they are attempting to re-size someone else's claim (not knowing they cant) it will give that message. They still get the claims blocks msg but then the gold ingots one goes right after that. I was only able to get the msg to happen for me once because it seems even in basic claims I can re-size their claims...which is a bit confusing but i can live with that. I have essentials economy on the server ( thinking bout replacing) and vault and just wondering if the gold ingots thing is because Grief Prevention has hooked into my eco plugin through vault. If so how can I disable this you need more gold ingots message as its confusing the less intelligent players. To be honest I'm confused as to what prompts the message. I thought maybe it could be when they attempt to re-size another s claim but then one guy got the msg when he was re-sizing his own. Sorry for the length of this post and its poor sentence structure. If you know whats going on here I would love to hear from you. Thank you. Love the plugin btw recommend it to all servers...to heck with towny
-
View User Profile
-
Send Message
Posted Jul 23, 2012@Arko2
You can do this with your bukkit.yml. Just alias /ban so that it does both /ban and /deleteallclaims. You can find details on how to create such a combo command on the bukkit wiki. I don't do this by default because many servers have an appeals process, so some players who are banned may be allowed back on. In the meantime, their claims would be griefable.
@netherfoam
Sounds like a case where you'd definitely want to look at cancelled events, since you're interested in what players type even when it's not going out to the chat. Just make sure you don't have the "ignore cancelled" tag on your handler, and you don't do the "if(event.getCancelled()) return" in your method body.
@datei80
If you mean for the whole server, yep, see config file. You can turn off the option which requires players to have permission for using other players' buttons and levers. This is discussed on the admin details page.
Or, if you mean just for one claim, see above. The command is /accesstrust public.
@Esaych
I'm starting to get the feeling that you're on a mission to find the most complicated scenario you can think of. If you want to require players to make claims to build, you can do that. But it will be for your whole server, not specific areas or even specific worlds.
If you want me to fix the big claim problem, please check your version number and update if necessary. If you still have the problem, send me your config.yml and claims data folder.
If you want to have a special area where trusted players can build without creating land claims, consider creating a separate world for them, then using your permissions plugin to grant only those players build rights in that world. Then you can disable claiming there without worry. I gotta warn you, though, the only folks you can trust are the folks you personally know in person. As soon as you let anybody else in for any reason, you're on your way to a griefing problem (not everyone is a griefer, but that policy will eventually find you a griefer).
Automatically claiming land will lead to very confused, frustrated, and possibly angry players. Other plugins have tried to do this, but griefers claim up everything by running around placing blocks everywhere. When the plugin adds a limit on how much land can be claimed, then players are tremendously confused and frustrated about what they have claimed, what they haven't, where their claims are, and how to manage all those accidental claims they didn't realize they were making until they ran out of claim allowance. Now the ideal of not having to think about claims crumbles, because suddenly the player has to start managing a big mess of accidental, randomly placed claims. Further, other players get really frustrated because everywhere they go it seems like land has been claimed for no reason - they don't see any builds, but still they're not allowed to build, because once a house was there, or once somebody placed some cobble blocks deep underground in that area.
@gusient
That's the way it should work. As described above, players get more claim blocks to claim a larger area as they play on the server. If players didn't have a reasonable limit, then griefers would run around claiming everything just to cause problems, turning the anti grief plugin into a griefing tool. So the solution for a player is to play more on the server, or try other channels like donating to the server for claim blocks, or asking admins how else they can earn some free blocks (voting for the server, building something cool, referring friends, etc).
If you're the server owner, you can give yourself more blocks with /acb, or create a free public claim with /adminclaims.
-
View User Profile
-
Send Message
Posted Jul 23, 2012Hi, I have a problem with this plugin because when trying to create a safe area, I get on the console: you don´t have enough blocks to claim that area. you need 204 blocks, for example. the only way i can make a safe area is making it very small, anyone can tell me what i have to do
-
View User Profile
-
Send Message
Posted Jul 22, 2012@TJW28
Thank you! It was griefprevention.createclaims that I needed to know. Thanks a lot!
-
View User Profile
-
Send Message
Posted Jul 22, 2012Hi,
is it possible that every allow to use all buttons, without taking each
/ac everyone or something like that
-
View User Profile
-
Send Message
Posted Jul 21, 2012@bigscary
Plugins like Showcase (And one I'm working on..QuickShop) ask players to enter amounts/info into chat. They then cancel the event (no spam). I know these plugins are rare, but they exist
-
View User Profile
-
Send Message
Posted Jul 21, 2012Hi
i am not sure but maybe delets claims of banned Players? =) it this possible?
-
View User Profile
-
Send Message
Posted Jul 21, 2012@netherfoam
Javadocs no, updated manual docs yes. :)
-
View User Profile
-
Send Message
Posted Jul 21, 20125.5 Updates!
Esaych, I looked into your problem again. I searched code for hours without any suspects, then finally tried creating a 1000x1000 claim on my server and letting the server run for a couple of hours. I didn't get a crash or any hang. My theory is that because there's a delay between my announcing a new version and Bukkit Dev actually publishing it in the files list at right, you may have accidentally grabbed an old version that didn't have your fixes. Will you please make sure you have 5.5 and try one more time with your big claim? If you still have the issue, please consider sending me your claimsdata folder and config.yml, so that I can directly paste your data onto my test server.
@netherfoam
I think you might be right, but I can't be sure. It depends on what the other plugins are trying to do with the chat. Do you know of any specific plugins which have a problem? My current thinking is that if I'm cancelling the event, then the chat doesn't go out to players so effectively, the player hasn't chatted, so then why would other plugins care what he tried to say? Also, other plugins have the option of looking at cancelled events if that's really what they want to do. Anyway I'm happy to adjust it, but not based on a hypothetical problem. Let me know if there's a concrete issue somewhere :) Thanks for the tip!
@Tigergruppe
That's already in. It's been in for MANY versions. No one can post an IP address in your chat (or even through whisper) unless you list that IP address in GP's config file. The exceptions are ops and anyone with the spam permission. That guy claims that his will filter website addresses, but really what he means is that he can filter the very well formed web addresses, but not obvious and simple workarounds like "visit my server instead, minecarts dot com!". You can see where any filter which would block that message would also block lots of other types of chat.
If you want good anti spam, GP is the best. Minimum false positives, maximum spam shutdown. Many, many months of careful refinement.
@fungreenfox
I'm very sorry you're having trouble wiht SQL, Fox, but I can't help you with database problems. I have no guess as to why you wouldn't be allowed to create the tables needed. Are you sure you need the database mode? Have you tried file mode? I think you'll be surprised at the performance.
Have you listed your tables to see what's there? Have you recently updated permissions, modified any table data yourself, dropped any tables, etc?
-
View User Profile
-
Send Message
Posted Jul 21, 2012can you please tell me, why GP can not create its files in the mysql? It has all permissions for owner to r/w in the folder. It worked first 12 hours, then more playerdata shows up, and it seems its some players names and or cant create cells
15:16:14 [INFO] [GriefPrevention] Enabling GriefPrevention v5.4 15:16:14 [INFO] GriefPrevention: Grief Prevention enabled. 15:16:15 [INFO] GriefPrevention: ERROR: Unable to create the necessary database table. Details: 15:16:15 [INFO] GriefPrevention: Table 'griefprevention.griefprevention_nextclaimid' doesn't exist 15:16:15 [INFO] GriefPrevention: Because there was a problem with the database, GriefPrevention will not function properly. Either update the database co nfig settings resolve the issue, or delete those lines from your config.yml so that GriefPrevention can use the file system to store data.
14:37:19 [INFO] [GriefPrevention] Enabling GriefPrevention v5.4 14:37:19 [INFO] GriefPrevention: Grief Prevention enabled. 14:37:20 [INFO] GriefPrevention: ERROR: Unable to create the necessary database table. Details: 14:37:20 [INFO] GriefPrevention: Table 'griefprevention.griefprevention_nextclaimid' doesn't exist 14:37:20 [INFO] GriefPrevention: Because there was a problem with the database, GriefPrevention will not function properly. Either update the database co nfig settings resolve the issue, or delete those lines from your config.yml so that GriefPrevention can use the file system to store data. 14:37:20 [INFO] [FalseBookCore] Enabling FalseBookCore v0.93.1alpha
-
View User Profile
-
Send Message
Posted Jul 20, 2012@bigscary
Any chance something like this http://dev.bukkit.org/server-mods/antiad-jne/ can be built into GP?
-
View User Profile
-
Send Message
Posted Jul 20, 2012@jamzam90
He has a point :S Could you help us out with coding the API a bit more nicely? And javadocs? :)