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 22, 2013@ShaneCourtrille
MCPC+ Has a feature to disable placing and crafting items. GP does not have this functionality. You can also use BlockControl to accomplish the same.
I also believe that GP will prevent large scale explosions and will only remove the block that is causing said explosion.
@BC_Programming:
Using mcpc-plus-1.6.2-R0.2-forge845-B62
edit: using gp build 173
http://pastebin.com/Y4hMtPpW
GP is not generating a "config.yml" anywhere. It also re-adds items that I add to the "world.yml"
"_template.yml" (possible this was removed?) is also no longer being mirrored.
Edit 2:
Claims are not being saved with the combination that I currently am running. I will revert back to build 95 which was stable for 152 and do some more testing.
-
View User Profile
-
Send Message
Posted Sep 21, 2013Is there..
a) a way to block nukes, reactor explosions using the 7.7 build
or
b) a dev build that will do so and works with 1.5.2?
btw I am using MCPC+ which I noticed was mentioned in the dev config.
-
View User Profile
-
Send Message
Posted Sep 21, 2013@DarkValaMorgoth
Yes.
-
View User Profile
-
Send Message
Posted Sep 21, 2013@BC_Programming
Is there and updated list of permissions???
-
View User Profile
-
Send Message
Posted Sep 21, 2013@BC_Programming
then the perms changed????
-
View User Profile
-
Send Message
Posted Sep 21, 2013@Alshain01
There aren't any GriefPrevention.* permissions in the dev builds. griefprevention.ignoreclaims is not a permission either, it is griefprevention.claims.ignore now.
@DarkValaMorgoth
buyclaimblocks needs both griefprevention.claimblocks.buy as well as griefprevention.commands.buyclaimblocks.
-
View User Profile
-
Send Message
Posted Sep 21, 2013@DarkValaMorgoth
They still have all other functions it seems
-
View User Profile
-
Send Message
Posted Sep 21, 2013@Alshain01
I have never had ANY problems with this plugin before.
-
View User Profile
-
Send Message
Posted Sep 21, 2013@DarkValaMorgoth
I'm also having issues getting really any permission to work, but specifically griefprevention.* and griefprevention.ignoreclaims don't seem to give me access on my test bench.
-
View User Profile
-
Send Message
Posted Sep 21, 2013Players are reporting that they no longer have access to /buyclaimblocks. All permissions are still there. Please help....
-
View User Profile
-
Send Message
Posted Sep 21, 2013@MinerAccident
Build Includes Access and Container Trust.
Container includes Access Trust.
Manager and Owner are separate.
There is no "inheritance". Tests for Access trust on the plugin succeed of the target player has access trust, Container trust, or Build trust; tests for Container trust success for Container and Build trust, but fail for Access trust, and tests for Build trust fail for Container and Access trust and succeed for build trust. The owner of a claim always has full access to that claim as well.
Managers are separate. as-is they have the ability to "manage" the claim by resizing it or creating subdivisions, but not necessarily to actually do anything within the claim(s).
The RequireX checks are really a exact mirror of the logic in the code. In fact they use the same functions to perform the checks.
RequireOwner only passed for the Owner of a Claim. RequireManager passes if the player is a Manager OR if they are an Owner. All the trust tests will succeed for the Owner of a claim. RequireAccess will succeed for Players that own the claim or have Access,Container or Build Trust. RequireContainer will succeed for the player that owns the claim or have Container or Build trust. RequireBuild will succeed for the player that owns the claim or players with Build trust.
-
View User Profile
-
Send Message
Posted Sep 19, 2013Hello. I'm having a problem with the claim amounts. i have the claims set to 200000(big claims yes) and the amount per hour 100000(yes big). its a personal server for friends, but no one is gaining any additional blocks to claims with, I've been on for a few hours and haven't gained any more blocks, even after i raised the limit to 200000. Am i doing anything wrong?
-
View User Profile
-
Send Message
Posted Sep 19, 2013@BC_Programming
Thanks for your reply! First, I want to say that I did set up GroupManager from Essentials plugin, and gave my default group the griefprevention.claims.allow, griefprevention.claims.create, and griefprevention.claims.delete permissions before I even read your reply, and it did indeed work for new players using the first chest drop feature. Awesome!
Finally, you're right, I didn't frame my second question very well. I understand that the ClaimControl setting doesn't actually give permissions, but only checks them. Still I believe you mostly answered my question further down. If I understand it correctly:
Am I on the right path here? I apologize for having a little trouble wrapping my head around this. In what case might someone pass a RequireBuild claim check, but not a RequireManager? If you could explain that, then I think I will have a better understanding of how it works.
Thank you for your help!
-
View User Profile
-
Send Message
Posted Sep 19, 2013@GodsDead
One possibility is that you could mark off a subdivision or two inside the spawn claim for a dock with public build trusts. That would let people do boating in that area but keep them from damaging any other parts of your spawn.
-
View User Profile
-
Send Message
Posted Sep 19, 2013Is there a way I can set GP to let boats be laid in admin claims? My spawn island is in the middle of the sea, and players need to be able to plant a boat!
-
View User Profile
-
Send Message
Posted Sep 19, 2013@Odense36 There is no logic dealing with flower-pots currently as far as I'm aware. I believe unrecognized interactions require access trust by default and might be cancelled in the wilderness in creative mode.
@MinerAccident
Creating claims when placing their first chest requires griefprevention.claims.allow permission. The world config for the world needs to have GriefPrevention.Claims.AutomaticNewPlayerClaimsRadius set to a value greater than -1 (it defaults to 4).
You might need a permissions plugin.
what exactly do the different claim trusts allow under the GriefPrevention.Rules - ClaimControl:? I'm talking about the RequireOwner, RequireManager, RequireAccess, RequireContainer, and RequireBuild? I can not find this in the new documentation.
They don't "allow" anything. they are requirements of the rule they are within. From here: http://dev.bukkit.org/bukkit-plugins/grief-prevention/pages/7-8-and-later-grief-prevention-configuration/
For example the ClaimControl setting on something like the "Lever" Rule sets the required trust level for a player to perform that action within a Claim.
AccessTrust is(normally) for buttons and levers. Container Trust includes Access Trust but also allows the use of Containers. Additionally, many things like Villager Trading or Sheep shearing default to requiring container trust. Build trust includes Access trust and container trust (the latter because with build trust you could steal items using hoppers anyway). Managers in a claim can resize the claim, and permissiontrust allows setting permissions. Permissiontrust isn't included in ClaimControl because it applies only to commands anyway. The names used to correspond with hard-coded behaviour but now it's entirely customizable so the Trust levels really just represent the defaults.
-
View User Profile
-
Send Message
Posted Sep 18, 2013Hi all! Really liking the flexibility and power of this plugin. Still new to administrating a minecraft server, so been doing a lot of reading. But to my questions:
I am using build 170 I believe with the latest craftbukkit (1.6.2-R1.0), and have not had too many issues. So far the only one I have come across is my new players don't seem to be able to use their first chest to make their initial claim. I think it might be a permissions issue, since I could do it with my account as the server OP. Anyone has any thoughts on this, please let me know. Do I need a permissions mod for this to work right?
My actual MAIN question right now, is what exactly do the different claim trusts allow under the GriefPrevention.Rules - ClaimControl:? I'm talking about the RequireOwner, RequireManager, RequireAccess, RequireContainer, and RequireBuild? I can not find this in the new documentation. And I am assuming there is a heirarchy built in (inheritance)? And if so, what is that heirarchy? Is it in the order above, or a different order? I'm hoping it is different: Owner -> Manager -> Build -> Container -> Access would make sense to me, but let me know where I can go to read about this, or tell me how this works. Any help would be great, thanks!
-
View User Profile
-
Send Message
Posted Sep 18, 2013I see. Thanks for the info =)
I still have another issue though... I have the '*' permission on my group. Now that I installed griefprevention, i'm unable to plant flowers in pots. They just immediatly dissapear, no errors. When i remove the '*' I am able to plant flowers again.
So I was wondering if there is a permission that doesn't allow to plant flowers in pots?
-
View User Profile
-
Send Message
Posted Sep 18, 2013@Odense36
That won't be possible without a database schema change and special logic to add the column if it isn't found, at the very least.
Even with 7.8/dev you can only set a per-world maximum for all players.
-
View User Profile
-
Send Message
Posted Sep 17, 2013@Alshain01
Isn't that just to give them more blocks to extend or make new claims? Let's say a player has 1000 blocks. That would mean that he can claim 10 plots of 10x10. I want to limit this for normal players to 1 claim (so only can extend) and 2 claims for vip users.
Edit: I just noticed the "CreationRequiresPermission" which let's people with permission claim multiple lands. But is there a way to put down a max number of claims? Can't seem to find that one.