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 Apr 24, 2012Hey saintcrime,
Use mcmmo or another party mod for your pvp problems with friends. You can only give permissions for the party part if you don't want the abilities and xpgain/levels. Anyone in your party takes no dmg from you. And you have party chat as well
-
View User Profile
-
Send Message
Posted Apr 24, 2012@Noirdrath
I too would like it if I could use TNT in my own claim. Not a big deal for me though.
-
View User Profile
-
Send Message
Posted Apr 24, 2012@shutka
I don't know what the advice will be from bigscary but I create a admin claim using /adminclaims that includes my worldguard city and then /trust all.
This creates a huge GP claim which everyone is trusted in (and so can build wherever worldguard lets them) but stops them being able to claim new areas using the shovel or placing a chest for the first time!
-
View User Profile
-
Send Message
Posted Apr 24, 2012bigscary, he basically means flags from worldguard for claims. Thats what he wants.
-
View User Profile
-
Send Message
Posted Apr 24, 2012All my users are experiencing a problem where if the person with the claim tries to use TNT in their own claim they get the explosion but no blocks break.
Now if that were a grieffer then that is cool, but this is the owner of said claim.
Any idea what is going on?
-
View User Profile
-
Send Message
Posted Apr 23, 2012I'm certain I'm having a problem. :-) Any logs I can look at?
config.yml: http://pastebin.com/2GYBC1gy
startup sequence: http://pastebin.com/2BSCXe16
EDIT: You explained at one point the playerdata format. I bet my problem has something to do with this. Here's me:
http://pastebin.com/aUjgFXac
Here's another one on my server:
http://pastebin.com/J98qerP9
-
View User Profile
-
Send Message
Posted Apr 23, 2012@shutka
I don't know what you mean by "worldguard integration". Please explain how you would want the two integrated, and why it would help you.
@Sollo360
That's super weird, do you have any other plugins? If so, do you have a similar problem with them? I'm guessing it has something to do with your hosting provider, or maybe something else you're running on the server yourself is doing something strange with your files.
@Rtzon
Just use /reload. Maybe you don't want to reload all your plugins, but adding a custom /reload command just for griefprevention is splitting hairs and adding to my test effort for an itty bitty payoff.
@Lius98
You can disable claims by listing only a world that doesn't exist, OR you can set both the require permissions to create claims to true, and set the automatic new player claim radius to -1. This combination would make creating claims impossible unless a player has the specific permission required.
@AuntieBeast
I'm very, very glad you're so satisfied with your transition. :)
@ThisUsernameIsMine
Many have asked, and it's a huge work item for me to make the plugin localizable (translatable). I will probably come back to this issue eventually, but right now it's not on my to do list.
@ThisUsernameIsMine
See FAQ. Short version: two major reasons. First, not making claims go to the sky by default means a jerk can build overtop you and claim it, making it possible for you to extend upward later. Second, I just didn't design for it, and doing it now would be an immense effort and would add lots of bugs that I'd have to gradually squash over time. It would also hurt performance noticeably.
@sebastiannielsenrobin
1) Seems tempting at first, but imagine the headache of having to always reduce the size of your claim when you don't want to spend those blocks. Also if you don't have enough blocks temporarily, you could end up in a situation where later when you DO have blocks to claim with, you're already well beyond your claim boundary and you don't get the automatic resize, AND you don't realize it, leaving your build vulnerable. I think it's best for players to maintain some awareness about the size of their claims, and give them tight control over where and when they spend their limited claim blocks.
2 and 3) That's a nice improvement which would eliminate the potential for abuse by griefers, but I think my original concerns still apply.
I do understand the value in what you're asking for. I just don't think it's worth the additional load in coding and (more importantly) testing to ensure quality, to add these features when so few have asked for them (you're the first to persist after an explanation for the current design). It's possible that if many more ask for something very similar, or someone makes a stronger case for these changes, then I will change my mind. :)
@saintcrime
At least 15 blocks under sea level is considered "underground". I've seen one case where a griefer tried to grief with lava by creating a trench 15 blocks deep, and dumping water down there. I decided it was a laughable attempt, and a risk I was comfortable with, given the additional coding/testing effort and cpu cycles required to do something more complex.
@spblat
I didn't change anything, but be sure you're not just standing around. If you don't move at least 3 blocks in 10 minutes, you don't get blocks for that 10 minutes. It's tough to test this on a live server, but if you feel certain you're having a problem after looking again, please let me know.
-
View User Profile
-
Send Message
Posted Apr 23, 2012We don't seem to be accruing claim blocks anymore. Did something break or change? I checked my config file and I don't see anything amiss. Could be something happened several releases ago, I'm all out of blocks :-(
-
View User Profile
-
Send Message
Posted Apr 23, 2012@sebastiannielsenrobin
well i did not say it cant be done, but i meant can it be done without causing more resource expenses
-
View User Profile
-
Send Message
Posted Apr 23, 2012Hello Bigscary,
I thought you had added an automatic claim deletion after no activity in so many days a while back. Was this removed?
-
View User Profile
-
Send Message
Posted Apr 23, 2012cvxx7q: It can be checked on each block placement on the claim boundary. Eg in the code that checks if you are allowed to place a block, also check if the claim should be extended.
-
View User Profile
-
Send Message
Posted Apr 23, 2012Hello Bigscary,
For Lava Placement it states above in description-"Lava can't be placed very close to another player, and may only be placed either underground,", How is "Underground" decided? Is it a certain depth, sealed off area or below a certain type of block?
Thanks Saintcrime.
-
View User Profile
-
Send Message
Posted Apr 22, 2012@ThisUsernameIsMine
current claim layout would not tolerate stacking and it creates loopholes for griefing
@sebastiannielsenrobin
your auto-extend idea seems good, but it may be resource expensive to run checks and performs extensions like this, especially if we rely on GP to track every player..
HAS GOLD SHOVEL?
IS IN CLAIM?
IS NEXT TO CLAIM?
IS PLACING BLOCK?
and probably a couple more
if bigscary could apply the vertical depth extension mechanics to horizontal extension that would probably work best, but even now the vertical tacking may be expensive already
the idea seems good, it just has to be hammered out a little ;)
-
View User Profile
-
Send Message
Posted Apr 22, 2012bigscary: I have a addition to the suggestion about autoclaim: This could be configurable: Autoclaim could be in 4 different modes: Autoclaim: 1 through 4
1 = If a player places a block on the claim boundary, its automatically extended with one block in that direction given that the player has enough blocks left for extending the claim. A block on claim boundary corner will extend the claim in both these directions. Golden shovel has no use except for admins.
2 = Same as 1, but requires that the building player HAS a golden shovel in her inventory AND/OR inside any chest inside of the claim being builded on. If not, the player will get a warning message about that. (it does not need to be in one of the 9 quickslots, its enough if its in inventory)
3 = Same as 1, but requires that the building player HAS a golden shovel in her inventory. (inside chest is not enough). (it does not need to be in one of the 9 quickslots, its enough if its in inventory)
4 = Autoclaim completely disabled. Player must manually extend their claims by equipping the golden shovel.
Note that autoclaim is suggested only to extend claims already there, not create new claims.
About the number of claims, its a easy feature to implement, and it could be configurable. I understand your concerns about player limited to one single claim and cannot "grow" in it because of neightbours. I think its up to the server admin, I would rather allow small minimum claim size, large initial claim, large inital blocks, and then allow players to gather pretty many blocks per hour, but instead limit player to one single claim.
-
View User Profile
-
Send Message
Posted Apr 22, 2012@cvxx7q
I understand :-)
Something else: What made you decide to not implement/support stackable claims?
I host a mixed-gamemode, single world server and often encounter that
people want but can't build below or above someone's claim.
Thanks :)
-
View User Profile
-
Send Message
Posted Apr 22, 2012@ThisUsernameIsMine
Strange the TODO list has wandered off, i suppose it was moved to the API Ideas page, extra languages was on there though it is not a high priority, code before translation unfortunately
-
View User Profile
-
Send Message
Posted Apr 22, 2012Since this plugin is so popular, i bet its used by non (native) english speaking people as well.
Is there a chance that Grief-Prevention will support other languages in the future?
No doubt many would appreciate that :-)
-
View User Profile
-
Send Message
Posted Apr 22, 2012BigScary: we implemented this on an existing map last night. We were armed for bear expecting lots of adjustment issues.
This went so smoothly, we suspect you somehow drug the players when the plugin is implemented!
Great work, and the /transferclaim works great and has been a huge help.
-
View User Profile
-
Send Message
Posted Apr 22, 2012Hey big i have another idea if it isn't already implemented, there should be a node the deny ALL kind of contact with using GP, I want to use Factions claiming for my users and let the Admins use GP to protect for ex. Spawn, is this possible to do? I would be really glad if you added it :)
-
View User Profile
-
Send Message
Posted Apr 22, 2012@Rtzon
the general view of "Reload" from a technical stand-point is that they are no good and at best only useful for testing purposes and debugging/development (quick code swaps and so on)
outside of these circumstances a reload has no benefit and in an online server this can be extremely detrimental
[TL;DR]
AFAIK bigscary has rejected implementing any form of reload