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 9, 2013BC_Programming, does it matter which economy plugin it is?
-
View User Profile
-
Send Message
Posted Sep 9, 2013@BC_Programming
Arr dam it i forgot about the new launcher changing that. Once i finally get a job ill see about helping you out. Im only a medical test and a 4 day training corse away from having a job YAY. I need the cash so bad lol. I may also be dropping GP after that I have plans to have an idea of mine coded.
-
View User Profile
-
Send Message
Posted Sep 8, 2013@ljprevo
That is such a great idea I went back in time two months and added it to the development build. :P Claim limits per player can be set per world. They cannot be set per player entirely (As in all claims everywhere, at least not easily) because of the way claims are loaded, but it should already be working to limit the total number of claims.
-
View User Profile
-
Send Message
Posted Sep 8, 2013I really wish that you would add a total amount of claims, instead of just a total amount of blocks.
Lets say they have 1000 blocks, they can make 10 10X10 claims. I want to be able to limit them to only 5 claims, where each can 20 X 10 each. They could then get more blocks but only 5 total claims that can be up to their allotted size. Make sense?
-
View User Profile
-
Send Message
Posted Sep 8, 2013@JustisR
you can use /trust [permission]. If you put the name of a permission in square brackets, the command will perform the trust on all players that are within that trust group. I think it either applies only to online players or players that have joined the server with GriefPrevention installed. With the dev build you can create groups in config.yml and use /trust g:<groupname> to trust all players in that group.
@deleted_9935739
Not that I know of- at least not without changing the plugin.yml description file in the plugin jar.
@oikeemine123
You need an economy plugin and vault installed for the claim block buy/sell to work.
-
View User Profile
-
Send Message
Posted Sep 8, 2013Hi! I have a problem with this plugin. When I try to buy claimblocks by typing /buyclaimblocks it says ''Sorry, buying anhd selling claim blocks is disabled.'' How can I enable it?
-
View User Profile
-
Send Message
Posted Sep 8, 2013Is there a way to turn off command aliases? Like /ac? I need to use that command for another plugin.
-
View User Profile
-
Send Message
Posted Sep 8, 2013-
View User Profile
-
Send Message
Posted Sep 8, 2013@TJW28
ahh that might make more sense. Still doesn't explain how it occurs entirely but at least it's something I didn't explicitly give a go. an NPE in that area of the code could only occur if a playerData or the claim being resized was null, but both those aren't possible at that point since a few lines previously both those values are inspected
Migration works here also. I'm reworking that anyway though to allow it to work between any two DataStore implementations.
-
View User Profile
-
Send Message
Posted Sep 8, 2013@BC_Programming
HI, yes, it was a dumb type, I am testing using the #170 dev build.
I should of pointed out, that the claim I was trying to resize, was "Another" players claim, not my own. I was subsequently able to resize my Own claim without issue. I also went and tried to resize other players claims, and got the same error as previously Mention.
Now, thinking it may be related to how claims are stored flatfile, I changed so it now uses mysql. Connection was fine, and I had alerts in the CP about claims being moved over, but, sadly, no claims were in fact copied to the database. ( its no big issues, I have backups and its just on a test server. ) Any reason I lost all claim data ?
Thanks
-
View User Profile
-
Send Message
Posted Sep 8, 2013is it possible to import residence protections into GP ?
-
View User Profile
-
Send Message
Posted Sep 8, 2013@TJW28
FWIW, the latest dev build is currently #170, but the youtube video is titled that it's using that so I assume that is a typo in the comment here.
Those sorts of logs are the most useful. Thank you for taking the time to get that information to me/us. :)
The line it says causes an error I don't think can possibly have that error occur, because all the cases that would cause a NPE on the reported line would cause one earlier. The only thing I can think would be that you might not actually be using #170? (all the dev builds identify as GriefPrevention 7.8, fwiw).
I popped on my test server to double-check that this wasn't a issue that was introduced by the changes I made most recently that I somehow missed, and it resized without issue. Can you double-check that you are using #170? The reason I am uncertain is because you mention a different build here in the comments, as well as the reported line not possibly lining up with the problem.
@Durell_1011
That is how I understand how it works, yes. The option will probably be removed once Block placement and Breaking are added as Rules, since it would be possible to get the same functionality with those, but in a more flexible fashion.
-
View User Profile
-
Send Message
Posted Sep 8, 2013Just to know if I understood this right, the option NoSurvivalBuildingOutsideClaims means that players in normal Survival mode have first to create their claims before they can build? So they can only build in their Claim? If you set this to true they can modify any unprotected block in the world?
-
View User Profile
-
Send Message
Posted Sep 7, 2013HI, Am once again trying to get this amazing plugin up and running with the latest Dev Builds ( 7.8 #170 ), but am still haveing issues. This is the First time I have actually seen ANY error in the control Panel, so, it may help somewhat.
Heres a video of what we are experiancing.
dev build #130
Heres the error generated in the video.
FInally, without the above issue, we still are plagued by the issues demonstrated Here .
With all the advancements, and features added to the dev versions, We are really eager to get 7.8 implemented on our server, and, I would happily pay, if that would help to investigate and troubleshoot our issues. Thank you.
-
View User Profile
-
Send Message
Posted Sep 7, 2013@BC_Programming
I think this is the issue i was making it /accesstrust public this allowed them to have the ability to abandon claim even though they thought they were abandoning there own. Since they were standing in the spawn at the time. I think we (like how i claim i have something to with it) block ability for anybody but owner to abandon a claim.
-
View User Profile
-
Send Message
Posted Sep 7, 2013is it possible to make all non aggressive mobs in a claim not killable and all aggressive mobs killable? Is this possible with 7.7, and how?
-
View User Profile
-
Send Message
Posted Sep 6, 2013The new launcher does not allow you to run in offline mode unless you have authenticated with that account.
I'm also not about to use a crack of any sort to run a second user on off-line mode, either.
-
View User Profile
-
Send Message
Posted Sep 6, 2013@Awsmpossum1313
I wasn't able to reproduce the problem, at least not as described. What I did:
Created massive claim (It was bigger than 100x100). made it an admin claim.
Shut down and restarted the server (claim was still there).
Created a new claim on the edge of the admin claim. Shut down and restarted the server-
Both claims were still there.
So I thought, alright, let's try them both at once- Maybe that restart in the middle is the problem.
Created the large claim, transferred it to an admin claim, and created a new claim touching it on one side. restarted the server, and both claims were still present.
Just realized I didn't lock the claims, but repeated both sets and locked the admin claim in each case, and it still didn't vanish.
It would seem your disappearance issue is caused by something else. From what I can tell, /lockclaim doesn't actually prevent the claim from being abandoned, but simply issues an extra warning, which is a bit of a strange way of doing it.
@seekzone
GP doesn't interact with other protection plugins. I don't know how factions works and thus have no idea how GP would work with it.
-
View User Profile
-
Send Message
Posted Sep 6, 2013Hello.
I have seen the video and realized it's an amazing plugin. Before I try it out though, I wanted to ask about the protection and factions. Say I have a faction, and the chunk is claimed. What happens with the protected zone? Does it stay? is it erased/removed?
Amazing work and I hope you keep on working the plugin.
-
View User Profile
-
Send Message
Posted Sep 6, 2013@Durell_1011
Protected to the sky, but not to the bedrock. I think by default it's 10 blocks down (going from memory). This prevents players from protecting the caves below and preventing you from mining any loot you might find due to large claims that cover the area.