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 27, 2013@2coolforu22
How is that an issue. Its only happening because the guy your hitting has an empty inventory AKA no weapon its there to stop spawn killing. A smart player could also make use of it as well. to solve that a radius to the maps spawn could be added.
hmm after looking at the plugin.yml there seems to be no easy way for me to disable the trust commands from players as its all wrapped into the 1 permission node. instead of being a grouped node like i thought it would of been. ( so there seems to be no fine grained permissions for the commands.) I may for now be able to edit the plugin.yml some and make what i need to prevent this whole players hiding in other claims. issue But Id like to think that i should not need to do that because all the permissions and flex i need to fix the issue should of been there.
Just in case I am being unclear here the permission: griefprevention.claims Should be a Node with children nodes that are for each of the commands that have it listed as its permission. This Way it could be implemented with out breaking existing servers.
-
View User Profile
-
Send Message
Posted Jul 27, 2013@BC_Programming
i rechecked my config and Found that the GUI items were still on the break list..... I failed some how was sure i removed them saved file and rebooted the server... Sigh..
I was unable to win as the defender by killing the attacker he simply re spawned ( I guess within range ) and was able to keep attacking me. Breaking more blocks etc.
-
View User Profile
-
Send Message
Posted Jul 27, 2013@plokijuhy
you can use /adminclaims to switch to administrator claims mode if you have the appropriate permission. Administrator claims do not require player claim blocks to create.
@RustyDagger
Cannot reproduce. Attempting to break such blocks during a siege gives me the expected "this material is too tough to break" message. I see no reason the owner would not also get the message that they cannot build while under siege.
When a player dies and they are participating in a siege, the siege is over and they are the loser. If the attacker was the winner the claim is unlocked for a temporary amount of time. If revert is enabled, all set blocks are reverted. The siege also ends if the attacker leaves the area (though I'd have to check the specific range). It also ends (defender loss) if the defender leaves the claim a given distance, which I think is 20 blocks.
There already is a cooldown on sieges as well. A player may not siege the same player or claim for an hour (not yet configurable).
The message issues are trivial to fix. I wasn't able to duplicate any of the other behaviours you observed.
-
View User Profile
-
Send Message
Posted Jul 27, 2013can you make a command to see who placed the block
-
View User Profile
-
Send Message
Posted Jul 27, 2013This is pissing me off I just got the plugin and watched the whole video thinking it'd be good but I cannot claim my whole spawn because "i dont have enough blocks" wtf does that mean someone please help me :(
-
View User Profile
-
Send Message
Posted Jul 27, 2013@RustyDagger
For one thing, you are testing features I added almost exclusively at your request. Nobody tested these features because you are the only person that has so far expressed interest in them. I added them because I'm sure others would. So far you are the only person asking for these new features, and thus the only one testing them and therefore also the only person complaining about the issues you find as a result. If your reports of problems are going to go hand-in-hand with criticism about the process used to create it, I'm just not going to bother to add these features at all.
The reason the features don't work is because of bugs. probably simple ones. Why? I don't have two minecraft accounts, so I have to actually add custom logic to the plugin just to test it. And because they are development builds I'm less wary about adding possibly broken code, as long as it doesn't have huge opportunities for data loss. I also don't exactly draw a salary from this, so it's not like I can spend more than 10-20 minutes experimenting with a change.
-
View User Profile
-
Send Message
Posted Jul 27, 2013Any way to get the buying claims functionality to work with essentials signs? IE:
[trade] $2500 500 GPLand:1
500 would be the amount of claim blocks you'd want to sell, GPLand would be the itemID, 1 would be the amount
$2500 would be the amount to buy 500 claim blocks, etc.
-
View User Profile
-
Send Message
Posted Jul 27, 2013I keep having a problem with pvp when two players are trying to do pvp it keeps coming up with you cannot fight with the Defenseless player is there any way to turn this off
-
View User Profile
-
Send Message
Posted Jul 26, 2013@fungreenfox
GPFlags is another plugin mate. i think from your comment there that you did not realize that. :D
@BC_programing
The error message that's put in chat when you resize a claim and DO NOT have enough claim blocks IS really confusing and wrongly worded. It says
"The Re sized claim Would not cover Enough Blocks. Claims must Use at least X Blocks"
Blocks With Inventory or GUI are Always breakable during a siege this includes Chests.... The Block Names are NOT on the break list. but Break any way.. :( kind of makes the chest looting feature pointless.)
All this is a result of 20 -40 min testing on a local server with 2 mincraft accounts honestly im starting to think no one has ever used siege because its so broken.
The X gets bigger the more you move out and expand the claim. This message should be stating that you need more claim blocks to do that.
Another Message that's broken is the player not in area when you type /siege it shows {0} instead of the players name.
The win Conditions for a Claim owner On a Siege battle seem really unfair i cant even work out what they are... it should be first one dead loses but its not. Also if that is done. a cool down on siege the same person again may be needed.
Chests and any block with a GUI are always breakable during a siege Even when not on the break list. Making the chest looting feature pointless.
Honestly Siege is so far broken...
-
View User Profile
-
Send Message
Posted Jul 26, 2013@Alshain01
i see it in the config for PVP and Spam, but not for claims, and claims will need an option for allowing claim owners and trusted ones.
-
View User Profile
-
Send Message
Posted Jul 26, 2013@RustyDagger
@fungreenfox
Guys, GPFlags has both the command blacklist and the deny entry/deny teleport. And it's commands are as easy as GP. You shouldn't ever have World Guard if GP is your anti-grief.
-
View User Profile
-
Send Message
Posted Jul 26, 2013@RustyDagger
I came up with the idea today, when some politely players were annoyed by other players setting their claim and just teleporting inside the walls made. Currently, my only solution is giving them a WG claim with cmd denyal at. Most users are not familiar to WG and commands and its paramters, can be a bit advanced there. So if GP can do this, it will make a lot of players happy. Or even if you are having a Parkour in GP claims, you would be able to deny flying etc.
-
View User Profile
-
Send Message
Posted Jul 26, 2013@fungreenfox
You mean like a command blacklist for inside claims. it could be added to the rules section and have a section for commands you cant use outside claims too. then you could in theory restrict users to only using a command in claims they have permissions for.
hmm I could see how that would be handy might be tricky to implement tho.
-
View User Profile
-
Send Message
Posted Jul 26, 2013Is it possible to deny guests setting their homes in a claimed area without having trust? Else this is a feature request.
-
View User Profile
-
Send Message
Posted Jul 26, 2013I have quite a few active plots on my server as it is a town server and we use it with the RealEstate expansion and MySQL. Well when users use any type of plot command or create or resize a plot, the entire server seems to freeze for about 1 - 5 seconds. This includes using trust, abandonclaim, etc.
-
View User Profile
-
Send Message
Posted Jul 25, 2013Players are still unable to retrieve their horses if they walk into/ride into someone else's claim. Could this be a config problem? http://pastebin.com/sksMvUSB
-
View User Profile
-
Send Message
Posted Jul 25, 2013@diskman2000
Use something like variable triggers for this. I use it myself for this very purpose, where I have players place a bed and then be told that if they place a chest as well in the next 10 seconds then their standing location will become their /home. Setup a script to work with block placing and then there is no way for outsiders to set home in others land as they do not have place permission.
I don't think integrating the /home command is in the scope of the project.
-
View User Profile
-
Send Message
Posted Jul 25, 2013@BC_Programming
I think that's just because ur siege ur self I had no errors at all during a siege when using my 2 accounts on my local server If i did i would of posted them :D
reverting those features makes the plugin useless to my needs O well replacement hunt time I guess.. :(
-
View User Profile
-
Send Message
Posted Jul 25, 2013@RustyDagger
I may just revert the functionality. Entirely, including removing the reverting feature.
Fact is I changed my local copy to allow me to siege myself for testing and there are Exceptions being thrown that shouldn't be possible in places that don't make any sense at all. In fact during a siege it appears that every single event triggered causes an error. Including those that contain absolutely no siege-related logic.
EDIT: OK, nevermind, I goofed and deleted a rather important line. while testing that broke everything.
Also seems like I accidentally inverted a condition so that it was treating block breaks opposite to what it was supposed to. It seems to work now, though I don't know what oddness Sieging myself may have resulted in.
It's still possible to "grief" since it only records blocks that were broken, so it's possible to break sand or gravel and the falling sand and gravel are not 'saved' from being broken or reverted. It could be possible to do so, but then it would be easy to exploit and since Anvils are expensive and use that mechanic I'm sure it would probably end up being exploited for anvil factories or something; So I'll just leave that as a minor amount of permanent damage that can be done as far as I'm aware.
It would also be possible to allow explosions to damage soft blocks during a siege and store them in the same "reverting" structure, though I've not made that change.
The next build should work better for you @RustyDagger.
-
View User Profile
-
Send Message
Posted Jul 25, 2013Can you add a way to block commands? It would be AWESOME to be able to block /sethome for untrusted users. :)