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 Dec 22, 2013In my creative world my players can place blocks outside of claims but not destroy them (They should not be able to do either!) Here is the config for the creative world. http://paste.ubuntu.com/6613900/
-
View User Profile
-
Send Message
Posted Dec 22, 2013@BC_Programming
well, what line protects horses from being killed? And I can't damage cows, sheep, chickens or any other friendly animal in claims. Even though my world config looks like this: http://pastebin.com/raw.php?i=Qi8fXLp3
-
View User Profile
-
Send Message
Posted Dec 22, 2013Love this plugin <3
I'm running a server though where we've got a central city that's admin claimed so that nobody can build within it. We'd like however to let our users open chest/harvest crops/etc within the claim. Is there any possibility to do this or easily add the functionality to do so?
-
View User Profile
-
Send Message
Posted Dec 22, 2013could you help me with that? heres my server log:
http://pastebin.com/piePh2MA
-
View User Profile
-
Send Message
Posted Dec 21, 2013I've been trying to configure the world.yml file for your plugin, but it seems like every time i reset the server so that the changes take affect, the world.yml is reset completely.
Anyone have any thoughts on why this may be, or what I may be doing wrong?
-
View User Profile
-
Send Message
Posted Dec 21, 2013@Bester111
1.7.4 is almost entirely client-side fixes. Unless they make HUGE changes to the API between the Bukkit API for 1.7.2 and the bukkit API for 1.7.4, it will work fine with 1.7.4.
@CoolGamrSms
Siege overrides have SiegeAttacker and SiegeDefender. You'll also want SiegeBystander. to override and force it to deny.
-
View User Profile
-
Send Message
Posted Dec 21, 2013Hmm, we ran into another issue. We have it configured so that during siege, neither attacker nor defender can place blocks (which I believe is the default). However, for whatever reason, players not involved in the siege are able to place blocks in the sieged claim. Is this a configuration flag we're not seeing or a bug?
Thanks, CoolGamrSms
-
View User Profile
-
Send Message
Posted Dec 21, 2013@Alurous
I like to make one large claim around the entire area use subclaims on servers where there is no maximum block cap. Each subclaim has individual trust settings that you can set with /accesstrust, /containertrust, and /trust. Each one contains the prior such that container trust includes access trust and the plain /trust includes both container and access trusts. If you have a limited number of claim blocks it may be better to leave the roads unprotected and fix them as you may need to and have each house be a separate claim using the above trusts as appropriate.
@Bester111
The plugin loads and says "Grief Prevention Running for Minecraft 1.7.x" so I don't understand where you got 1.7.4 from it. There is no CraftBukkit 1.7.4 yet, but 1.7.4 clients are able to play on 1.7.2 servers natively.
@Nentify
The bonus blocks do not count towards the cap, however if all players had say 10000 blocks as a cap and those promoted to say the first rank were given 1000 bonus blocks, it effectively gives them a 11000 block cap (aside from any other block reward system if you are using one).
@ultra1108
I meant try changing the CreativeRules setting. There are two other rules, BlockPlacement and BlockBreaking that can be set for claims and wilderness. Try adjusting those to allow or deny for your server needs.
-
View User Profile
-
Send Message
Posted Dec 21, 2013@Sargewood I tried the creativerules in the config, i deleted all the worlds under creativerules:, but it auto-adds them because it knows which worlds are creative. PLEASE HELP!
-
View User Profile
-
Send Message
Posted Dec 21, 2013ok stupid question craftbukkit is at 1.7.2 but your pluggin is at 1.7.4. How do i get my craftbukkit to 1.7.4. ok lol a second question. I have towns and cities set up on my server how will this work to protect them and or streets ty
-
View User Profile
-
Send Message
Posted Dec 21, 2013My question is, what if I get a plot of land, build a village within it and I want to have other people live in it, how do I add people to be able to open chests/doors/use everything ?
-
View User Profile
-
Send Message
Posted Dec 21, 2013@chirochord
This is the same issue I reported just a little while ago (though I didn't word it as well). If you read back he says that turning sieges on will automatically turn these protection settings to false (and he has two lengthy reasons why, just check the other comments). I tested this on some builds. Some builds even if you have siege on in one world, the admin and claim protections turned false for all worlds. The latest build 215, however, is turning it to false for me no matter what I do as well.
-
View User Profile
-
Send Message
Posted Dec 21, 2013@DonGrif
Somewhere in the process of updating my config for later development builds I had an issue where no one on my server was getting any claim blocks. I had overlooked the MaxClaimBlocks setting and it somehow was 0. Make sure this number is what you intend it to be. Players above this number will not earn claim blocks, but players below the number will.
-
View User Profile
-
Send Message
Posted Dec 20, 2013@Smac3223
Any ETA on when both the plugin itself and the page info will be updated?
No. Though effectively, the plugin is already updated. In order for an ETA to exist, the work put into it needs to be consistent. Some weeks I'll spend a few nights up until 5 AM trying to reproduce an issue that was vaguely reported. Other weeks I Don't even touch the project at all.
@Tirco
But is there a way to disable PvP in claims, and have it only enabled when a siege is going on?
As I explained in a earlier comment regarding this, that is not possible.
or, well, it IS possible, but it would be exploited in ways that would make it even worse.
Let's consider the setting. You want to protect players that are in claims, except when that player is being sieged.
So the question is, how would that work? How would the plugin know who can and cannot be damaged? Every single one I can think of has some way for it to be exploited in a major way by a player, and with ideas just off the top of my head.
The first idea is to simply have it allow damage between the attacker and defender of a siege.
But what if that attacking player makes a claim nearby? can the attacker damage that player? They are inside their own claim. So we say, ok, simple- we'll allow damage to the player if they are involved in a siege even if they are in another claim that is not under siege.
Fair enough. But what if that player has friends who are also inside that other claim? For example imagine if an attacker lays siege to a castle, then goes into their nearby wooden hut house inside their claim. The defender first has the issue that leaving their claim will cause them to lose to siege, but it has the addition issue that any other player within that defending players claim is invincible. They are protected from damage.
So the other workaround is to say, have it so a player can be damaged by the defender of a claim if he is inside a claim owned by a player that is the attacker in that siege.
Good, it's fixed. Hooray.
So them the enterprising band of friends just has somebody else lay siege. eg. Say we have the attackers, Bill, Thomas, and Fred, who want ot siege the castle of Chumpsworth.
Chumps worth has a large claim. Let's say Bill makes a nearby claim. He then does /siege, and then hides in that claim. He is protected by the land protection. So we have the special consideration that if he is the attacker in a siege he can always be damaged by the defender. But that is why Thomas and Fred are along. If they are inside bills claim, they are protected because there cannot be PvP combat inside claims. So we have the additional stipulation that A player can be damaged by the defender of a siege if they are inside a claim owned by the attacker of that siege.
So Then it can simple be Thomas doing the siege. He runs back to Bills claim and he's protected.
There is no reasonable way to prevent exploitation without making things very dangerous. The only way to really do it would be to make all players on any claim that has a attacker or defender in a siege vulnerable to attack. Which is ripe for even more vulnerabilities. Aside form that it could be done such that only an attacker and defender can damage one another; other players with the defender cannot damage even on a claim, and other players with the attacker cannot damage either. The players can still do damage by using lava, dispensers and so forth, while still being 100% immune from being damaged.
Further still, it would mean pretty insane special logic surround who can be damaged where and by whom.
-
View User Profile
-
Send Message
Posted Dec 20, 2013Hi! I've been looking through the configs, and may just be wery blind... But is there a way to disable PvP in claims, and have it only enabled when a siege is going on?
Sieges are kind of stupid if there's no PvP in the claim, but i still want people to feel safe on their claims! :)
-
View User Profile
-
Send Message
Posted Dec 20, 2013@Alshain01
Can I not actually set a cap though, instead of giving them free blocks?
-
View User Profile
-
Send Message
Posted Dec 20, 2013@Cytooxien
set it to false or remove the world from CreativeRulesWorlds as it does similar thing
-
View User Profile
-
Send Message
Posted Dec 20, 2013Hello one quick question, can I set NoSurvivalBuildingOutsideClaims differently for every world ? All other values I can share but I would need to alter this for one particular world.
-
View User Profile
-
Send Message
Posted Dec 20, 2013Hot to disable building outside claims in a world at the new Version?
-
View User Profile
-
Send Message
Posted Dec 20, 2013With the bukkit beta of 1.7 out and since I'm still using quite an older version of this plugin...
Any ETA on when both the plugin itself and the page info will be updated? Server is gonna have a complete wipe clean to start over and this and Population Density along with BigScary's anti x-ray and the nocheatplus plugin are pretty much the only ones being used.
From what I've gathered so far there's been lots and lots of changes with how things are configured and adjusted in these new beta builds of the plugin. Basically we're just hoping to have this new world/server and plugins integrated seamlessly without too much hassle.
Any info you can provide will be appreciated :D